Memtest86 acceptable results?

[failblox]

First, a little background info. I have 8GB (2x4GB) of Corsair Vengeance DDR3 1600MHz 9-9-9-24 1.5V on a P8Z77-V Pro, but recently I've added another 8GB (2x4GB) Corsair Vengeance kit with the exact same specifications listed earlier. The only difference between the two kits of memory looking at the boxes is that one is red and the other is black.

Below is a link to my results running Memtest86 for ~36 hours non-stop.

http://i.imgur.com/qi61qvc.jpg

Is the one error that I have out of 10 passes okay for stability? I'm not looking for rock-solid-google-server-grade stability, but just for general use, gaming, and video editing.

Is this normal or should I buy new RAM/take the new kit out? Any help would be greatly appreciated

[Enderman]

- How many errors are acceptable?

No errors are acceptable. Even if there is just one error, something is

amiss which can cause your system to crash. Of course what the cause of the

errors is you will still have to determine.

http://www.memtest.org/download/1.55/memtest86+-1.55/FAQ

[Krzyimprt]

First, a little background info. I have 8GB (2x4GB) of Corsair Vengeance DDR3 1600MHz 9-9-9-24 1.5V on a P8Z77-V Pro, but recently I've added another 8GB (2x4GB) Corsair Vengeance kit with the exact same specifications listed earlier. The only difference between the two kits of memory looking at the boxes is that one is red and the other is black.

Below is a link to my results running Memtest86 for ~36 hours non-stop.

http://i.imgur.com/qi61qvc.jpg

Is the one error that I have out of 10 passes okay for stability? I'm not looking for rock-solid-google-server-grade stability, but just for general use, gaming, and video editing.

Is this normal or should I buy new RAM/take the new kit out? Any help would be greatly appreciated

Yeah that look fine.

[Enderman]

Yeah that look fine.

If you think having a BSOD every day because of a mem error is "fine" then you might need to look up the definition of that word again.

[Tr3vor]

If you get one error, it is not fine.

 

I'd figure out what stick is the problem and replace it.

[failblox]

If you think having a BSOD every day because of a mem error is "fine" then you might need to look up the definition of that word again.

The reason I'm asking is because with prime95 - for example - just because prime95 crashes your computer doesn't necessarily mean that your computer will crash under daily use. Prime95 is a worst case scenario program - a stress tester, which is what Memtest86 is except just for memory. Am I right?

So yes, you're right - my computer isn't 100% stable. However, under normal use I don't think I should get a BSOD.

I may be entirely wrong about this - maybe memory stability is different than CPU stability but if I'm wrong please correct me.

I think I should mention that I don't have the money to spare to buy a new 16GB kit of RAM.

[Enderman]

The reason I'm asking is because with prime95 - for example - just because prime95 crashes your computer doesn't necessarily mean that your computer will crash under daily use. Prime95 is a worst case scenario program - a stress tester, which is what Memtest86 is except just for memory. Am I right?

So yes, you're right - my computer isn't 100% stable. However, under normal use I don't think I should get a BSOD.

I may be entirely wrong about this - maybe memory stability is different than CPU stability but if I'm wrong please correct me.

You don't have a say what parts of your memory your OS uses. If a piece of data is saved to your ram and it gets corrupted it will cause a BSOD. How often your OS will put one of its files in that bad section is another question. Either way it is an issue, and you should fix it or RMA the RAM (lol) because one error is not normal. Mem test is not a stress test, it is a stability test, and it should be 0 errors no matter what.

[failblox]

You don't have a say what parts of your memory your OS uses. If a piece of data is saved to your ram and it gets corrupted it will cause a BSOD. How often your OS will put one of its files in that bad section is another question. Either way it is an issue, and you should fix it or RMA the RAM (lol) because one error is not normal. Mem test is not a stress test, it is a stability test, and it should be 0 errors no matter what.

So even though I'm mixing different RAM kits, this isn't normal?

[Enderman]

So even though I'm mixing different RAM kits, this isn't normal?

anything above 0 is not normal and needs to be fixed

[failblox]

anything above 0 is not normal and needs to be fixed

Thanks. I'll do some more testing and see if I can isolate the problem.

Just wondering - is it possible that the two kits of RAM are stable, each on their own, working separately from the other kit, but it's just that they're unstable when you put the two kits together?

[Enderman]

Thanks. I'll do some more testing and see if I can isolate the problem.

Just wondering - is it possible that the two kits of RAM are stable, each on their own, working separately from the other kit, but it's just that they're unstable when you put the two kits together?

Ok, troubleshooting should find the problem.

I dont really mix my ram kits, but afaik it is possible to have two working kits with no errors that give an error when used together. This would probably be an issue with the motherboard ram configuration settings, but i think its also possible that two ram kits have issues with eachother, although this is really rare.

[Krzyimprt]

If you think having a BSOD every day because of a mem error is "fine" then you might need to look up the definition of that word again.

joking... It's probably because they were not from the same two kits. But then again, memtest is not always 100% accurate.

[Enderman]

joking... It's probably because they were not from the same two kits. But then again, memtest is not always 100% accurate.

Yeah, it actually is 100% accurate. It scans every bit and byte in your RAM to make sure it works as intended.

[Krzyimprt]

Yeah, it actually is 100% accurate. It scans every bit and byte in your RAM to make sure it works as intended.

I'm talking about when using multiple sticks. Some errors may not even come up, testing each stick individually is the best route. It's obviously the new stick he plopped in there causing the error. Most RAM manufacturer's come with lifetime warranties anyways. But yes you're right 1 error is too many, usually if a stick is bad it will start popping of several addresses at a time. You don't agree that 35 hours is complete overkill?