BSOD with no apparent cause, PFN list corrupt.

[Pureauthor]

I randomly BSOD'd due to 'PFN_LIST_CORRUPT' and I can't find any apparent reason. Poking around on Google made me realize it may be due to a bad driver, but I lack the technical expertise to figure out which driver it is.

Anyway, I ran to SF Diagnostic Tool as requested and uploaded the info. Also attached is a Notepad document containing information I was able to pull from Driver Verifier and WinDbg. I hope it proves useful in figuring out what went wrong and how to fix it ASAP.

Thanks in advance.

 

[Arc]

Update Broadcom NetLink (TM) Gigabit Ethernet Driver. It is too old.

fffff880`07d38000 fffff880`07d89000   k57nd60a   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\k57nd60a.sys
[COLOR=Red]    Image name: k57nd60a.sys
    Timestamp:        Fri Oct 16 15:59:38 2009[/COLOR] (4AD84B12)
    CheckSum:         00059567
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from Ethernet NIC Driver Downloads | Broadcom

Update Intel(R) Centrino(R) Advanced-N 6200 AGN driver. It is old, too.

fffff880`0767e000 fffff880`07d2b000   NETw5s64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\NETw5s64.sys
[COLOR=Red]    Image name: NETw5s64.sys
    Timestamp:        Wed Sep 16 01:10:39 2009[/COLOR] (4AAFEDB7)
    CheckSum:         006A6E93
    ImageSize:        006AD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from https://downloadcenter.intel.com/Default.aspx

Let us know how th computer is running after doing these.
____________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, bef09, 1, 0}

Probably caused by : afd.sys ( afd!AfdTLCompleteBufferUserReceive+159 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000000bef09, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003288a83 to fffff800032c0c00

STACK_TEXT:  
fffff880`0dcd6c28 fffff800`03288a83 : 00000000`0000004e 00000000`00000007 00000000`000bef09 00000000`00000001 : nt!KeBugCheckEx
fffff880`0dcd6c30 fffff800`03333446 : fffff880`009ea180 fffffa80`03dfee01 00000000`00000008 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x165e6
fffff880`0dcd6c70 fffff800`032c43e8 : 00000000`0000000c 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x368d5
fffff880`0dcd6d00 fffff880`06f138b9 : 00000000`00000000 fffffa80`03dfee02 fffffa80`0f2584d0 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff880`0dcd6df0 fffff880`0184fbb7 : fffff880`0dcd6ff8 fffffa80`0dbaa1a0 00000000`00000000 fffff880`0dcd6fb0 : afd!AfdTLCompleteBufferUserReceive+0x159
fffff880`0dcd6ef0 fffff880`01866625 : 00000006`eac3c9e6 fffffa80`0e2946b0 fffffa80`0e2946b0 fffffa80`0e929680 : tcpip!TcpSatisfyReceiveRequests+0x4a7
fffff880`0dcd71d0 fffff880`018651d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpDeliverDataToClient+0x105
fffff880`0dcd7350 fffff880`0186379b : 00000000`00000000 fffffa80`07fa9030 fffff880`051f90bc 00000000`00000000 : tcpip!TcpDeliverReceive+0xa7
fffff880`0dcd7450 fffff880`01862d65 : fffff880`0dcd77e8 00000000`00000000 fffffa80`0e2946b0 00000000`00000010 : tcpip!TcpTcbFastDatagram+0x3ab
fffff880`0dcd74e0 fffff880`0186269a : fffffa80`04b7a490 fffff880`0185b544 fffffa80`049fc628 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5
fffff880`0dcd7690 fffff880`01863c3b : fffff880`051f90c4 fffffa80`04b67000 00000000`00000000 fffff880`0dcd7a00 : tcpip!TcpMatchReceive+0x1fa
fffff880`0dcd77e0 fffff880`0185bbd7 : fffffa80`04b7a490 fffffa80`04a38f07 fffffa80`00008ad2 00000000`00008ad2 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`0dcd78b0 fffff880`0185b74a : 00000000`00000000 fffff880`0196e9a0 fffff880`0dcd7a70 fffffa80`0e9e3700 : tcpip!IppDeliverListToProtocol+0x97
fffff880`0dcd7970 fffff880`0185ad49 : fffff880`0196e9a0 fffffa80`0ea4f300 fffff880`0dcd7aa0 fffff880`0dcd7a60 : tcpip!IppProcessDeliverList+0x5a
fffff880`0dcd7a10 fffff880`018589ef : fffffa80`acfe09c7 fffff880`0196e9a0 fffff880`0196e9a0 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`0dcd7af0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x64f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdTLCompleteBufferUserReceive+159
fffff880`06f138b9 f0834530ff      lock add dword ptr [rbp+30h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  afd!AfdTLCompleteBufferUserReceive+159

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4efa9418

FAILURE_BUCKET_ID:  X64_0x4E_7_afd!AfdTLCompleteBufferUserReceive+159

BUCKET_ID:  X64_0x4E_7_afd!AfdTLCompleteBufferUserReceive+159

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

 

[Pureauthor]

All right, thanks for you help. I updated the Drivers like you said.

Since this crash was apparently random, I can't tell for certain if it fixed the issue for a while, so should I mark it as Solved for the time being or wait?

 

[Arc]

Wait and observe the situation. Report us after 4 days or the occurrence of next BSOD, whichever is earlier.