*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 119, {1, 1137d, 1137e, 1137e}
Unable to load image \SystemRoot\system32\drivers\mctkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mctkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for mctkmd64.sys
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 )
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: 000000000001137d
Arg3: 000000000001137e
Arg4: 000000000001137e
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 6
LAST_CONTROL_TRANSFER: from fffff8800153e22f to fffff80003a92d00
STACK_TEXT:
fffff800`05daa6a8 fffff880`0153e22f : 00000000`00000119 00000000`00000001 00000000`0001137d 00000000`0001137e : nt!KeBugCheckEx
fffff800`05daa6b0 fffff880`04574eb9 : 00000000`00000000 00000000`0001137d 00000000`00000000 00000000`0001137e : watchdog!WdLogEvent5+0x11b
fffff800`05daa700 fffff880`045751e6 : fffffa80`087bc000 fffffa80`06d2aba8 fffffa80`000011ac fffffa80`06eb0000 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`05daa730 fffff880`04574f76 : fffffa80`0001137d fffff800`05daa930 fffffa80`087bc000 fffffa80`08498000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
fffff800`05daa780 fffff880`0447c13f : fffffa80`06cb6040 fffff880`0f329d98 fffffa80`06eb0000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`05daa7b0 fffff880`0fed92cc : fffff880`0f329d1d fffff800`05daa9a0 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`05daa7e0 fffff880`0f329d1d : fffff800`05daa9a0 00000000`00000000 00000000`00000000 00000000`00000000 : mctkmd64+0x82cc
fffff800`05daa7e8 fffff800`05daa9a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xb5d1d
fffff800`05daa7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`05daa9a0
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`04574eb9 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
---------
*******************************************************************************
* *
* 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: 0000000000615a19
Arg3: 0000000000615a1a
Arg4: 0000000000615a1a
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 6
LAST_CONTROL_TRANSFER: from fffff8800109822f to fffff80003a80d00
STACK_TEXT:
fffff880`02f8c598 fffff880`0109822f : 00000000`00000119 00000000`00000001 00000000`00615a19 00000000`00615a1a : nt!KeBugCheckEx
fffff880`02f8c5a0 fffff880`0459aeb9 : 00000000`00000000 00000000`00615a19 00000000`00000000 00000000`00615a1a : watchdog!WdLogEvent5+0x11b
fffff880`02f8c5f0 fffff880`0459b1e6 : fffffa80`08aa8000 fffffa80`06eb4ba8 00000000`000011ac fffff880`0f33c41d : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`02f8c620 fffff880`0459af76 : 00000000`00615a19 00000000`00000020 fffffa80`08aa8000 fffffa80`086e6000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
fffff880`02f8c670 fffff880`044a213f : fffffa80`07078040 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02f8c6a0 fffff880`0fd892cc : 00000000`0010a48c fffff880`02f8c890 00000000`00000000 fffff880`0f33c4cb : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02f8c6d0 00000000`0010a48c : fffff880`02f8c890 00000000`00000000 fffff880`0f33c4cb fffffa80`084a9460 : mctkmd64+0x82cc
fffff880`02f8c6d8 fffff880`02f8c890 : 00000000`00000000 fffff880`0f33c4cb fffffa80`084a9460 00000000`00000000 : 0x10a48c
fffff880`02f8c6e0 00000000`00000000 : fffff880`0f33c4cb fffffa80`084a9460 00000000`00000000 00000000`00000000 : 0xfffff880`02f8c890
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`0459aeb9 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
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80063768f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`033a86b0 fffff800`03cd1c59 : fffffa80`063768d0 fffffa80`05522680 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033a8bd0 fffff800`03bb1fa7 : fffffa80`063768d0 fffff800`03c2c2b8 fffffa80`05522680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033a8c00 fffff800`03b195c5 : fffff800`03c8dac0 00000000`00000001 fffffa80`06375850 fffffa80`05522680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033a8c40 fffff800`03a99021 : fffff880`01030e00 fffff800`03b195a0 fffffa80`05522600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033a8c70 fffff800`03d2b32e : 00000000`00000000 fffffa80`05522680 00000000`00000080 fffffa80`0550fb30 : nt!ExpWorkerThread+0x111
fffff880`033a8d00 fffff800`03a80666 : fffff880`03164180 fffffa80`05522680 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033a8d40 00000000`00000000 : fffff880`033a9000 fffff880`033a3000 fffff880`039bd500 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Run the tests overnightOK, it seems to be passing the tests quite happily at the moment. Bearing in mind it's behaviour, would you suggest running the tests tomorrow after it starts up or just keep it running now to see if anything happens?