Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\NANO-PC-Thu_02_05_2015_102049_96\020515-33431-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e4a890
Debug session time: Thu Feb 5 20:42:10.313 2015 (UTC + 6:00)
System Uptime: 3 days 15:54:56.140
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 119, {1, 2c46026, 2c460bc, 2c460bb}
*** 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+168311 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 0000000002c46026
Arg3: 0000000002c460bc
Arg4: 0000000002c460bb
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: a
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
DPC_STACK_BASE: FFFFF80003FFDFB0
LAST_CONTROL_TRANSFER: from fffff8800197d22f to fffff80002c7de80
STACK_TEXT:
fffff800`03ff7668 fffff880`0197d22f : 00000000`00000119 00000000`00000001 00000000`02c46026 00000000`02c460bc : nt!KeBugCheckEx
fffff800`03ff7670 fffff880`03f93ec5 : 00000000`00000000 00000000`02c46026 00000000`00000000 00000000`02c460bc : watchdog!WdLogEvent5+0x11b
fffff800`03ff76c0 fffff880`03f941f2 : fffffa80`0c697000 fffff800`03ff77d0 fffff880`000011ac fffff800`03ff79ec : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`03ff76f0 fffff880`03f93f82 : fffff800`02c46026 00000000`00000004 fffffa80`0c697000 fffff800`03ff7a5c : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
fffff800`03ff7740 fffff880`03e9a13f : fffffa80`0b957480 fffffa80`00000000 fffffa80`0b98d000 fffff880`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`03ff7770 fffff880`0497b311 : fffff880`01e44008 fffff800`02df7e80 fffff800`03ff7b30 fffff880`01e44000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`03ff77a0 fffff880`01e44008 : fffff800`02df7e80 fffff800`03ff7b30 fffff880`01e44000 fffffa80`0c3f2000 : igdkmd64+0x168311
fffff800`03ff77a8 fffff800`02df7e80 : fffff800`03ff7b30 fffff880`01e44000 fffffa80`0c3f2000 fffff880`08d8f000 : 0xfffff880`01e44008
fffff800`03ff77b0 fffff800`03ff7b30 : fffff880`01e44000 fffffa80`0c3f2000 fffff880`08d8f000 fffff880`00000002 : nt!KiInitialPCR+0x180
fffff800`03ff77b8 fffff880`01e44000 : fffffa80`0c3f2000 fffff880`08d8f000 fffff880`00000002 02c46026`00193cab : 0xfffff800`03ff7b30
fffff800`03ff77c0 fffffa80`0c3f2000 : fffff880`08d8f000 fffff880`00000002 02c46026`00193cab 00000000`00000000 : 0xfffff880`01e44000
fffff800`03ff77c8 fffff880`08d8f000 : fffff880`00000002 02c46026`00193cab 00000000`00000000 00000000`00000000 : 0xfffffa80`0c3f2000
fffff800`03ff77d0 fffff880`00000002 : 02c46026`00193cab 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`08d8f000
fffff800`03ff77d8 02c46026`00193cab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff800`03ff77e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x02c46026`00193cab
STACK_COMMAND: kb
FOLLOWUP_IP:
igdkmd64+168311
fffff880`0497b311 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: igdkmd64+168311
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ca64f34
FAILURE_BUCKET_ID: X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_igdkmd64+168311
BUCKET_ID: X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_igdkmd64+168311
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x119_1_driver_reported_invalid_fence_id_igdkmd64+168311
FAILURE_ID_HASH: {20f47dc1-fbc8-43c2-484d-d916d190c04f}
Followup: MachineOwner
---------
0: kd> lmvm igdkmd64
start end module name
fffff880`04813000 fffff880`053ab360 igdkmd64 T (no symbols)
Loaded symbol image file: igdkmd64.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
Image name: igdkmd64.sys
[COLOR="Red"]Timestamp: Sat Oct 02 03:14:28 2010 (4CA64F34)[/COLOR]
CheckSum: 00B9D8E9
ImageSize: 00B98360
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4