GeIL 2GB PC6400C4 800MHz DDR2 Voltage?

keogh · 9 Apr 2007 at 11:32

Howdy,

I have the GeIL 2GB (2x1GB) PC6400C4 800MHz Ultra Low Latency DDR2 in my ASUS P5N-E SLi Motherboard and just want to know what voltage you think I should put the sticks at?

I'm running them on stock/suggested timings at 4-4-4-12 2T 800mhz. I dont want to up the mhz, cos I'm sure its that which is giving me the blue screen of death every now and then.

I know GeIL suggest 2.1v, but my ASUS doesn't like to be exact like that, so I have the choice of:

2.085v
2.178v
2.259v
2.353v

Obviously there are a few more, but I wouldn't use those. I have it at 2.259v at the moment... is that the best?

Any advice will be appreciated!

p.s. I'm halfway thru test 8 on memtest86 without any failures so far wth 4-4-4-12 2T 800mhz @ 2.259v

ta

MeatLoaf · 9 Apr 2007 at 15:09

If youre not clocking it put it 2.178v

keogh · 9 Apr 2007 at 16:20

MeatLoaf said:
If youre not clocking it put it 2.178v

you got it!

ted34 · 13 Apr 2007 at 12:11

run memtest to confirm whats giving you the BSOD. If your not clocking you should easy be able to keep them below 2.1v. Check your chipset volts isnt too low as that could be causing the crashes at 400mhz

keogh · 13 Apr 2007 at 12:26

Im at stock now and I run memtest when I was running at 850mhz on the same timings, and I left memtest running for 9hrs and got 14 passes 0 fails, so its not the RAM.

I've dropped my E6600 to 3ghz now and (fingers crossed) it seems to be running ok now, I think its my P5N-E thats causing the issues, it doesn't like me overclocking at all!

paniK · 13 Apr 2007 at 13:02

sorry to hijack a bit but my problem is the same. blue screen of death every now and again with the same RAM but 1gb and an e4300 @ 2.7ghz. the blue screen only appears when I come out of standby and this is occasionally maybe 3 times a week maybe more.

vcore @ 1.325
vdimm @ 1.8V
DDR2 overvoltage @ 0.3V so effectively 2.1V as suggested by Geil
timings at 4-4-4-12. tried loosening to 4-5-5-12 but didn't help.
FSB @ 300MHz on CPU
Divider @ 2.66
RAM speed @ 798Mhz in bios

anyone shed any light.

and I can't run memtest cos I run a cordless keyboard and mouse that doesnt works in the bios but dont work anywhere else. running a DS3 btw

keogh · 13 Apr 2007 at 13:10

paniK said:
sorry to hijack a bit but my problem is the same. blue screen of death every now and again with the same RAM but 1gb and an e4300 @ 2.7ghz. the blue screen only appears when I come out of standby and this is occasionally maybe 3 times a week maybe more.

vcore @ 1.325
vdimm @ 1.8V
DDR2 overvoltage @ 0.3V so effectively 2.1V as suggested by Geil
timings at 4-4-4-12. tried loosening to 4-5-5-12 but didn't help.
FSB @ 300MHz on CPU
Divider @ 2.66
RAM speed @ 798Mhz in bios

anyone shed any light.

and I can't run memtest cos I run a cordless keyboard and mouse that doesnt works in the bios but dont work anywhere else. running a DS3 btw

does it do the same when running at stock (i.e. no overclock)?

paniK · 13 Apr 2007 at 13:14

erm, it was at stock for about 2 weeks and I couldn't say it did.

in saying that if there's something dodgy with the overclock, what is it? im sure the voltages and performance stats are fine and I am aware this is 1GB and not 2GB but im hardly pushing whats possible. just annoyed at what it is.

chipset maybe?

everything looks good but something is amiss somewhere

keogh · 13 Apr 2007 at 13:18

Well it is the same with me, if I run my CPU at 3.4ghz, although it runs fine for 19hrs in Orthos, I get the occasional BSOD during games, and I also get the random BOOT FAILURE.

But now I have knocked my CPU down to 3ghz it seems (so far) to be ok... but I havent been running it long in 3ghz so cant say for sure yet.

I mentioned on the Asus P5N-E thread that I think it might be the Vcore offset being at auto, so once I know it is ok at 3ghz for a while, im gonna bump it back to 3.4ghz and set the offset to +100mv and see what difference it makes.

But its sumin to do with the overclock and my board I reckon!

paniK · 13 Apr 2007 at 13:39

you see, mine isnt even at load, I can run anytghng I want and it won't do anything. Its only when I logon to windows 2 seconds later BAD_POOL_CALLER and it does a memory dump then says restart. then it does diskcheck and finds errors in system32. this is all very regular and annoying

keogh · 13 Apr 2007 at 13:45

paniK said:
you see, mine isnt even at load, I can run anytghng I want and it won't do anything. Its only when I logon to windows 2 seconds later BAD_POOL_CALLER and it does a memory dump then says restart. then it does diskcheck and finds errors in system32. this is all very regular and annoying

Hmm thats sounds much worse than my problem?

Mine just occasionally goes black on boot up and stays black, I have to force another restart and it will tell me I have a boot failure during post, and it will reset my BIOS to default.

But upon going into my BIOS the values will STILL be selected at what I had it at during overclock, but the actual settings will be default (i.e. is CPU-Z it will tell me 2.4ghz). So all I have to do is hit F10 to save again, and reboot and it gets in.

Then it might not happen when I restart the next time... on the other hand it might

Not sure bout your problem though? Seems a bit more serious?

Maybe stupid, but have you run a diagnostics test on your HDD for bad sectors? I thought it was my Seagate, but I run a full long drive test on that and it showed as fine!