Decoding Memtest86 Results.

icabass3

Honorable
May 13, 2013
63
0
10,640
Hello everyone, I just finished running memtest86 as a last resort, and I was going to ask if someone perhaps knew what these results mean.


Symptoms : Random BSOD's {Specifically bug codes: atikmdag.sys ; Paged_File_in blabla ; PFN_LIST Corrupt ; and the list goes on.


I have done this so far

New motherboard
New Ram
Tried different graphics cards
tried different graphic drivers
tried different versions of diretx
tried different versions of Microsoft c++ dist.
re-formatted windows several times
tried another HDD
tried a different SATA cable
tried a different SATA port
tried another PSU

So, as you can see I'm basically at the end of the line. I'm thinking maybe cpu memory controller?


Here are some pictures of the Memtest86 results

IMG_20150829_194543986_HDR_zpsr7cfiyjw.jpg


IMG_20150829_215128134_zps3wwgx99m.jpg



As always, any help is appreciated.
 
Solution
Might try loosening the H60 then snug it back down screw tight, if too snug in a corner or saide it can throw the CPU out of level which will affect the MC (but I think from the Sounds of it it is the MC in your CPU :( sorry)

icabass3

Honorable
May 13, 2013
63
0
10,640
Happening on a GIGABYTE Z87-D3H AND a brand new Asus Z97A. Using Corsair Vengeance 16GB Kit. Model CMZ16GX3M4A1600C9. Corsair H60 Cooler. 750 Watt PSU. Both boards are running the latest BIOS.

If the memory controller is on the processor that was my thinking as well.

I have already done the 1 by 1 stick method on the Z87 Board. It BSOD'd whenever I added any stick of ram to the second RAM channel / dual channel slots.

Here, you can download the system perfmon /report files as well as Sysnative File collections on the minidump. For some reason, only one minidump is being displayed.

https://drive.google.com/folderview?id=0B5B6yyhmjnvGfk1Qbzlhcnh0Wk5La2pZVzRtSW1rYzVfMUJHdm1JSWpvYmtKLVQxR3FjLVk&usp=sharing
 

icabass3

Honorable
May 13, 2013
63
0
10,640
Alright, thanks guys! I'm running all of the sticks 1 by 1 through memtest86. Then I'll put a known good set of ram in the system. If they still come up bad in memtest86 I'll know it's the memory controller.