Memtest errors. System stable.

[litwicki24]

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.

 

[cadaveca]

If you reboot instead of cold boot, timings are set differently. This difference alone can account for the problem you describe.

 

[OneMoar]

if its throwing errors on the BitRott test's (which are now run by default with the latest memtest x86) ignore it
thats completely normal
run the test loop again sans bitrot tests and see what it shows

 

[litwicki24]

Why sometimes its shows errors after 5 minutes, sometimes i can pass 10 hours without errors ?!

 

[litwicki24]

Now i am 24 hours in memtest without single error.
One time i run memtest then after 5 minutes i have 34 errors. Second time when i run memtest it can go even 24 hours without single error.
And i dont change anything in bios. Can somebody explain me this? This is weird, now i am in test 24 hour no single error. But yesterday i had 34 errors after 5 minutes.

 

[litwicki24]

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?

 

[OneMoar]

you still haven't answered my question
WHAT SECTION OF THE TEST IS IT GIVING ERRORS ON ....

 

[litwicki24]

Here is a log:

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

 

[OneMoar]

that doesn't tell me what test it was running when those errors occurred
run THIS version of memtest
http://www.memtest.org/#downiso
the passmark/windows version is garbage

 

[litwicki24]

I used that memtest:

Memtest-86 6.0 So its bad version?

From here:

http://www.memtest86.com/download.htm

 

[xorbe]

Those look like real errors to me. Conditions that cause errors can come and go, making things seem stable for a while.

1600 9-9-9-24 is not aggressive. What voltage? 1T or 2T?

Games are stable.

Not per your posts on AT and GF and [H] forums ...

 

[Dan848]

I always try the least expensive and least labor intensive tasks first.

Memtest is not the problem. This sounds like a hardware problem. This can be caused by several things, however, doing the following sometimes fixes the problem:

Using a can of compressed air blow out everything around the RAM including the CPU heatsink, then remove the RAM and blow air into the empty RAM slots. Do not use air from an air compressor, Wal-Mart or computer stores sell air in cans.

Before running tests, remove and insert each stick of RAM into each socket. If there is any non-conductive or low conductive material build-up, installing and uninstalling the RAM in each slot should remove it. In other words you may have an open circuit for some reason, if so, this will correct the local problem.

The little tabs on each end of the RAM slots that hold the RAM in should snap into the grooves in the RAM [usually green] PCB, if they are lose or broken, you may have a problem there. When putting RAM in a motherboard it should be tight, sometimes very tight, if not, the slots could be too loose to grip the RAM sticks, or, the PCB on the RAM sticks may be too thin. - Just a head's up to let you know some problem areas.

Reinstall the RAM, just one stick and run tests on the computer as you did earlier. If that includes a few days of playing games, or running programs along with memtest, do it. If no problems are found put the other stick of RAM in the same slot. Do this for every RAM slot, one stick of RAM at a time. If there is a problem on the motherboard this will identify it, also, if one stick of RAM occasionally shows errors and the other stick does not there may be something wrong with that stick of RAM.

You should use canned air to clean everything out because a little dust or dirt can cause a contact to not mate up properly. Use care when removing and installing RAM. Push it streight in the slot, or from top to bottom or bottom to top if the slot is tight, no side to side movement, that can break something.


Edited for clarity