BSOD crash dump file

#1
Hi everyone, I need some help to determine why my pc keeps crashing. It normally happens within the first 10-15 minutes of starting up and restarting before BSOD happens seems to avoid the problem. Once restarted the pc will normally operate without any problems for the whole day.

Attached is a copy of the dmp file from this morning along with the Memory & SPD tabs from CPU-Z.

As far as I can tell, all my drivers are up to date.

Any help would be appreciated.
 


Attachments

yowanvista

Well-Known Member
#2
STOP 0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR

Usual causes: Video driver/sub-system

Remove the Nvidia driver
Download Driver Sweeper
Use it to remove any Nvidia driver files left

Reinstall the latest Nvidia Driver
Drivers - Download NVIDIA Drivers

Code:
*******************************************************************************
*                                                                             *
*                        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
---------
 


#3
Thanks for that. I've done exactly what you said however it decided to crash again yesterday evening while unattended and has just done it again within about 10 minutes of startup.

Both dump files are attached, ar ethey both pointing to the same thing too?
 


Attachments

yowanvista

Well-Known Member
#4
Remove the Magic Control Technology UVTP100 USB to VGA adapter, it is causing issues on your system

You can update it here Magic Control Technology

Code:
*******************************************************************************
*                                                                             *
*                        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
---------
 


#5
Don't recognise that, I've got two monitors both connected to the GT220. How/where do I remove it?
 


yowanvista

Well-Known Member
#6
You can find it in the device manager or in "Uninstall or change a program"
 


#7
Thanks for the quick responses. Can't find anything by that name but I have found USB Display Device (Trigger1) from StarTech. Do you think that could be it?

It is. I started uninstalling and Magic popped up on Installshield title bar.

Hopefully that will do it. If it happens again tomorrow, I'll be back.

Thanks again for your help.
 


Last edited:

yowanvista

Well-Known Member
#8
It may be it, either disable that device or uninstall it

If that still doesn't fix it you will need to prevent the driver, mctkmd64.sys from loading
It can be achieved by booting in safemode, navigating to C:\Windows\System32\drivers, locating the "mctkmd64.sys" and renaming it to mctkmd64.sys.bak
Then reboot
 


#9
I don't know if you saw my edited post or whether you had already replied

It was the same, I started uninstalling and Magic popped up on Installshield title bar.

Hopefully that will do it. If it happens again tomorrow, I'll be back.

Thanks again for your help yowanvista and the quick responses, it's greatly appreciated.
 


#10
Hi, I'm back again. It's still doing it, please could you have a look and tell me what seems to be the problem now.

Thanks.
 


Attachments

yowanvista

Well-Known Member
#11
This time its a hardware error, mctkmd64.sys issues are eliminated
Run Prime95 to test the CPU, Select "Small FFTs"
Prime95

Code:
*******************************************************************************
*                                                                             *
*                        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
---------
 


#12
OK, what results are we looking for?
 


yowanvista

Well-Known Member
#13
Theres a hight probability that your CPU has defects, the Prime95 test will confirm it
Is the CPU overclocked?
 


#14
This what it's showing me for CPU #1 - #4

[Jun 14 19:11] Worker starting
[Jun 14 19:11] Setting affinity to run worker on logical CPU #1
[Jun 14 19:11] Beginning a continuous self-test to check your computer.
[Jun 14 19:11] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 14 19:11] Test 1, 210000 Lucas-Lehmer iterations of M501041 using Core2 type-1 FFT length 24K, Pass1=96, Pass2=256.
[Jun 14 19:12] Test 2, 210000 Lucas-Lehmer iterations of M496943 using Core2 type-1 FFT length 24K, Pass1=96, Pass2=256.
[Jun 14 19:14] Test 3, 210000 Lucas-Lehmer iterations of M487423 using Core2 type-1 FFT length 24K, Pass1=96, Pass2=256.
[Jun 14 19:14] Torture Test completed 2 tests in 2 minutes - 0 errors, 0 warnings.
[Jun 14 19:14] Worker stopped.

It hasn't been altered by me and it's a Packard Bell so it's off the shelf.
 


yowanvista

Well-Known Member
#15
Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
 


#16
As it's running continuous tests, I stopped it after 8 cycles for Small FFTs and it's currently running Large FFTs. How many cycles would you like to see?

One thing I don't get is why does it crash every time after 10 mins but then run quite happily for 7-8 hours and then only occasionally crash?
 


yowanvista

Well-Known Member
#17
These test are designed to stress your CPU in a combination of tests which would locate errors
Post the log if it generates one when crashing
 


#18
OK, 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?
 


yowanvista

Well-Known Member
#19
OK, 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?
Run the tests overnight
 


#20
OK wiil do. Two final questions for this evening then. If I need it to run all 3 types of test, I can only run 1 type at a time (unless I've missed something) so which should I use for tonight? Secondly, if it does crash during the night, where do we get the log from?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.