1.7v on air?

meaz · 2 Jul 2006 at 19:39

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.

meaz · 2 Jul 2006 at 19:58

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.

meaz · 2 Jul 2006 at 20:12

SkeeterPSA said:
Lol i have same cpu id be scared s less trying for 3ghz

G luck tho.

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

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.

meaz · 2 Jul 2006 at 20:43

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.

meaz · 2 Jul 2006 at 22:23

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.

meaz · 2 Jul 2006 at 23:05

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

meaz · 2 Jul 2006 at 23:27

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

i will try it with the memory on a lower divider now.

meaz · 2 Jul 2006 at 23:40

PinkFloyd said:
Nice chip. Hope you manage to get 3.2GHz
mainly to proove the disbeleivers wrong

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)

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

meaz · 3 Jul 2006 at 00:19

Defcon5 said:
command rate might be command per clock (cpc) with enable/disable

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.

meaz · 3 Jul 2006 at 16:47

my ram is geil value pc3200 @ 2.5-3-3-5 timings - it was clocked @ 235MHz when I had the crash and that was only 2585mhz or something. I only run it 24/7 at 2617MHz as I change it with easytune for the last few FSB. Vdimm @ 2.8v highest the mobo will allow.

thanks

meaz · 4 Jul 2006 at 16:20

I`ve been running it at 2907MHz 24/7 since last night and it hasnt crashed, makes folding@home a bit faster than at 2617MHz. It is safe running 1.55v for a long time? or is it likely to make my chip subject to electromigration where it will deteriate in quality and need more vcore to do the same speed as before?

meaz · 4 Jul 2006 at 23:01

cool thanks for the help. Its still not crashed at 2900 and its at 44c full folding load according so speedfan with a 33c case temp.

meaz · 5 Jul 2006 at 13:03

it crashed at 2.9ghz 1.55v so have upped it to 1.6 this is undervolted to 1.56v - 1.584v according to cpu-z latest build. I am thinking its the Geil Value PC3200 that doesn't like running at 240MHz 24/7 folding, folding needs total stability to run even more than seti@Home so the system would probably be prime stable at 1.55v just not folding stable. If it crashes again I will lower the voltage back to 1.55v and set the divider from 183 to 166 and hopefully that'll sort it out.

meaz · 5 Jul 2006 at 13:50

just last night after a day of running folding it crashed, the screen just went blue no blue screen just the screen was blue. IVe never seen that happen before. Was a strange one, it could be the power regulaltors overheating as its only an nForce3 250gb cheap mobo.

meaz · 5 Jul 2006 at 15:10