A dump file is a snapshot of an app at the point in time the dump is taken. It shows what process was executing and what modules were loaded. It shows what process was executing and what modules were loaded. So whenever the application is released, we should keep a copy of the symbol files for future debugging. Analyze the Dump File. Press Ctrl+D or File->Open Dump File to load the dump file. Call the analyze command once the dump file loaded.
- Analyze the Dump File. From the STACK TEXT we can see OnOK called TestUnHandledException, TestUnHandledException called _tcsncpy, and finally crashed at msvcrt::mbsnbcpy. Additionally, WinDbg also tells us the file name is CrashRptTestDlg.cpp and line number is 178 (the line number is approximate, as optimization of release version).
- We've updated WinDbg to have more modern visuals, faster windows, a full-fledged scripting experience, with the easily extensible debugger data model front and center. WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows you're used to will still work as they did before.
- WinDbg doesn't load symbol file that is created using the same source but built at a differnt time than the original. Ask Question 3. We released a product (C#.NET library) and didn't store the pdb file of the library, assuming that we can always generate symbol files using the same source code. Windbg refuses to load symbols for dump.
- Windbg BSOD crash Minidump files help needed. Loading Kernel Symbols. Dump files are usually found at c: windows minidump. You may need to change your settings in Windows to be able to see the files. To show hidden files select the keyboard shortcut Win+S.
WinDbg Preview is a brand-new version of WinDbg with more modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center. WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows you're used to will still work as they did before.
For the latest news, tips, and tricks from the debugger dev team, refer to the debugger tools team blog.https://blogs.msdn.microsoft.com/windbg/
Major Features of WinDbg Preview
Here's some of the most notable things that have changed or are new.
General features
- Easier Connection Setup and Recall - The WinDbg Preview includes the ability to recall previous session configuration information.
- Easy feedback channel - Your feedback will guide the development effort going forward. For more information, see Providing Feedback
- Dump file processor detection -Auto-detects processor architecture for easier managed debugging.
- Performance Improvements Windows now load asynchronously and can be canceled - When you run another command, WinDbg Preview will stop the loading of your locals, watch, or other windows.
Windowing improvements
- Disassembly Window Improvements - The disassembly window is also improved, the highlight of the current instruction remains where it is when you scroll.
- Memory window improvements - The memory window has highlighting and improved scrolling.
- Locals and watch data model visualization - The locals and watch windows are both based off of the data model that is used by the dx command. This means the locals and watch windows will benefit from any NatVis or JavaScript extensions you have loaded, and can even support full LINQ queries, just like the dx command.
- Logs - This is a under the covers log of the WinDbg Preview internals. It can be viewed for troubleshooting or to monitor long running processes.
For more information, see WinDbg Preview - View menu.
- Command window - Use the command window provides easy access to toggle DML and clear the debugger command window. All current debugger commands are compatible with and continue to work in WinDbg Preview.
Dark theme
Use File > Settings to enable the dark theme.
Ribbon Quick Access
Just pin the buttons you use the most and you can collapse the ribbon to save screen real estate.
Source Window
The source window has been updated to be much more in line with modern editors.
Highlighting
The command window has two new highlighting features. Selecting any text will give a subtle highlight to any other instances of that text. You can then hit 'Highlight/Un-highlight' or Ctrl+Alt+H to persist the highlighting.
Better keyboard navigation
Just hit Ctrl+Tab and you can easily navigate between windows with just your keyboard.
Integrated Time Travel Debugging (TTD)
If you need a TTD trace of your application, just check the 'Record process with Time Travel Debugging' box when launching or attaching. WinDbgNext will set it up for TTD and open the trace when you're done recording.
For more information, see Time Travel Debugging - Overview.
Debugging App packages
Debugging your universal app or background task is now a single click.
For more information, see Launch App Package.
Attach to a process
The attach dialog is faster, more detailed, and is easier to use.
Enhanced breakpoint tracking
- Enable/Disable breakpoints - The breakpoints window shows all your current breakpoints and provides easy access to enabling and disabling them.
- Hit count - The breakpoint window keeps a running total of each time the breakpoint is hit.
For more information, see Breakpoints.
Analyze Dump File Windbg
Enhanced data model support
- Built in data model support - WinDbg Preview is written with built in data model support and the data model is available through out the debugger.
- Model window - The model window gives you an expandable and browsable version of ‘dx’ and ‘dx -g’, letting you create powerful tables on-top of your NatVis, JavaScript, and LINQ queries.
For more information, see WinDbg Preview - Data model.
New scripting development UI
- Script development UI - There is now a purpose built scripting window to make developing JavaScript and NatVis scripts easier, with error highlighting and IntelliSense.
For more information, see WinDbg Preview - Scripting.
Backwards compatibility
Because the underling debugger engine is the same, all of the previous debugger commands and debugger extensions continue to work.
Debugging Dump File Windbg
Providing feedback
Your feedback will help guide WinDbg's development going forward.
- If you have feedback such as a feature that you really want to see or a bug that makes something difficult, use the Feedback Hub.
Videos
Watch these episodes of the Defrag Tools show to see Windbg Preview in action.
- Defrag Tools #182 - Tim, Chad, and Andy go over the basics of WinDbg Preview and some of the features.
- Defrag Tools #183 - Nick, Tim, and Chad use WinDbg Preview and go over a quick demo.
- Defrag Tools #184 - Bill and Andrew walk through the scripting features in WinDbg Preview.
- Defrag Tools #185 - James and Ivette provide and introduction to Time Travel Debugging.
- Defrag Tools #186 - James and JCAB covers advanced Time Travel Debugging.
Next Steps
For information on what's new in the most recent release, see WinDbg Preview - What's New.
Sciologness.com is not responsible in any way for the performance of or issues caused by any third-party drivers.Drivers may also be available for free directly from manufacturers' websites. Drivers are the property and the responsibility of their respective manufacturers, and may also be available for free directly from manufacturers' websites.
The Sciologness.com™ agent utility uses data collection technology to conveniently update multiple PC drivers. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Review these topics to install and configure WinDbg Preview.
These topics describe how to get connected to the environment that you want to debug.
These topics describe some common tasks, organized by the menu tabs.
---
I had a blue screen of death & ive been trying to figure out what it was. So at first i couldnt even open the minidump file i had to transfer permision to myself (dont even know how i did that). But when i opned it ,it was just a bunch of symbols and numbers. So i downloaded the Windbg Tool to debug it and this is what i got. I have no clue what im doing could use some help
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:WindowsMinidump121916-9062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff800`9601e000 PsLoadedModuleList = 0xfffff800`96323060
Debug session time: Mon Dec 19 12:39:19.780 2016 (UTC - 5:00)
System Uptime: 0 days 19:02:25.502
Loading Kernel Symbols
................................
................................
................................
..
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe70fbcb96060, ffffac80c49aa960, ffffe70fbedaf910}
Probably caused by : pci.sys
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe70fbcb96060, Physical Device Object of the stack
Arg3: ffffac80c49aa960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe70fbedaf910, The blocked IRP
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 700Z3C/700Z5C
SYSTEM_SKU: System SKUNumber
SYSTEM_VERSION: 0.1
BIOS_VENDOR: Phoenix Technologies Ltd.
BIOS_VERSION: P07ABJ
BIOS_DATE: 11/04/2013
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP700Z5C-S02UB
BASEBOARD_VERSION: FAB1
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe70fbcb96060
BUGCHECK_P3: ffffac80c49aa960
BUGCHECK_P4: ffffe70fbedaf910
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58258ce9
MODULE_NAME: pci
FAULTING_MODULE: fffff80d6dea0000 pci
CPU_COUNT: 8
CPU_MHZ: 95b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SEAN-PC
ANALYSIS_SESSION_TIME: 12-19-2016 14:00:58.0536
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_TEXT:
ffffac80`c49aa928 fffff800`96219023 : 00000000`0000009f 00000000`00000003 ffffe70f`bcb96060 ffffac80`c49aa960 : nt!KeBugCheckEx
ffffac80`c49aa930 fffff800`96218f36 : ffffe70f`bfdec230 00000000`00000002 00000000`00000001 ffffac80`c4980180 : nt!PopIrpWatchdogBugcheck+0xeb
ffffac80`c49aa990 fffff800`960814e0 : ffffe70f`bfdec268 00000000`0023ae82 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffac80`c49aa9e0 fffff800`9616b77a : ffffffff`00000000 ffffac80`c4980180 ffffac80`c498ccc0 ffffe70f`c4d227c0 : nt!KiRetireDpcList+0x440
ffffac80`c49aac60 00000000`00000000 : ffffac80`c49ab000 ffffac80`c49a5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.14393.479
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm_IMAGE_pci.sys
TARGET_TIME: 2016-12-19T17:39:19.000Z
OSBUILD: 14393
OSSERVICEPACK: 576
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-09 04:23:02
BUILDDATESTAMP_STR: 161208-2252
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.576
ANALYSIS_SESSION_ELAPSED_TIME: 562
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm_image_pci.sys
FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe70fbcb96060, Physical Device Object of the stack
Arg3: ffffac80c49aa960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe70fbedaf910, The blocked IRP
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 700Z3C/700Z5C
SYSTEM_SKU: System SKUNumber
SYSTEM_VERSION: 0.1
BIOS_VENDOR: Phoenix Technologies Ltd.
BIOS_VERSION: P07ABJ
BIOS_DATE: 11/04/2013
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP700Z5C-S02UB
BASEBOARD_VERSION: FAB1
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe70fbcb96060
BUGCHECK_P3: ffffac80c49aa960
BUGCHECK_P4: ffffe70fbedaf910
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58258ce9
MODULE_NAME: pci
FAULTING_MODULE: fffff80d6dea0000 pci
CPU_COUNT: 8
CPU_MHZ: 95b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SEAN-PC
ANALYSIS_SESSION_TIME: 12-19-2016 14:00:59.0919
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_TEXT:
ffffac80`c49aa928 fffff800`96219023 : 00000000`0000009f 00000000`00000003 ffffe70f`bcb96060 ffffac80`c49aa960 : nt!KeBugCheckEx
ffffac80`c49aa930 fffff800`96218f36 : ffffe70f`bfdec230 00000000`00000002 00000000`00000001 ffffac80`c4980180 : nt!PopIrpWatchdogBugcheck+0xeb
ffffac80`c49aa990 fffff800`960814e0 : ffffe70f`bfdec268 00000000`0023ae82 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffac80`c49aa9e0 fffff800`9616b77a : ffffffff`00000000 ffffac80`c4980180 ffffac80`c498ccc0 ffffe70f`c4d227c0 : nt!KiRetireDpcList+0x440
ffffac80`c49aac60 00000000`00000000 : ffffac80`c49ab000 ffffac80`c49a5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.14393.479
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm_IMAGE_pci.sys
TARGET_TIME: 2016-12-19T17:39:19.000Z
OSBUILD: 14393
OSSERVICEPACK: 576
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-09 04:23:02
BUILDDATESTAMP_STR: 161208-2252
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.576
ANALYSIS_SESSION_ELAPSED_TIME: 562
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm_image_pci.sys
FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:WindowsMinidump121916-9062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff800`9601e000 PsLoadedModuleList = 0xfffff800`96323060
Debug session time: Mon Dec 19 12:39:19.780 2016 (UTC - 5:00)
System Uptime: 0 days 19:02:25.502
Loading Kernel Symbols
................................
................................
................................
..
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe70fbcb96060, ffffac80c49aa960, ffffe70fbedaf910}
Probably caused by : pci.sys
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe70fbcb96060, Physical Device Object of the stack
Arg3: ffffac80c49aa960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe70fbedaf910, The blocked IRP
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 700Z3C/700Z5C
SYSTEM_SKU: System SKUNumber
SYSTEM_VERSION: 0.1
BIOS_VENDOR: Phoenix Technologies Ltd.
BIOS_VERSION: P07ABJ
BIOS_DATE: 11/04/2013
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP700Z5C-S02UB
BASEBOARD_VERSION: FAB1
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe70fbcb96060
BUGCHECK_P3: ffffac80c49aa960
BUGCHECK_P4: ffffe70fbedaf910
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58258ce9
MODULE_NAME: pci
FAULTING_MODULE: fffff80d6dea0000 pci
CPU_COUNT: 8
CPU_MHZ: 95b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SEAN-PC
ANALYSIS_SESSION_TIME: 12-19-2016 14:00:58.0536
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_TEXT:
ffffac80`c49aa928 fffff800`96219023 : 00000000`0000009f 00000000`00000003 ffffe70f`bcb96060 ffffac80`c49aa960 : nt!KeBugCheckEx
ffffac80`c49aa930 fffff800`96218f36 : ffffe70f`bfdec230 00000000`00000002 00000000`00000001 ffffac80`c4980180 : nt!PopIrpWatchdogBugcheck+0xeb
ffffac80`c49aa990 fffff800`960814e0 : ffffe70f`bfdec268 00000000`0023ae82 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffac80`c49aa9e0 fffff800`9616b77a : ffffffff`00000000 ffffac80`c4980180 ffffac80`c498ccc0 ffffe70f`c4d227c0 : nt!KiRetireDpcList+0x440
ffffac80`c49aac60 00000000`00000000 : ffffac80`c49ab000 ffffac80`c49a5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.14393.479
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm_IMAGE_pci.sys
TARGET_TIME: 2016-12-19T17:39:19.000Z
OSBUILD: 14393
OSSERVICEPACK: 576
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-09 04:23:02
BUILDDATESTAMP_STR: 161208-2252
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.576
ANALYSIS_SESSION_ELAPSED_TIME: 562
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm_image_pci.sys
FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe70fbcb96060, Physical Device Object of the stack
Arg3: ffffac80c49aa960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe70fbedaf910, The blocked IRP
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 700Z3C/700Z5C
SYSTEM_SKU: System SKUNumber
SYSTEM_VERSION: 0.1
BIOS_VENDOR: Phoenix Technologies Ltd.
BIOS_VERSION: P07ABJ
BIOS_DATE: 11/04/2013
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP700Z5C-S02UB
BASEBOARD_VERSION: FAB1
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe70fbcb96060
BUGCHECK_P3: ffffac80c49aa960
BUGCHECK_P4: ffffe70fbedaf910
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58258ce9
MODULE_NAME: pci
FAULTING_MODULE: fffff80d6dea0000 pci
CPU_COUNT: 8
CPU_MHZ: 95b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: SEAN-PC
ANALYSIS_SESSION_TIME: 12-19-2016 14:00:59.0919
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_TEXT:
ffffac80`c49aa928 fffff800`96219023 : 00000000`0000009f 00000000`00000003 ffffe70f`bcb96060 ffffac80`c49aa960 : nt!KeBugCheckEx
ffffac80`c49aa930 fffff800`96218f36 : ffffe70f`bfdec230 00000000`00000002 00000000`00000001 ffffac80`c4980180 : nt!PopIrpWatchdogBugcheck+0xeb
ffffac80`c49aa990 fffff800`960814e0 : ffffe70f`bfdec268 00000000`0023ae82 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffac80`c49aa9e0 fffff800`9616b77a : ffffffff`00000000 ffffac80`c4980180 ffffac80`c498ccc0 ffffe70f`c4d227c0 : nt!KiRetireDpcList+0x440
ffffac80`c49aac60 00000000`00000000 : ffffac80`c49ab000 ffffac80`c49a5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.14393.479
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm_IMAGE_pci.sys
TARGET_TIME: 2016-12-19T17:39:19.000Z
OSBUILD: 14393
OSSERVICEPACK: 576
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-12-09 04:23:02
BUILDDATESTAMP_STR: 161208-2252
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.576
ANALYSIS_SESSION_ELAPSED_TIME: 562
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm_image_pci.sys
FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}
Followup: MachineOwner
---------
***Post moved by the moderator to the appropriate forum category.***