Loading Dump File [C:\Windows\Minidump\070817-10515-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 15063 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`cf67e000 PsLoadedModuleList = 0xfffff801`cf9ca5a0 Debug session time: Sat Jul 8 09:41:55.158 2017 (UTC - 4:00) System Uptime: 0 days 0:14:56.772 Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck EA, {ffffc009552f17c0, 0, 0, 0} *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* THREAD_STUCK_IN_DEVICE_DRIVER (ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger is connected and running when watchdog detects a timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx() and detailed message including bugcheck arguments will be printed to the debugger. This way we can identify an offending thread, set breakpoints in it, and hit go to return to the spinning code to debug it further. Because KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck information in this case. The arguments are already printed out to the kernel debugger. You can also retrieve them from a global variable via "dd watchdog!g_WdBugCheckData l5" (use dq on NT64). On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is interrupted by hardware interrupt and ISR or DPC routine is running at the time of the bugcheck (this is because the timeout's work item can be delivered and handled on the second CPU and the same time). If this is the case you will have to look deeper at the offending thread's stack (e.g. using dds) to determine spinning code which caused the timeout to occur. Arguments: Arg1: ffffc009552f17c0, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object. Arg3: 0000000000000000, Pointer to offending driver name. Arg4: 0000000000000000, Number of times this error occurred. If a debugger is attached, this error is not always fatal -- see DESCRIPTION below. On the blue screen, this will always equal 1. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.15063.413 (WinBuild.160101.0800) DUMP_TYPE: 2 DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_P1: ffffc009552f17c0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: 552f17c0 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT CPU_COUNT: 4 CPU_MHZ: daa CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3c CPU_STEPPING: 3 CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0xEA PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-4T6O434 ANALYSIS_SESSION_TIME: 07-08-2017 12:02:26.0064 ANALYSIS_VERSION: 10.0.14321.1024 amd64fre LAST_CONTROL_TRANSFER: from fffff80e34805f5b to fffff801cf7ea3f0 STACK_TEXT: ffffd181`e21ffdd8 fffff80e`34805f5b : 00000000`000000ea ffffc009`552f17c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffd181`e21ffde0 fffff80e`3480602e : ffffd181`e21ffeb8 fffff80e`37e18890 ffffd181`e21ffeb8 ffffd181`e21fffa0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f ffffd181`e21ffe50 fffff80e`37db6970 : ffffc009`54461000 00000000`00000000 ffffd181`e21fffa0 fffff80e`37e1887c : dxgkrnl!TdrTimedOperationDelay+0xbe ffffd181`e21ffe90 ffffc009`54461000 : 00000000`00000000 ffffd181`e21fffa0 fffff80e`37e1887c 00000000`00002710 : atikmdag+0x56970 ffffd181`e21ffe98 00000000`00000000 : ffffd181`e21fffa0 fffff80e`37e1887c 00000000`00002710 00000000`00000028 : 0xffffc009`54461000 STACK_COMMAND: .thread 0xffffc009552f17c0 ; kb THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17 THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94 FOLLOWUP_IP: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f fffff80e`34805f5b cc int 3 FAULT_INSTR_CODE: cccccccc SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 7f24be34 IMAGE_VERSION: 10.0.15063.409 FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys TARGET_TIME: 2017-07-08T13:41:55.000Z OSBUILD: 15063 OSSERVICEPACK: 413 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2017-06-03 04:53:36 BUILDDATESTAMP_STR: 160101.0800 BUILDLAB_STR: WinBuild BUILDOSVER_STR: 10.0.15063.413 ANALYSIS_SESSION_ELAPSED_TIME: 4ee ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8} Followup: MachineOwner ---------