Did I fail Memtest86..?

[z1ggy]

I believe I used version 4.6.

I ran the test for 22hr or so, did 15 passes, 3 iterations. The overall results said I had 65353+ errors and 19 max contiguous errors. My comp does crash from time to time, although I think this is more of a registry file/HD problem. So, to me it looks like I failed big time. Do I need new memory?

Also, does G skill have life time warranty on their RAM? If so, can I simply send my sticks back to them, and get 8gb back for free? Thanks.

 

[Dahak]

With that number of error it could be yes your memory is bad, but I would check the following first.

1) are you overclocking? if so run it at stock and see
2) is the memory running at spec?
3) is there a bios update to the board to help compatibility?
4) is it two sticks of 4GB Ram? or its it 1 stick of 8GB Ram.
4a) if it is two stick, try one stick at a time and see if it fails.

if it still fails after all that then I would replace the ram. I am not familiar enough with G.Skill to know if there is a lifetime warranty or not

 

[z1ggy]

With that number of error it could be yes your memory is bad, but I would check the following first.

1) are you overclocking? if so run it at stock and see
2) is the memory running at spec?
3) is there a bios update to the board to help compatibility?
4) is it two sticks of 4GB Ram? or its it 1 stick of 8GB Ram.
4a) if it is two stick, try one stick at a time and see if it fails.

if it still fails after all that then I would replace the ram. I am not familiar enough with G.Skill to know if there is a lifetime warranty or not

1. no
2. yes
3. unsure but I was under the impression to not mess with the BIOS/UEFI
4. 2x4gb
4a. okay

 

[gbeirn]

Run Memtest+, latest version is 5.01 I believe. So older versions will not work well with newer chipsets/CPUs.

 

[Charlie98]

3. unsure but I was under the impression to not mess with the BIOS/UEFI

Generally true... unless you are encountering problems. :biggrin:

 

[z1ggy]

Run Memtest+, latest version is 5.01 I believe. So older versions will not work well with newer chipsets/CPUs.

Okay, I will download that verson, thanks.

Generally true... unless you are encountering problems. :biggrin:

I'll check to see if an update has been released. Can I do this right from the UEFI main screen, or do I need to go to ASRock's website?

Also I looked and G.skill does offer lifetime warranty on their RAM. I'd need to go get an RMA code and then ship the memory back to them.

 

[xgsound]

The most I ever ran Memtest86 was 1 pass of every test. More cannot hurt. I considered any error bad ram at current timings and voltages; I would then retest at new timings or voltage looking for no errors.

I often start troubleshooting for random crashes with memtest86 because it uses so few other resources and establishes memory as good or bad. YMMV

Jim

 

[z1ggy]

So it's clear I've got some junkie RAM. However, windows is running funky, too. I downloaded Diskcheckup and ran the quick test. All statuses as OK. But when I run the long test (which takes over night) I come back and the computer always crashes. Is this due to the RAM, too?

I'm thinking I need some new memory and also a reformat of windows. I might grab an SSD while I'm at it if I'm going to bother doing a reformat.

I'm assuming my HD is okay though, even though the computer seems to keep crashing during the long test? The SMART values all say OK.. no critical errors or anything.

 

[Blain]

So it's clear I've got some junkie RAM.

Not so fast, Sparky...

"Please be aware that not all errors reported by MemTest86 are due to bad memory.

The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard.

It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.

Once a memory error has been detected, determining the failing SIMM/DIMM module is not a clear cut procedure. With the large number of motherboard vendors and possible combinations of memory slots it would be difficult if not impossible to assemble complete information about how a particular error would map to a failing memory module."