*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 1cdaf7, 0, 1ceaf7}
Probably caused by : [COLOR="Blue"]memory_corruption[/COLOR] ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
7: 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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001cdaf7, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000001ceaf7, 0
Debugging Details:
------------------