Answered by:
Win 8.1 Encountering PFN_List_Corrupt BSOD while shutting down

Question
-
Hi there, starting last month my computer began experiencing PFN_List_Corrupt BSODs occasionally while shutting down. I am running Win 8.1. I tried memory search but the system says no error was found. Could someone help me with this? The DMP Files are here: http://1drv.ms/1A7pv3k
Thanks!
Monday, December 1, 2014 2:14 PM
Answers
-
- Edited by Yolanda Zhu Wednesday, December 10, 2014 7:14 AM
- Marked as answer by EMMmmmmmm Wednesday, December 17, 2014 10:13 AM
Wednesday, December 10, 2014 7:13 AM
All replies
-
Hi,
Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {9a, 218e0c, 6, 2} *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys Probably caused by : igdkmd64.sys ( igdkmd64+1c992 ) Followup: MachineOwner --------- 4: 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: 000000000000009a, Arg2: 0000000000218e0c Arg3: 0000000000000006 Arg4: 0000000000000002 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_9a CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from fffff80333a17527 to fffff8033396a1a0 STACK_TEXT: ffffd000`b29a5548 fffff803`33a17527 : 00000000`0000004e 00000000`0000009a 00000000`00218e0c 00000000`00000006 : nt!KeBugCheckEx ffffd000`b29a5550 fffff803`338691b2 : 00000002`146d2863 00000000`00000020 fffff6f0`00e56998 00000000`00002000 : nt!MiBadRefCount+0x4f ffffd000`b29a5590 fffff803`33868ea1 : 00000000`00000000 00000000`00000001 00000000`00000010 00000000`00000001 : nt!MiInsertNonPagedPoolOnSlist+0x2e2 ffffd000`b29a55f0 fffff803`33abb3d7 : 00000000`00000000 ffffc000`c13de510 ffffc000`c22e14d0 fffff800`6d4d6956 : nt!MiFreePoolPages+0x5d ffffd000`b29a5620 fffff803`33abbd0f : ffffe001`c9c61010 ffffe001`ce7027c0 00000000`00000000 00000000`00000002 : nt!ExDeferredFreePool+0x3c7 ffffd000`b29a56a0 fffff800`77301992 : 00000000`00000000 00000000`00000000 ffffe001`ce0d0000 00000000`324d4740 : nt!ExFreePoolWithTag+0x84f ffffd000`b29a5790 00000000`00000000 : 00000000`00000000 ffffe001`ce0d0000 00000000`324d4740 ffffe001`ce279bb0 : igdkmd64+0x1c992 STACK_COMMAND: kb FOLLOWUP_IP: igdkmd64+1c992 fffff800`77301992 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: igdkmd64+1c992 FOLLOWUP_NAME: MachineOwner MODULE_NAME: igdkmd64 IMAGE_NAME: igdkmd64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 52379d96 FAILURE_BUCKET_ID: 0x4E_9a_igdkmd64+1c992 BUCKET_ID: 0x4E_9a_igdkmd64+1c992 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x4e_9a_igdkmd64+1c992
The dump shows that the BSOD is probably caused by : igdkmd64.sys
It is known as Intel Graphic Kernel Mode Driver or belongs to software intel Graphic Accelerator Drivers for Windows.
I suggest you keep the latest version of the driver or software, or reinstall as a test.
Yolanda Zhu
TechNet Community SupportTuesday, December 2, 2014 7:08 AM -
Hi there,
Thank you for your reply. I've tried you suggestion and updated the driver. The system worked fine for a few days but just encountered another BSoD this morning, also due to PFN List Corruption. I've uploaded the DMP file here: http://1drv.ms/1uaCEmR
Could there be another cause? Thanks!
Monday, December 8, 2014 7:34 AM -
- Edited by Yolanda Zhu Wednesday, December 10, 2014 7:14 AM
- Marked as answer by EMMmmmmmm Wednesday, December 17, 2014 10:13 AM
Wednesday, December 10, 2014 7:13 AM