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: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000001, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.
MEMORY_CORRUPTOR: ONE_BIT
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: test.exe
LAST_CONTROL_TRANSFER: from 805230c8 to 804fae0b
STACK_TEXT:
b9affbc0 805230c8 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
b9affbf0 80511dab c0883f38 0000008f 831064e8 nt!MiDecrementShareCount+0x3a
b9affc14 805afccb 77c27101 831062f0 007ffff8 nt!MiDeleteValidAddress+0x177
b9affc34 8051384d 831062f0 83106428 831062f0 nt!MiDeleteAddressesInWorkingSet+0x65
b9affc68 805d1f99 001062f0 82a67198 c0000005 nt!MmCleanProcessAddressSpace+0x193
b9affcf0 805d207d c0000005 b9affd4c 804ffe85 nt!PspExitThread+0x621
b9affcfc 804ffe85 82a67198 b9affd48 b9affd3c nt!PsExitSpecialApc+0x23
b9affd4c 80541a7e 00000001 00000000 b9affd64 nt!KiDeliverApc+0x1af
b9affd4c 77c01ce9 00000001 00000000 b9affd64 nt!KiServiceExit2+0x3a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0112da38 00000000 00000000 00000000 00000000 0x77c01ce9