Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\My Documents\Desktop\042612-5974-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03e50000 PsLoadedModuleList = 0xfffff800`04094650
Debug session time: Thu Apr 26 11:48:42.603 2012 (UTC + 8:00)
System Uptime: 0 days 16:30:13.101
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, 1d14d6, 1d14d7, 1d14d7}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
Followup: MachineOwner
---------
1: 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: 00000000001d14d6
Arg3: 00000000001d14d7
Arg4: 00000000001d14d7
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 7
LAST_CONTROL_TRANSFER: from fffff8800145822f to fffff80003eccc80
STACK_TEXT:
fffff880`02f1b4d8 fffff880`0145822f : 00000000`00000119 00000000`00000001 00000000`001d14d6 00000000`001d14d7 : nt!KeBugCheckEx
fffff880`02f1b4e0 fffff880`0fd79eb9 : fffffa80`04874180 00000000`001d14d6 00000000`00000000 00000000`001d14d7 : watchdog!WdLogEvent5+0x11b
fffff880`02f1b530 fffff880`0fd7a125 : fffffa80`0519e000 fffff880`02f1b810 00000000`000011ac 00000000`00000001 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`02f1b560 fffff880`0fd79f76 : fffffa80`001d14d6 00000000`00000000 fffffa80`05194000 fffffa80`04d76000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`02f1b5b0 fffff880`0fc8113f : fffffa80`0451d480 fffffa80`041bc000 00000000`000003d0 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02f1b5e0 fffff880`0f0d697e : fffff880`02f1b810 fffff880`02f1b810 00000000`00000000 fffffa80`0453e000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02f1b610 fffff880`02f1b810 : fffff880`02f1b810 00000000`00000000 fffffa80`0453e000 fffff880`0f0d690e : nvlddmkm+0xb597e
fffff880`02f1b618 fffff880`02f1b810 : 00000000`00000000 fffffa80`0453e000 fffff880`0f0d690e fffffa80`0453e000 : 0xfffff880`02f1b810
fffff880`02f1b620 00000000`00000000 : fffffa80`0453e000 fffff880`0f0d690e fffffa80`0453e000 00000000`00000000 : 0xfffff880`02f1b810
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`0fd79eb9 c744244053eeffff mov dword ptr [rsp+40h],0FFFFEE53h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
Followup: MachineOwner
---------
1: kd> lmvm dxgmms1
start end module name
fffff880`0fd72000 fffff880`0fdb8000 dxgmms1 (pdb symbols) d:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
Loaded symbol image file: dxgmms1.sys
Mapped memory image file: d:\symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys
Image path: \SystemRoot\System32\drivers\dxgmms1.sys
Image name: dxgmms1.sys
Timestamp: Sat Nov 20 17:49:53 2010 (4CE799C1)
CheckSum: 00047A89
ImageSize: 00046000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms1.sys
OriginalFilename: dxgmms1.sys
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
Comments