MemTest86 results: 10000+ errors

[Mockingbird]

...and this is without enabling EXPO/XMP

/

[hellowalkman Reporter]

MemTest rarely gives failures or errors on stock RAM unless there is a hardware issue, like the RAM is physically bad (bad SPD hub maybe or bad chips) or some issue elsewhere like in the CPU's IMC or the motherboard, at least that's what I've found from my experience.

Remove, clean, and re-seat the ram one stick at a time to see if the same result persists. If it passes, then try two together.

Also, this article may help: https://www.memtest86.com/troubleshooting.htm

[Mindovermaster Moderator]

Yes, as Hellowalkman says, try running each stick separately. Coiuld be one particular stick.

Also, If you have any spare RAM, try that, too. Just to check out your board isn't the problem.

[sinetheo]

I would over volt and the memory and memory controller and under clock and rerun the test. If there are still problems try each stick to see if you have a bad dimm. 

 

[Mindovermaster Moderator]

I wouldn't over Volt it, but do reset BIOS if anything was overclocked.

[ThaCrip]

I think others already gave you the gist of it. but I would give memtest.org a shot and see if that reports similar.

[Mockingbird]

A different set of memory gives the same errors.

PC won't post when switching memory slots from A2 and B2 to A1 and B1.

[adrynalyne]

On 10/12/2023 at 19:45, Mockingbird said:

A different set of memory gives the same errors.

PC won't post when switching memory slots from A2 and B2 to A1 and B1.

There is only one culprit left— the motherboard. 

[Mockingbird]

On 10/12/2023 at 18:59, adrynalyne said:

There is only one culprit left— the motherboard. 

After a CMOS reset, it now ran memtest86 for 30 minutes without any error.

Before, it would throw errors almost immediately.

Still, a long way to go.

[Mindovermaster Moderator]

On 10/12/2023 at 21:11, Mockingbird said:

After a CMOS reset, it now ran memtest86 for 30 minutes without any error.

Before, it would throw errors almost immediately.

Still, a long way to go.

It was an overclock that went wrong..

[Mockingbird]

On 10/12/2023 at 20:26, Mindovermaster said:

It was an overclock that went wrong..

The PC was not overclocked at all.

EXPO/XMP off

[adrynalyne]

On 10/12/2023 at 21:30, Mockingbird said:

The PC was not overclocked at all.

EXPO/XMP off

Since you aren’t offering anything but tidbits of info, answer just one thing directly please: Was the bios set to defaults? If the answer is yes, then I still wouldn’t trust the motherboard or at the very least the bios version since it clearly trained the ram wrong. CMOS resets shouldn’t be needed for something like this unless you had set incompatible bios settings (more than likely in the form of an overclock).

[Mockingbird]

On 11/12/2023 at 01:36, adrynalyne said:

Since you aren’t offering anything but tidbits of info, answer just one thing directly please: Was the bios set to defaults? If the answer is yes, then I still wouldn’t trust the motherboard or at the very least the bios version since it clearly trained the ram wrong. CMOS resets shouldn’t be needed for something like this unless you had set incompatible bios settings (more than likely in the form of an overclock).

Yes. The BIOS wasn't touched at all.

[Mockingbird]

Anyway, after the CMOS reset, Memtest86 now shows a PASS with the new set of memory.

[hellowalkman Reporter]

On 11/12/2023 at 20:38, Mockingbird said:

Anyway, after the CMOS reset, Memtest86 now shows a PASS with the new set of memory.

Just to be a bit more sure, I recommend trying HCI Memtest and y-Cruncher (single-threaded All in RAM test). I have found that these work very well in detecting unstable RAM.

[WITHOUT-ME]

try with another PSU

[Mockingbird]

On 11/12/2023 at 01:36, adrynalyne said:

Since you aren’t offering anything but tidbits of info, answer just one thing directly please: Was the bios set to defaults? If the answer is yes, then I still wouldn’t trust the motherboard or at the very least the bios version since it clearly trained the ram wrong. CMOS resets shouldn’t be needed for something like this unless you had set incompatible bios settings (more than likely in the form of an overclock).

You are right about that.

A BIOS update appears to have resolved (or at least alleviated) the problem.

[Mindovermaster Moderator]

On 12/12/2023 at 20:52, Mockingbird said:

You are right about that.

A BIOS update appears to have resolved (or at least alleviated) the problem.

You never mentioned you did a BIOS update.. 

[Raa]

On 13/12/2023 at 14:36, Mindovermaster said:

You never mentioned you did a BIOS update.. 

Yup, that literally makes all the difference. A pretty big omission by the OP... 🤦‍♂️

 

[adrynalyne]

On 12/12/2023 at 21:41, Raa said:

Yup, that literally makes all the difference. A pretty big omission by the OP... 🤦‍♂️

 

It’s a very weird discussion. Is he testing us?

[hellowalkman Reporter]

Maybe he just wanted the conversation to go on for longer. 😚

[Mockingbird]

On 12/12/2023 at 20:41, Raa said:

Yup, that literally makes all the difference. A pretty big omission by the OP... 🤦‍♂️

 

The BIOS update was only performed afterward.

After the CMOS reset, the PC passed Memtest86, but the crashing issue persists.

A BIOS update was later performed, which resolved the crashing issue (at least so far).

Edited December 13, 2023 by Mockingbird

[Mockingbird]

On 12/12/2023 at 19:36, Mindovermaster said:

You never mentioned you did a BIOS update.. 

The BIOS update was only performed afterward.

After the CMOS reset, the PC passed Memtest86, but the crashing issue persists.

A BIOS update was later performed, which resolved the crashing issue (at least so far).

Edited December 13, 2023 by Mockingbird