Memtest errors. System stable.

Hi
First my pc:
4790 stock
Corsair 750 RM
ram:
Corsair Vengeance Low Profile 2x4GB 1600MHz, DDR3, CL(9-9-9-24), XMP White (CML8GX3M2A1600C9W)
Mobo:Asus Sabertooth Z79 Mark2

So. Overall my system is stable 24h. I can run Prime 95 Blend for 10 hours without errors. SuperPi without errors. Games are stable.
But today i tested Memtest86. And on first passes shows 34 errors. So trying to reproduce errors i run again Memtest 86 and now its running 4 hour without errors. And i have a question. Can i trust to memtest 86? Why on my first run he showed 34 errors on first tests, but now i run again memtest and he is passing now 4 hours without errors. Can somebody explain me that?
I currently have a system that passes 12 hour prime tests consistently and handles intense gaming with ease! But sometimes will not complete a memtest pass without many errors at start.

sew333 said:

Hi
First my pc:
4790 stock
Corsair 750 RM
ram:
Corsair Vengeance Low Profile 2x4GB 1600MHz, DDR3, CL(9-9-9-24), XMP White (CML8GX3M2A1600C9W)
Mobo:Asus Sabertooth Z79 Mark2

So. Overall my system is stable 24h. I can run Prime 95 Blend for 10 hours without errors. SuperPi without errors. Games are stable.
But today i tested Memtest86. And on first passes shows 34 errors. So trying to reproduce errors i run again Memtest 86 and now its running 4 hour without errors. And i have a question. Can i trust to memtest 86? Why on my first run he showed 34 errors on first tests, but now i run again memtest and he is passing now 4 hours without errors. Can somebody explain me that?
I currently have a system that passes 12 hour prime tests consistently and handles intense gaming with ease! But sometimes will not complete a memtest pass without many errors at start.

Click to expand...

Yes, trust Memtest86.
Also, have you overclocked the RAM at all?
Try bumping the RAM voltage to 1.65 volts and see if it fails.

Why sometimes i have errors after 5 minutes of testing and sometimes i can pass 10 hours without errors. ?

sew333 said:

Why sometimes i have errors after 5 minutes of testing and sometimes i can pass 10 hours without errors. ?

Click to expand...

That I don't know.
Are you forcing SMP mode in memtest? (Forcing memtest to use all cores)

Cold boot and re-boot will make a difference on errors when testing.
BitRott test will almost always fail. Disregard it.

If PC is stable in everything you do then I wouldn't worry about Memtest86. I don't know what version are you using but latest are sometimes showing errors without special reason, sometimes just after start. There is safe mode but it's not loading memory controller much.

if I run memtest and get an multiple errors within a minute. Then run memtest the next night with the same ram, and run error free for 12+ hours, whats up with that?

Here is a log:
3 days ago i get that errors:
2015-04-18 16:14:35 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBF64, Expected: EFEFEFEF, Actual: EFFFEFEF
2015-04-18 16:14:36 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBF24, Expected: EFEFEFEF, Actual: EFCBEFEF
2015-04-18 16:14:37 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBC24, Expected: EFEFEFEF, Actual: EFF7EFEF
2015-04-18 16:14:39 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBB24, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:14:40 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DBAE4, Expected: EFEFEFEF, Actual: EFEBEFEF
2015-04-18 16:14:41 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB9A4, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:14:42 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB464, Expected: EFEFEFEF, Actual: EFEEEFEF
2015-04-18 16:14:44 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DB424, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:14:45 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAFA4, Expected: EFEFEFEF, Actual: EF67EFEF
2015-04-18 16:14:46 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAA64, Expected: EFEFEFEF, Actual: EF77EFEF
2015-04-18 16:14:47 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DAA24, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:14:49 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA564, Expected: EFEFEFEF, Actual: EF25EFEF
2015-04-18 16:14:50 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA4E4, Expected: EFEFEFEF, Actual: EFE3EFEF
2015-04-18 16:14:51 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA0E4, Expected: EFEFEFEF, Actual: EFEBEFEF
2015-04-18 16:14:53 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4DA0A4, Expected: EFEFEFEF, Actual: EFE9EFEF
2015-04-18 16:14:54 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9FE4, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:14:55 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9CA4, Expected: EFEFEFEF, Actual: EFE8EFEF
2015-04-18 16:14:56 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D98A4, Expected: EFEFEFEF, Actual: EFE1EFEF
2015-04-18 16:14:58 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D97E4, Expected: EFEFEFEF, Actual: EFDBEFEF
2015-04-18 16:14:59 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D9564, Expected: EFEFEFEF, Actual: EFECEFEF
2015-04-18 16:15:00 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D94E4, Expected: EFEFEFEF, Actual: EF8DEFEF
2015-04-18 16:15:01 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8F64, Expected: EFEFEFEF, Actual: EFC7EFEF
2015-04-18 16:15:03 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8F24, Expected: EFEFEFEF, Actual: EFFFEFEF
2015-04-18 16:15:04 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8EA4, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:15:05 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8C64, Expected: EFEFEFEF, Actual: EFCFEFEF
2015-04-18 16:15:06 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8C24, Expected: EFEFEFEF, Actual: EF6DEFEF
2015-04-18 16:15:08 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8B24, Expected: EFEFEFEF, Actual: EFA7EFEF
2015-04-18 16:15:09 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8AE4, Expected: EFEFEFEF, Actual: EFEDEFEF
2015-04-18 16:15:10 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8824, Expected: EFEFEFEF, Actual: EF39EFEF
2015-04-18 16:15:12 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8764, Expected: EFEFEFEF, Actual: EFBFEFEF
2015-04-18 16:15:13 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8724, Expected: EFEFEFEF, Actual: EFCEEFEF
2015-04-18 16:15:14 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D86E4, Expected: EFEFEFEF, Actual: EFB7EFEF
2015-04-18 16:15:15 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8364, Expected: EFEFEFEF, Actual: EFE7EFEF
2015-04-18 16:15:17 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8324, Expected: EFEFEFEF, Actual: EF6EEFEF
2015-04-18 16:15:18 - [MEM ERROR - Data] Test: 4, CPU: 0, Address: 17E4D8064, Expected: EFEFEFEF, Actual: EF23EFEF


I am using Memtest86 6.0
http://www.memtest86.com/download.htm

Is this normal? After 100% finished each test TIME just stops for a couple of seconds. And after few seconds time is running again on beggining on new test.


I explain:
It locks up on 0% for 5 second and its running again.

Try memtest 5.01..

Mr.Scott said:

Cold boot and re-boot will make a difference on errors when testing.
BitRott test will almost always fail. Disregard it.

Click to expand...

Mr.Scott what did you mean by this? Should you test on a cold boot or a re-boot?
And what is a BitRott test?

GearingMass said:

Mr.Scott what did you mean by this? Should you test on a cold boot or a re-boot?
And what is a BitRott test?

Click to expand...

You test on a re-boot. A cold boot is far more likely to produce errors because, like a car, it's not warmed up to operating temp.
This is BitRot.
http://en.wikipedia.org/wiki/Data_degradation
Particularly, decay of data in memory.
Currently Memtest86+ 6.0 runs a default Bit Rot test. (I can't remember which one). It almost never is error free. It can be disabled though.

Mr.Scott said:

You test on a re-boot. A cold boot is far more likely to produce errors because, like a car, it's not warmed up to operating temp.
This is BitRot.
http://en.wikipedia.org/wiki/Data_degradation
Particularly, decay of data in memory.
Currently Memtest86+ 6.0 runs a default Bit Rot test. (I can't remember which one). It almost never is error free. It can be disabled though.

Click to expand...

Thanks!

Actually, my computer has been failing to boot about 5% of the time, and when it does the MB throws out a memory-related error code. I'm thinking I need to run memtest86+ to see if it's faulty memory sticks (I never did this when I first built it) -- should I disable the Bit Rot test when I go to do that?

Test 10 is Bit Rot test. Disable or just ignore it.

Mr.Scott said:

Test 10 is Bit Rot test. Disable or just ignore it.

Click to expand...

So, these results are meaningless and erroneous, or what?

Is there a situation in which they are accurate?

Thanks!

I'm sure they're not meaningless, but if that's the only test you error on and your computer runs fine, then I would say that your ram is basically OK.
That's just my opinion though.
I have sets of ram that fail no other test but Bit Rot and they run fine enough for daily duties, gaming, and extreme benching conditions without error. Take it for what it's worth.

I've read that MemTest86 ver. 6.00 is buggy, but with my old systems it seemed to work fine and showed no errors except when I ran its row hammer test (Wiki article)
on Kingston HyperX (speed or voltage didn't matter, chips may have been Micron or Nanya), but Samsung Green passed that test.

MemTest86 v6 documentation also says testing memory by running more than one CPU core at a time can cause spurious errors, but I didn't see that with either type of memory.

No errors during different periods of testing could indicate a bad connection. I had one system crash if a DIMM was touched even the slightest, and it it turned out to be lint in the socket, while with another system some of the socket contacts were tarnished.