Verifier drivers NOT provided by Microsoft (BSOD) igdkmd64
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091214-9296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
Machine Name:
Kernel base = 0xfffff803`1a485000 PsLoadedModuleList = 0xfffff803`1a74f350
Debug session time: Fri Sep 12 09:45:20.195 2014 (UTC + 2:00)
System Uptime: 0 days 0:08:19.959
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 116, {ffffe0019ed942a0, fffff8016d4fb0d0, ffffffffc0000001, 3}
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** 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+c0d0 )
Followup: MachineOwner
---------
7: kd> !analyse -v
No export analyse found
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe0019ed942a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8016d4fb0d0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
igdkmd64+c0d0
fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`32e90788 fffff801`6d1cbfac : 00000000`00000116 ffffe001`9ed942a0 fffff801`6d4fb0d0 ffffffff`c0000001 : nt!KeBugCheckEx
ffffd000`32e90790 fffff801`6d1bf3a2 : fffff801`6d4fb0d0 ffffe001`9865f540 ffffe001`9865f600 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`32e907d0 fffff801`6d1cb8b2 : ffffe001`9ed901a0 00000000`00000087 ffffe001`9ed942a0 00000000`00000000 : dxgkrnl!DXGADAPTER:
repareToReset+0x152
ffffd000`32e90820 fffff801`6d277644 : ffffe001`9ed942a0 ffffd000`32e908c9 00000000`00000000 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x1be
ffffd000`32e90850 fffff801`6d2aa3fa : 00000000`00000008 ffffd000`32e90950 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x3e4
ffffd000`32e90930 fffff801`6d263ba8 : ffffffff`ff676980 00000000`00000000 ffffd000`32e90ac0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x1868a
ffffd000`32e909c0 fffff801`6d29ed4a : ffffe001`9cfa2000 ffffe001`9cfa2000 ffffe001`9dc67a20 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
ffffd000`32e90b70 fffff801`6d29ed1d : ffffe001`9cfa2000 00000000`00000080 ffffe001`9cfdd880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`32e90bc0 fffff803`1a55e514 : fffff803`1a7d2a00 ffffe001`9cfdd880 ffffd000`32e90c90 fffff803`1a5dc07d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`32e90c00 fffff803`1a5df2c6 : fffff803`1a76b180 ffffe001`9cfdd880 fffff803`1a7d2a00 ffffc001`7524abe0 : nt!PspSystemThreadStartup+0x58
ffffd000`32e90c60 00000000`00000000 : ffffd000`32e91000 ffffd000`32e8b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd64+c0d0
fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: igdkmd64+c0d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53e8f12b
FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_vrf_image_igdkmd64.sys
FAILURE_ID_HASH: {3e1b97eb-0b23-2ef6-99fb-38dcc07b5a62}
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe0019ed942a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8016d4fb0d0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
igdkmd64+c0d0
fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
ffffd000`32e90788 fffff801`6d1cbfac : 00000000`00000116 ffffe001`9ed942a0 fffff801`6d4fb0d0 ffffffff`c0000001 : nt!KeBugCheckEx
ffffd000`32e90790 fffff801`6d1bf3a2 : fffff801`6d4fb0d0 ffffe001`9865f540 ffffe001`9865f600 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffd000`32e907d0 fffff801`6d1cb8b2 : ffffe001`9ed901a0 00000000`00000087 ffffe001`9ed942a0 00000000`00000000 : dxgkrnl!DXGADAPTER:
repareToReset+0x152
ffffd000`32e90820 fffff801`6d277644 : ffffe001`9ed942a0 ffffd000`32e908c9 00000000`00000000 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x1be
ffffd000`32e90850 fffff801`6d2aa3fa : 00000000`00000008 ffffd000`32e90950 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x3e4
ffffd000`32e90930 fffff801`6d263ba8 : ffffffff`ff676980 00000000`00000000 ffffd000`32e90ac0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x1868a
ffffd000`32e909c0 fffff801`6d29ed4a : ffffe001`9cfa2000 ffffe001`9cfa2000 ffffe001`9dc67a20 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
ffffd000`32e90b70 fffff801`6d29ed1d : ffffe001`9cfa2000 00000000`00000080 ffffe001`9cfdd880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`32e90bc0 fffff803`1a55e514 : fffff803`1a7d2a00 ffffe001`9cfdd880 ffffd000`32e90c90 fffff803`1a5dc07d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`32e90c00 fffff803`1a5df2c6 : fffff803`1a76b180 ffffe001`9cfdd880 fffff803`1a7d2a00 ffffc001`7524abe0 : nt!PspSystemThreadStartup+0x58
ffffd000`32e90c60 00000000`00000000 : ffffd000`32e91000 ffffd000`32e8b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd64+c0d0
fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: igdkmd64+c0d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53e8f12b
FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_vrf_image_igdkmd64.sys
FAILURE_ID_HASH: {3e1b97eb-0b23-2ef6-99fb-38dcc07b5a62}
Followup: MachineOwner
---------