[SOLVED] PFN LIST CORRUPT BSOD - Windows 8.1 x64

Y

yure

Member
Joined
Jul 28, 2014
Posts
24
· OS - Windows 8.1, 8, 7, Vista ? Windows 8.1
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 8
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
· Age of system (hardware) everything is about a year except for the ram and gpu upgraded 5 - 6 months ago
· Age of OS installation - have you re-installed the OS? last re installed was about 8 months ago when i went from win 8 to 8.1
· CPU - Intel Core i5 3570 @ 3.40GHz
· Video Card - 4095MB NVIDIA GeForce GTX 970 (EVGA)
· MotherBoard -ASRock Z77 Extreme4
· Power Supply - EVGA super nova 650 watts


· System Manufacturer -Ibuypower
· Exact model number : dunno but i upgraded a few parts a while ago


· Laptop or Desktop? desktop





this started about 4 days ago every time im about to shut off my pc it crashes.
 

Attachments

i thought i had resolved the issue but it still happen but now it doesn't even go to a blue screen the computer just restarts . who crash me keep telling me this crashing.jpg i have run memtest for 10+hrs and there no errors so i scratch the possibility of my ram being bad i have run malware bytes just incase im infected or something but there were no hits there either, i have re installed the nvdia drivers but this keeps on happening so idk if just the card going bad (not even a year old ) the driver is just buggy or something else going and it just flags the nvdia drivers as the culprit
 
Code: 
3: kd> [COLOR=#008000].bugcheck[/COLOR]
Bugcheck code 0000004E
Arguments 00000000`000000[COLOR=#ff0000]9a[/COLOR] 00000000`0014a056 00000000`0000000[COLOR=#0000cd]6[/COLOR] 00000000`0000000[COLOR=#ff8c00]3[/COLOR]

We only going to be able to get limited information since the bugcheck is produced as a Minidump, nonetheless there is still some useful information which we can use. It appears that a driver has attempted to remove an active page from the PFN list. Let's investigate a little further.

The third parameter indicates the page state of the page which is present within physical memory. All the pages are stored in an enumeration called _MMLISTS:

Code: 
3: kd> [COLOR=#008000]dt nt!_MMLISTS[/COLOR]
   ZeroedPageList = 0n0
   FreePageList = 0n1
   StandbyPageList = 0n2
   ModifiedPageList = 0n3
   ModifiedNoWritePageList = 0n4
   BadPageList = 0n5
   ActiveAndValid = [COLOR=#ff0000]0n6[/COLOR] << Current Page State
   TransitionPage = 0n7

From the page state, we can see that the page has either been locked for I/O, or is present within the working set of a process. The reference count illustrates this point also, it can be found in the fourth parameter of the bugcheck. The page should only be eligible for removal when the reference count is 0.

We can examine the call stack, and find some other clues:

Code: 
3: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd000`3238f958 fffff802`4ea07737 nt!KeBugCheckEx
01 ffffd000`3238f960 fffff802`4e84d032 [COLOR=#ff0000]nt!MiBadRefCount+0x4f[/COLOR] << Reference Count > 0
02 ffffd000`3238f9a0 fffff802`4e84cd21 nt!MiInsertNonPagedPoolOnSlist+0x2e2
03 ffffd000`3238fa00 fffff802`4eaad3e2 [COLOR=#ff0000]nt!MiFreePoolPages+0x5d[/COLOR] << Free Page
04 ffffd000`3238fa30 fffff802`4eaadcee nt!ExDeferredFreePool+0x3e2
05 ffffd000`3238fab0 fffff801`ae7d740d [COLOR=#ff0000]nt!ExFreePoolWithTag+0x84e[/COLOR] << Free Page with Specified Pool Tag
06 ffffd000`3238fba0 00000000`00000000 [COLOR=#0000cd]nvlddmkm+0x19940d[/COLOR]

Code: 
3: kd> [COLOR=#008000]lmvm nvlddmkm[/COLOR]

start             end                 module name
fffff801`ae63e000 fffff801`af076000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=#ff0000]Wed Apr 08 21:32:37 2015[/COLOR] (55259065)
    CheckSum:         009F7AE7
    ImageSize:        00A38000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you ran the system without the nVidia drivers? Tried using Safe Mode?
 
yea i have ran the pc on safe mode to uninstall the drivers and then re installed them, i did this yesterday. a week ago the pc would bsod at the time of the shutdown phase with the pfn corrupt ist, using whocrashed it pointed to the nvidia driver so i upgraded to the newest driver since i was 3 drivers behind and i thought this was fixed but then 2 days ago the pc would restart instead of shutting down but no bsod . once i again i ran whocrashed and it pointed back to the nvidia drivers(from the pic of the previous post) so thats when i used ddu(display driver uninstaller) it goes into safe mode and completely uninstall the drivers then then boot the pc normally after i installed the drivers (which i did last night)
 
also im kinda confused that if let say the video card had gone bad, wouldnt it bsod while im playing games such as gtav that do have heavy loads , sometimes for 3+ hrs and on , rather than bsoding when im shutting off my computer
 
well its been over 24+ hrs and there was no blue screens with driver verifier on, i also did some benchmarks to my gpu to see if indeed my gpu was going bad but there no problems there but one thing i did find was that my event log was clean when driver verifier was on but when i reset and reboot the pc it would get this error .....Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188 this had to do with some file reaching the max size and cant log anymore events maybe because of my ssd settings affecting this not quite sure but other than that it seems that my issue is fix for now
 
i enabled all of these on driver verifier from the Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista
▪ Special Pool
▪ Force IRQL checking
▪ Pool Tracking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Miscellaneous Checks
▪ Power framework delay fuzzing (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)

and nothing went wrong besides the error on the event log from my previous post
 
i actually looked at my registry and the maxfile for the circular kernel context logger in set to zero so it should be unlimited right ? perhaps im getting all these errors because the way Samsung magician works with its optimization software limiting things on some options for a " maximum performance" ?
 
sigh theres no end to this... heres the newest dump, i can leave the pc all day long and it be normal, is just at the time of shutoff instead it hangs then restarts....im just about to say faulty card or can it be that "precision x" has something to do with it ? since i do use it and it runs until i shutoff the pc
 
i actually looked at my registry and the maxfile for the circular kernel context logger in set to zero so it should be unlimited right ? perhaps im getting all these errors because the way Samsung magician works with its optimization software limiting things on some options for a " maximum performance" ?​
Click to expand...

What?

Why are you messing with stuff that isn't relevant?

Code: 
Verify Flags Level 0x00000000

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks
    [ ] (0x00020000) DDI compliance checking

Anyway, for what it's worth, there's only one verifier parameter enabled.. which is automatic checks. Not entirely sure if this is due to the fact that the system crashed in a hang like way, or if you just only enabled automatic checks.

Either way, no new info.
 
sorry for the late response but i solved my problem, it was indeed the Nvidia driver 350.12, i went back to a previous driver and i have not crashed at all ( 2 days now ) so im marking this as solved. thank you patrick and xbluerobot for helping me with this error
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top