BSODs PNF_LIST_CORRUPTION and more.

Spuuse · 29 Jan 2014

Hello!

so i got some blue screens now. I have tried everything what i can do :) I have installed os again. Tested different OS and still got blue screens.
Sometimes it just blue screen while i'm just normally surfing in internet and often while im playing BF4 or AC4 sometimes while playing heartstone. PC is new. i have runned memtest just like 2 passes on both sticks and no errors. i can't keep my pc on nights because my cpu cooler makes terrible noice

All temps are okey. CPU maximum temp 65 and GPU 70
I have also checked my HDD and problems. All drivers are up to date. i think.

Arc · 29 Jan 2014

Hi Spuuse.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Uninstall the display driver in full. Then clean up any possible leftover. Then install Version 13.9 only.
It is not you only, but many a people are having issues with the latest AMD display driver.

Code:

fffff880`079b97f8  fffff880`11f31c97Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xa0c97
-----------------------------------------------------------------------------------------------
fffff880`03e00000 fffff880`03ea0000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013 (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
__________________________________________________________________________________________

Code:

BugCheck 109, {a3a039d8989cc672, b3b7465eeb199878, fffff80002e34ed1, 1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+53350 )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 4E, {99, 80faa, 2, 87aa9}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 1000007E, {ffffffffc0000005, fffff880045b157a, fffff880079ba598, fffff880079b9e00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e )

Followup: MachineOwner
---------

Spuuse · 29 Jan 2014

Thanks for answering!

Lol i thought that i was installed all updates but no

And im going to install that driver what you suggested now. and i have no clocks. expect GPU is factory clocked. but if i remember right i did memtest sometime ago and had 2 errors there. i thought that was not bad thing

But i will do that memtest again tonight if i can. and i have done gpu stress test and everything was okey. tempatures was something like 76 celsius.

Arc · 30 Jan 2014

Spuuse said:

but if i remember right i did memtest sometime ago and had 2 errors there. i thought that was not bad thing

But i will do that memtest again tonight if i can.

No, take it seriously. Because a single error is enough to rule out the RAM as bad and failing; and with a failing RAM, the computer may BSOD anytime. No other steps will be of any good till the RAM issue will be there.

Spuuse · 30 Jan 2014

Okey. There was 20 errors in 6 passes. New memory and faulty stick... Bad thing is that i can't maybe return sticks because i ordered it from germany..

Arc · 30 Jan 2014

Spuuse said:

Okey. There was 20 errors in 6 passes. New memory and faulty stick... Bad thing is that i can't maybe return sticks because i ordered it from germany..

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

Spuuse · 30 Jan 2014

Okey now i have tested both sticks in same slot. Stick number one no errors. Stick number two, errors. do i have to do this to all or is this enough?

Arc · 30 Jan 2014

Enough!

You know what to do now :)