PFN_LIST_CORRUPT Windows 8.1 bsod

[yure]

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) About 2months mobo, psu the rest is about 7-8 months old (ram.cpu.gpu)
· Age of OS installation - have you re-installed the OS? upgraded to win 8.1 about 2 months ago
· CPU - Intel Core i5 3570 @ 3.40GHz
· Video Card - Intel HD Graphics (ASRock)
2047MB NVIDIA GeForce GTX 760 (EVGA)
· MotherBoard -ASRock Z77 Extreme4
· Power Supply - EVGA super nova 650 watts


· System Manufacturer -bought it from Ibuypower
· Exact model number : dunno but i upgraded a few parts a while ago since the mobo it came with died on me


· Laptop or Desktop? desktop

unfortunately the perfmon report did not work access denied
as soon a i started the computer and logged on, it went immediately to that PFN_LIST_CORRUPT then the computer restarted but it was weird since its been a while since the last bsod probably about 2 months since the last one. once the computer restarted i was able to log in and its hasn't bsod so far

 

[Jared]

Hello, my name is Jared and I'll try to solve your BSOD problems.

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
[COLOR="#FF0000"]Arg1: 000000000000009a[/COLOR], 
Arg2: 000000000035f31b
Arg3: 0000000000000006
Arg4: 0000000000000002

Here we have our 0x4E bugcheck, the first parameter is 0x9a meaning a driver tried to free pages which were locked for an I/O.

ffffd000`325bac08 fffff803`297fd353 : 00000000`0000004e 00000000`0000009a 00000000`0035f31b 00000000`00000006 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR]
ffffd000`325bac10 fffff803`2969ac02 : 00000003`29a43863 00000000`00000020 fffff6f0`00a73220 ffffe001`478265e0 : [COLOR="#FF8C00"]nt!MiBadRefCount+0x4f[/COLOR]
ffffd000`325bac50 fffff803`2969a8f1 : 891fd0fc`3057c801 00000000`00000001 00000000`00000010 00000000`00000001 : [COLOR="#FF8C00"]nt!MiInsertNonPagedPoolOnSlist+0x2e2[/COLOR]
ffffd000`325bacb0 fffff803`2989b3d9 : 00000000`00000000 00000000`00001000 00000000`00000010 ffffd000`325bad4c : [COLOR="#FF0000"]nt!MiFreePoolPages+0x5d[/COLOR]
ffffd000`325bace0 fffff803`2989ca24 : ffffe001`4c898c00 ffffe001`488c5930 00000000`00000000 00000000`00000002 : [COLOR="#FF0000"]nt!ExDeferredFreePool+0x3c9[/COLOR]
ffffd000`325bad60 fffff801`95b5f599 : 00000000`c1d01f41 fffff801`95c4c6ff ffffe001`47805000 ffffe001`4d52564e : [COLOR="#FF0000"]nt!ExFreePoolWithTag+0x744[/COLOR]
ffffd000`325bae30 00000000`c1d01f41 : fffff801`95c4c6ff ffffe001`47805000 ffffe001`4d52564e 00000000`00000020 : [COLOR="#FF0000"]nvlddmkm+0xd7599[/COLOR]
ffffd000`325bae38 fffff801`95c4c6ff : ffffe001`47805000 ffffe001`4d52564e 00000000`00000020 fffff801`95c46a29 : 0xc1d01f41
ffffd000`325bae40 ffffe001`47805000 : ffffe001`4d52564e 00000000`00000020 fffff801`95c46a29 00000000`00000000 : [COLOR="#FF0000"]nvlddmkm+0x1c46ff[/COLOR]
ffffd000`325bae48 ffffe001`4d52564e : 00000000`00000020 fffff801`95c46a29 00000000`00000000 fffff801`00000001 : 0xffffe001`47805000
ffffd000`325bae50 00000000`00000020 : fffff801`95c46a29 00000000`00000000 fffff801`00000001 00000000`00000001 : 0xffffe001`4d52564e
ffffd000`325bae58 fffff801`95c46a29 : 00000000`00000000 fffff801`00000001 00000000`00000001 00000000`40020000 : 0x20
ffffd000`325bae60 00000000`00000000 : fffff801`00000001 00000000`00000001 00000000`40020000 ffffe001`488c5940 : [COLOR="#FF0000"]nvlddmkm+0x1bea29[/COLOR]

Here we can see some user mode functions with the Kernel Nvidia driver trying to free pages, it then tries to add pages to a singly linked list when we discover a bad page frame number list followed by the bugcheck.
I'm not sure why it tries to insert a nonpaged memory pool into a singly linked list...
It is a Memory Management Internal routine so that is why it isn't documented and hence the reason I can't find much about it.

Our Nvidia driver is up to date, you could try a new beta driver or rolling back to an older driver.

0: kd> [COLOR="#008000"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff801`95a88000 fffff801`966ec000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="#FF0000"]Tue May 20 00:08:44 2014[/COLOR] (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4