Need help with Memtest86!

[Backstretch]

Hey guys. I'm way out of my league here. Long story short my games (BF5, Apex, etc.) would artifact, crash, give me a BSOD, black screen my computer (no display out), hard lock it, the works. I RMA my GPU and the new card has the exact same problems. So now i'm thinking it's not the card. The latest BSOD i got was memory management, so i went ahead and ran MemTest86 and here are my results.

 

As you can see there are errors. I don't know if they're the source of my issues but an error is an error. I just don't know what they mean. Any help would be awesome. Here is a link to my build. https://pcpartpicker.com/list/99sqFt

Again thank you for any help. Really trying to solve this issue. It's super frustrating.

[porina]

Any ram error is bad. Are they repeatable or do they vary between tests? See if it goes away if you reduce the ram speed.

 

I would suggest making sure you're on latest mobo bios, but do not update the bios while you're getting ram errors as you don't want to risk corrupting the bios.

[Backstretch]

1 minute ago, porina said:

Any ram error is bad. Are they repeatable or do they vary between tests? See if it goes away if you reduce the ram speed.

 

I would suggest making sure you're on latest mobo bios, but do not update the bios while you're getting ram errors as you don't want to risk corrupting the bios.

I've only run the test once, because as you can see it took over 3 hours to complete. I will try to scale my RAM back, and see if i still get the errors. will report back with my findings.

[porina]

3 minutes ago, Backstretch said:

I've only run the test once, because as you can see it took over 3 hours to complete. I will try to scale my RAM back, and see if i still get the errors. will report back with my findings.

My thinking is trying to work out if the ram is defective, or is it just a case of incompatibility. Normally it is a case of work or not work, but you can hit marginal cases where it seems to work but might throw occasional errors. These can be really annoying... If you drop the speed (turn off DOCP/XMP) and still get repeatable errors, that would point to faulty ram. 

 

To save time, I believe memetest86 can let you select which tests to run. You could only do those ones which indicated errors previously.

 

Out of interest, are you running the ram at 3000 or 2933? Even if ram can be set to 3000, the highest officially supported speed is 2933. It's only a minor difference, but could swing it.

[Backstretch]

8 hours ago, porina said:

My thinking is trying to work out if the ram is defective, or is it just a case of incompatibility. Normally it is a case of work or not work, but you can hit marginal cases where it seems to work but might throw occasional errors. These can be really annoying... If you drop the speed (turn off DOCP/XMP) and still get repeatable errors, that would point to faulty ram. 

 

To save time, I believe memetest86 can let you select which tests to run. You could only do those ones which indicated errors previously.

 

Out of interest, are you running the ram at 3000 or 2933? Even if ram can be set to 3000, the highest officially supported speed is 2933. It's only a minor difference, but could swing it.

Okay so essentially i scaled the RAM back from 3200 mhz to 3000 mhz (the modules rated speed w/ XMP, but i manually set the speed to 3000mhz, i did not enable XMP). I probably should've done this first before bugging you but that OC worked for months without a hitch. It's just now giving me problems. Anyway after scaling back the RAM i ran the

test and got zero errors.

Why did it just now decide to start screwing with me? I have G skill TridentZ with Samsung B-die, why can i not OC it stable a mere 200mhz? Should i run the test again? Maybe the first test was an outlier? Maybe this test was? I am so out of my knowledge pool here. Thank you for your help again.

[porina]

1 hour ago, Backstretch said:

Why did it just now decide to start screwing with me? I have G skill TridentZ with Samsung B-die, why can i not OC it stable a mere 200mhz? Should i run the test again? Maybe the first test was an outlier? Maybe this test was? I am so out of my knowledge pool here. Thank you for your help again.

Maybe it was close to the limit already, but small shifts in component tolerances over time were sufficient to push it over. Even changes in weather could push it. I had CPU overclocks that were fine in winter, but went unstable when it got warmer.

 

You might be able to get it working at 3200 again if you tinker more with timings and voltages, but in my opinion it isn't worth the time.

[nick name]

Without knowing your timings, your voltages we can't really help you identify anything.  Can you give us more information?

[Backstretch]

Here is what you guys asked for. the voltage is set to auto in BIOS, and is ALWAYS sitting at 1.36V. Basically everything of consequence is set to AUTO in BIOS. except the memory frequency of course. the XMP profile only goes to 2933 even though it's a 3000mhz kit. everything outside of that is bone stock for memory.

[Falkentyne]

Set command rate to 2T

Then set Memtest86 to LOOP test #7 (moving inversions, 32 bit).

This should find errors faster without dealing with the hammer test (hammer test takes like double the time of the previous 12 tests combined).

[Backstretch]

9 hours ago, Falkentyne said:

Set command rate to 2T

Then set Memtest86 to LOOP test #7 (moving inversions, 32 bit).

This should find errors faster without dealing with the hammer test (hammer test takes like double the time of the previous 12 tests combined).

will setting the command rate to 2T allow me to clock my RAM to 3200mhz?