Unstable E2140 need lots of advice

ColdAsIce · 30 Nov 2008 at 20:15

Having loads of trouble with this E2140, if anyone could take a look at my settings and point me in the direction of where I am going wrong.

thanks for looking.

gareth170 · 30 Nov 2008 at 20:23

looks like the ddr voltage failed.

is your memory running at 667 or 800? if 800 u need to underclock it so u can get a stable overclock on your cpu

ColdAsIce · 30 Nov 2008 at 20:47

ColdAsIce · 30 Nov 2008 at 22:29

Just ran memtest, getting loads of errors. Should I just put everything back to default and run memtest again?

MeatLoaf · 30 Nov 2008 at 22:55

ColdAsIce said:
Just ran memtest, getting loads of errors. Should I just put everything back to default and run memtest again?

Yep id try that to begin with

Senture · 30 Nov 2008 at 23:42

At a guess, it looks like you're pushing the RAM too far (timing wise). 2gb sticks usually run at 5-5-5-15 or 5-5-5-18 and yours are running at 5-3-3-15. What sticks do you have?

slowrunner · 1 Dec 2008 at 10:03

1. PCI-Express frequency wants to be locked at 100mhz

2. Looks like you have 667mhz memory and are trying to run it at 800mhz?

3. Memory timings are too tight.

4. System voltage control should be set to manual, on auto the settings you've entered wont be being used.

kerrgreg · 1 Dec 2008 at 10:22

what motherboard and ram are you running?

ColdAsIce · 1 Dec 2008 at 12:14

kerrgreg said:
what motherboard and ram are you running?

Gigabyte GA-P35-DS3R (Socket 775)

Crucial Ballistix 2GB (2x1GB) DDR2 PC2-5300C3 667MHz Dual Channel Kit

ColdAsIce · 1 Dec 2008 at 12:42

PC won't even boot now, awesome.

With one stick of RAM in it powers up but there is no display.

With both sticks it powers up for 1 second and then reboots its self.

Trying different combinations with no success

Gunda · 1 Dec 2008 at 12:44

so yeah you need to drop your fsb to 333and lock the ram at 667 or lower using 1:1 also set your timings to 5-5-5-15. should see you up to a 2.66Ghz clock with the 8multi.

you ram is holding you back on getting anything more from that cpu.

slowrunner · 1 Dec 2008 at 13:02

As Gunda said, the RAM is limiting you, I wouldn't be surprised if it's now fried itself from being run at 800mhz with such tight timings. If it is goosed and needs replacing get some DDR2-6400, then you can safely run the RAM the way you were, after slacking the timings off to manufacturers specs.

ColdAsIce · 1 Dec 2008 at 13:09

slowrunner said:
As Gunda said, the RAM is limiting you, I wouldn't be surprised if it's now fried itself from being run at 800mhz with such tight timings. If it is goosed and needs replacing get some DDR2-6400, then you can safely run the RAM the way you were, after slacking the timings off to manufacturers specs.

Yep, think you are spot on. Going to buy some new ram to test with from a local pc shop.

Cob · 1 Dec 2008 at 13:36

Is it a new system?

Because Ballistix is well known for dying.

ColdAsIce · 1 Dec 2008 at 13:55

Ok it was definitely the memory, just bought some cheap DDR2 800 512 stick for £10 and the system booted with no problems.

Currently running memtest, looks like everything is fine. Didn't even get past 1% last night without like 127errors.

Tempted to take this 512 stick back and just buy two 1gig stickers of ddr2 800 and try overclocking again. Will RMA the old ram and just ebay the replacement sticks.

warren_1979 · 1 Dec 2008 at 21:34

Gigabyte boards always say fails even if you put it +1v above gigabytes default. So running some ballistix's at recommended spec will say fail. Mine does.

slowrunner · 1 Dec 2008 at 22:20

warren_1979 said:
Gigabyte boards always say fails even if you put it +1v above gigabytes default. So running some ballistix's at recommended spec will say fail. Mine does.

My memory voltage is at +0.2v, and the bios health status page doesn't say fail! It says OK!

warren_1979 · 1 Dec 2008 at 22:25

slowrunner said:
My memory voltage is at +0.2v, and the bios health status page doesn't say fail! It says OK!

I have an old 965p ds3 and it does it on that for sure. Didn't fully read the thread and after reading it properly he's obviously duffed his RAM in, that's why it says fail. But the older gigabyte boards have this bug.