1.7v on air?

meaz

meaz

meaz

Permabanned
Joined
12 Jul 2005
Posts
336
Hi, just to get a screenshot of CPU-Z, ideally at 3.2 or above could I set the vcore to 1.7v or is this seriously going to kill my processor. What are the chances of it surviving on air cooling? the CPU is a 3500+ Venice.

Thanks.
 
3.2 from a 3500+ on air? Don't see that happening I am afraid epsecially in this weather. 1.7v won't kill it but it will run very hot and probably max out at around 2.9
 
remember, this is just for a screenshot of CPU-Z. I've had a screenshot of 3.1GHz already and just want to see the highest I can get from this chip with a cheap heatsink. Temps are well under 45c full load so cooling isn't the problem. I will try 1.65v later and see if I can get it at 3.2GHz.
 
Lol i have same cpu id be scared s less trying for 3ghz :D

G luck tho. ;)

Btw why dont u just do a photoshop job for cpuz lol, save u actually doing the cpu.
 
SkeeterPSA said:
Lol i have same cpu id be scared s less trying for 3ghz :D

G luck tho. ;)

Btw why dont u just do a photoshop job for cpuz lol, save u actually doing the cpu.
Click to expand...

I get bored during the night and like seeing what I can get a screenshot of out of that chip, a photoshop would be easy enough but I wouldnt be able to verify the overclock. :D
 
I reckon it'll make it. It already got to 3101MHz with the akasa £4.25 heatsink. I just need to make another 99MHz and it'd probably be possible pushing it to 1.65v which will probably undervolt to 1.625v.

35006pb.jpg
 
Last edited:
That is one very impressive 3500+ then, how about stop messing around with a 5 quid cooler and get some water cooling :)
 
Unless you have some seriously cool case temps, I very much doubt 45C load.


I had a 2.9ghz 1.595V San Diego that was 55C load with a 15-20C room on a XP-120 with a 6V YS-TECH.
 
My case temperature is either 38 or 25c. I dont know what 'temp' and 'temp1' refer to. So maybe my sensors are under reading my 10c thats still under 50c full load.
 
1.7v is fine for a quick run, id be tempted to try 1.75.

Had my 3000+ on 1.72 with no probs for a quick pi run
 
Cool thanks , I will try 1.65v later and maybe 1.7v if it doesnt die at 1.65v.

Does anyone know where command rate is likely to be in memory settings? does this usually have a different name associated to it as I can't seem to find the option.

Thanks,
meaz
 
I might try 1.7v as I can only get this when set to 1.65v undervolted to 1.616v:

31353wt.jpg


i will try it with the memory on a lower divider now.
 
Nice chip. Hope you manage to get 3.2GHz :)
mainly to proove the disbeleivers wrong :p ;)


Is putting 1.7+ v through a oppy170 temporarily going to be fine? (not that I'd want to go that high, just out of interest)
 
PinkFloyd said:
Nice chip. Hope you manage to get 3.2GHz :)
mainly to proove the disbeleivers wrong :p ;)


Is putting 1.7+ v through a oppy170 temporarily going to be fine? (not that I'd want to go that high, just out of interest)
Click to expand...

i dont think its going to work unless I put 1.7v through this chip, it just locks or blue screens instantly above the screenshot above. Ive tried setting the divider lower and appears it does the same thing - but it is undervolting a fair amount I suppose :(
 
Last edited:
Defcon5 said:
command rate might be command per clock (cpc) with enable/disable
Click to expand...

thanks dude, thats well good. This setting makes an increible difference to performance even at 2600MHz it is as fast as it was before at 2750MHz in Windows. I couldn't find the setting in the BIOS so I downloaded A64 Tweaker and set it that way which did the job.

arghhhh, this 1t malarky makes my system unstable.
 
Last edited:
I honestly wouldnt trust CPU-Z voltage readings. It actually more likely to be closer to what its actually set to in the bios. 45c load on 1.6v @ 3.1ghz is just wrong also, unless you're on water.
 
You must log in or register to reply here.
Back
Top Bottom