My newly built pc is randomly crashing. This can happen sometimes when i just boot it up or when im in a game.
Specs:
M.2 SSD Samsung
Mini itx b450 mobo
Msi rtx 1660
Sfx 600w psu
Corsair rgb ram 2x8gb 3200mhz
R7 2700x
120mm aio cooler.
I ran verifier and windbg and this is what i got
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\minidump\050120-8421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803
Debug session time: Fri May 1 12:11:44.559 2020 (UTC + 2:00)
System Uptime: 0 days 0:00:39.211
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803
11: kd> !analyze -v
***
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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffa10c641e0960
Arg4: ffffe00866db8f50
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-R9FPUQ2
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 21
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffa10c641e0960
BUGCHECK_P4: ffffe00866db8f50
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa10c
ffffa10c
ffffa10c
ffffa10c
ffffa10c
ffffa10c
ffffa10c
ffffa10c
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.1059
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a08
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
Specs:
M.2 SSD Samsung
Mini itx b450 mobo
Msi rtx 1660
Sfx 600w psu
Corsair rgb ram 2x8gb 3200mhz
R7 2700x
120mm aio cooler.
I ran verifier and windbg and this is what i got
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\minidump\050120-8421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803
19e00000 PsLoadedModuleList = 0xfffff803
1a248150Debug session time: Fri May 1 12:11:44.559 2020 (UTC + 2:00)
System Uptime: 0 days 0:00:39.211
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803
19fc2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa10c
641e0890=000000000000011911: 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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffa10c641e0960
Arg4: ffffe00866db8f50
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-R9FPUQ2
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 21
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffa10c641e0960
BUGCHECK_P4: ffffe00866db8f50
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa10c
641e0888 fffff803
1e8641a0 : 0000000000000119 00000000
00000002 ffffffffc000000d ffffa10c
641e0960 : nt!KeBugCheckExffffa10c
641e0890 fffff803
219fabf8 : 0000000000000000 ffffe008
66db6000 ffffe00866db6000 ffffe008
66db8f50 : watchdog!WdLogEvent5_WdCriticalError+0xe0ffffa10c
641e08d0 fffff803
21a58684 : ffffe00800000000 ffffe008
66db8f50 ffffe00866cba000 ffffe008
6bd119a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08ffffa10c
641e0a00 fffff803
21a69c15 : ffffe00866c8b9a0 ffffe008
66cba000 0000000000000000 ffffe008
65f47010 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4ffffa10c
641e0b80 fffff803
21a69a8a : ffffe00866cba400 fffff803
21a699c0 ffffe00866cba000 00000000
00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175ffffa10c
641e0bd0 fffff803
19e6bcd5 : ffffe00866d40680 fffff803
00000001 ffffe00866cba000 00000067
b4bbbdff : dxgmms2!VidSchiWorkerThread+0xcaffffa10c
641e0c10 fffff803
19fc9998 : fffff80315ca4180 ffffe008
66d40680 fffff80319e6bc80 0078006f
00620058 : nt!PspSystemThreadStartup+0x55ffffa10c
641e0c60 00000000
00000000 : ffffa10c641e1000 ffffa10c
641db000 0000000000000000 00000000
00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.1059
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a08
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------