Question Pc crashed when playing games, and gpu now disabled by windows

Sleyzox

Commendable
Nov 22, 2019
16
0
1,510
0
I've had this problem for a little while, when I was playing certain games, little pink artifacts appeared and my pc shut down after that Windows disabled it and I couldn't enable it even when reinstalling gpu's drivers. I had temporarily fixed the problem by reducing in MSI Afterburner the power limit of the GPU.

Here is my setup:
Gpu: Nvidia gtx 1080ti
Cpu: Intel i7-8700k
16gb of ram



Here is the Crash Dump:

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: fffffe0ff1d1f860
Arg4: ffff8c83d370a4b0

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.19041.1586 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe0ff1d1f860

BUGCHECK_P4: ffff8c83d370a4b0

CPU_COUNT: c

CPU_MHZ: e70

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: 0



ANALYSIS_SESSION_TIME: 04-10-2022 14:55:51.0241

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff8014c943ad0 to fffff801457f7620

STACK_TEXT:
fffffe0ff1d1f788 fffff8014c943ad0 : 0000000000000119 0000000000000002 ffffffffc000000d fffffe0ff1d1f860 : nt!KeBugCheckEx
fffffe0ff1d1f790 fffff8014e2c8399 : ffff8c83d3707000 00000000c000000d fffffe0ff1d1f899 000000000000000a : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe0ff1d1f7d0 fffff8014e344b9d : ffff8c8300000000 ffff8c83d370a4b0 ffff8c83d3616000 ffff8c83d50550d0 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
fffffe0ff1d1f900 fffff8014e34d51a : ffff8c83d50550d0 ffff8c83d3616000 0000000000000000 ffff8c83d5c336e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffe0ff1d1fa80 fffff8014e34d38a : ffff8c83d3616400 fffff8014e34d2c0 ffff8c83d3616000 ffff9d0152d0f100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffe0ff1d1fad0 fffff80145755a15 : ffff8c83d3619280 fffff80100000001 ffff8c83d3616000 000fa4efbd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffffe0ff1d1fb10 fffff801457fec78 : ffff9d0152d0f180 ffff8c83d3619280 fffff801457559c0 ffffffff000708d8 : nt!PspSystemThreadStartup+0x55
fffffe0ff1d1fb60 0000000000000000 : fffffe0ff1d20000 fffffe0ff1d19000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 446f09ad210e1dd57674461ee1fa384d29860f4f

THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+a99
fffff8014e2c8399 e802dd0000 call dxgmms2!VIDMM_PHYSICAL_ADAPTER::~VIDMM_PHYSICAL_ADAPTER (fffff8014e2d60a0)

FAULT_INSTR_CODE: dd02e8

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.19041.1613

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: a99

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

TARGET_TIME: 2022-04-09T22:01:15.000Z

OSBUILD: 19041

OSSERVICEPACK: 1586

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2036-04-28 02:36:43

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.19041.1586

ANALYSIS_SESSION_ELAPSED_TIME: 7a3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue

FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup: MachineOwner
 
Last edited:

DSzymborski

Titan
Moderator
Well, that's not quite as horrifying as some of ATNG's worst. Still, given ATNG's record, I'd guess that either the PSU killed off the GPU or that the PSU is dying and can't run the still-working PSU.

The next step would be either testing with a known working PSU -- you'd almost certainly want a new one under any circumstance -- or testing your GPU in another PC. Given the lack of quality of this PSU, testing another GPU of similar power consumption would not be something I'd want to risk.
 

Sleyzox

Commendable
Nov 22, 2019
16
0
1,510
0
Well, that's not quite as horrifying as some of ATNG's worst. Still, given ATNG's record, I'd guess that either the PSU killed off the GPU or that the PSU is dying and can't run the still-working PSU.

The next step would be either testing with a known working PSU -- you'd almost certainly want a new one under any circumstance -- or testing your GPU in another PC. Given the lack of quality of this PSU, testing another GPU of similar power consumption would not be something I'd want to risk.
Ok thanks a lot I’m gonna try one of those options
 

Sleyzox

Commendable
Nov 22, 2019
16
0
1,510
0
Well, that's not quite as horrifying as some of ATNG's worst. Still, given ATNG's record, I'd guess that either the PSU killed off the GPU or that the PSU is dying and can't run the still-working PSU.

The next step would be either testing with a known working PSU -- you'd almost certainly want a new one under any circumstance -- or testing your GPU in another PC. Given the lack of quality of this PSU, testing another GPU of similar power consumption would not be something I'd want to risk.
So I bought a new psu but got the same problem does it mean my gpu is dead?
 

DSzymborski

Titan
Moderator
So I bought a new psu but got the same problem does it mean my gpu is dead?
What PSU did you buy? Is it a proper one for the GPU? We're trying to not increase the problem, after all.

If it is a proper PSU this time, then the GPU might have given up the ghost. Artifacting is quite frequently a sign of a failing GPU if there are no driver issues.
 

Sleyzox

Commendable
Nov 22, 2019
16
0
1,510
0
What PSU did you buy? Is it a proper one for the GPU? We're trying to not increase the problem, after all.

If it is a proper PSU this time, then the GPU might have given up the ghost. Artifacting is quite frequently a sign of a failing GPU if there are no driver issues.
The psu I bought is a 850w Corsair RM850
 

Sleyzox

Commendable
Nov 22, 2019
16
0
1,510
0
OK, good PSU now.

Probably the best final test would be if there is someone who can put your GPU in their machine to test.
Sorry for the wait
So I finally tested my gpu in someone else’s pc and it worked fine, we played the same games that would crash my gpu in my pc and everything worked well
 

ASK THE COMMUNITY