Other apps to test RAM - Memtest not working

Toadus · 8 May 2009 at 08:23

Hi.

I have 2 x 2gb DIMMs of Corsair Dominator 8500C5D. When I run Memtest, the application loads fine, I see a progress bar moving very quickly, (lasts about just 5 seconds) gets to about 70% at a guess, then my PC re-boots. :confused:

I'm totally lost on this one. Does anyone know of anything else I can use to test my RAM? The reason being, is that I've been trying to OC my PC for some time now, and whenever I go past 3.2ghz, I get random BSODs always saying the same thing: IRQL_LESS_THAN_OR_EQUAL...

Many thanks in advance!

Yellowbeard · 8 May 2009 at 16:18

On ASUS boards, Memtest has a conflict with the Legacy USB Support setting. Disable this while running Memtest.

Also, if your OC is not stable, it may be a voltage setting. List your voltages for CPU, memory controller, and memory.

Toadus · 9 May 2009 at 08:00

Yellowbeard said:
On ASUS boards, Memtest has a conflict with the Legacy USB Support setting. Disable this while running Memtest.

Also, if your OC is not stable, it may be a voltage setting. List your voltages for CPU, memory controller, and memory.

Hi mate.

I read about the USB legacy when Googling this issue. I turned it off, but it didn't make any odds. I've since upgraded my BIOS, so it might be worth me having another shot actually, I didn't think of that.

I've taken the OC off completely, and everything back to stock, including the RAM, but it doesn't make any difference with Memtest. So weird the way the PC just re-boots.

For my OC settings, I have the following memory config:

5-5-5-15 (as per the manufacturer's instructions)
Bank Cycle Time: 22 (as instructed by CPU-Z)
Command rate: 2 (given by the Auto setting in the BIOS)
Voltage set to 2.17 (manufacturer says 2.1, but the little extra is probably OK)
DRAM Frequency set to 1000mhz. (It's 1066mhz capable ram, but my motherboard can only handle up to ~1000mhz apparently.
All other RAM settings are left on Auto.

tomgibbes · 9 May 2009 at 10:50

I was trying one version of memtest and getting the same problem on a P31 Gigabyte board with my 4gb of 1066mhz ocz gold.

I was using version 3.5 from the official website (i think it was).

When I tried version 2.11 from here:
http://www.memtest.org/
It worked fine and thankfully my RAM is 100% okay.

Hope this helps!

Toadus · 9 May 2009 at 10:58

Thanks very much, I'll give it try this evening and report back.

Yellowbeard · 9 May 2009 at 14:43

Toadus said:
Hi mate.

I read about the USB legacy when Googling this issue. I turned it off, but it didn't make any odds. I've since upgraded my BIOS, so it might be worth me having another shot actually, I didn't think of that.

I've taken the OC off completely, and everything back to stock, including the RAM, but it doesn't make any difference with Memtest. So weird the way the PC just re-boots.

For my OC settings, I have the following memory config:

5-5-5-15 (as per the manufacturer's instructions)
Bank Cycle Time: 22 (as instructed by CPU-Z)
Command rate: 2 (given by the Auto setting in the BIOS)
Voltage set to 2.17 (manufacturer says 2.1, but the little extra is probably OK)
DRAM Frequency set to 1000mhz. (It's 1066mhz capable ram, but my motherboard can only handle up to ~1000mhz apparently.
All other RAM settings are left on Auto.

What is your memory controller voltage set to?

Toadus · 9 May 2009 at 15:53

Is that different to what I posted above? Is that's what's listed as "HT" in my BIOS? If so, it's currently at 1.44. I've tried raising it, but to no evail.

Yellowbeard · 9 May 2009 at 16:12

I have not seen that specific BIOS so you'll need to check the manual or with ASUS. On Nvidia, the memorh controller is called SPP so it could be any variation of MCH, NBv, NB, SPP, SPPv, etc.

On my last 650i board, it took 1.53v to get stable with 4 modules or with 2 at anything above 1000.

Toadus · 9 May 2009 at 16:52

NB? As in the north bridge? If so, I've currently got it at 1.44v. I've set it as high as 1.6v, but that's made no odds to the IRQL issue.

Do you think this is a memory related error?

Toadus · 9 May 2009 at 16:54

It's probably worth mentioning that when I first starting OC'ing this PC, and I was still playing around with Vcore voltages and NB voltages, etc, the crashes were always pretty random. Whereas now, when I try to go past 3.2ghz, it's always the exact same crash. I've tried upping literally all the voltages just to see if it would still do the IRQL message, which it certainly did...