PC crashes when I launch games

Question

PC crashes when I launch games

Lucas Groeneveld 0

For the past few weeks my PC has struggled to launch games, specifically Baldur's Gate 3 and Crusader Kings 3, and once it even crashed when I tried to watch Netflix.

The games won't start. It will open briefly, sometimes long enough to hear the sound of whatever logo or menu screen opens first, then the pc crashes and reboots. It doesn't matter whether I start the game from Steam, Geforce Experience, or from the .exe. No blue screen of beath, no warning, it just reboots. I did get a BSOD once with the error code: VIDEO_SCHEDULER_INTERNAL_ERROR, but most of the time that did not appear and I went straight from a black screen to the PC rebooting.

Almost every part of the PC is brand new and recently installed, except for the hard drives and power supply. Though it should be noted that this problem existed before I replaced any of the parts. I've tried reinstalling drivers with DDU. I've tried a fresh install of windows. I've tried running games in administrator.

Specs:

Windows 11 Home
B550 GAMING GEN3 (MS-7B86)
Bios version American Megathreads International LLC. P.50, 2023/06/27
AMD Ryzen 5 5600x 6-Core Processor
2x16gb Kingston Fury DDR4
Peladn Gaming RTX3060 12G
Corsair TX750M psu
4 drives total: ADATA SU720, Samsung SSD850 EVO 250GB, ST31000524as, WDC WD10ezex-00WN4A0

dmp file: (there were two files, but one will not upload. Both Dropbox and Google Drive say its unreadable and I apparently don't have permission to open it even though I'm the admin)
https://drive.google.com/drive/folders/10hCCOXY0A8lUa44dC5zfJczcv_SCXnmN?usp=drive_link User's image

User's image

Lucas Groeneveld 0

Managed to open the dmp file that was unreadable. Still can't upload it, but here is the text:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\080623-10015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Empty Dump Data Extension block was ignored
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff804`55400000 PsLoadedModuleList = 0xfffff804`56013460
Debug session time: Sun Aug  6 16:35:37.162 2023 (UTC - 6:00)
System Uptime: 0 days 0:20:01.758
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols

Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`5582ec80 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffba0b`218af780=0000000000000119
11: 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: ffffba0b218af8e0
Arg4: ffffbc0642c48de0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1530

    Key  : Analysis.Elapsed.mSec
    Value: 1828

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 218

    Key  : Analysis.Init.Elapsed.mSec
    Value: 33821

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 111

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

    Key  : Failure.Hash
    Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffba0b218af8e0

BUGCHECK_P4: ffffbc0642c48de0

FILE_IN_CAB:  080623-10015-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffba0b`218af778 fffff804`633a5685     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffba0b`218af8e0 : nt!KeBugCheckEx
ffffba0b`218af780 fffff804`68ab6fa0     : 00000000`00000000 ffffbc06`389dc310 ffffbc06`389dc318 ffffbc06`389dc320 : watchdog!WdLogSingleEntry5+0x3b45
ffffba0b`218af830 fffff804`68b3ea1e     : ffffbc06`00000000 ffffbc06`42c48d00 ffffbc06`42b9b000 ffffbc06`42c48de0 : dxgmms2!VidSchiSendToExecutionQueue+0x1a280
ffffba0b`218afa00 fffff804`68b96dbc     : ffffbc06`42c48de0 ffffba0b`218afab9 ffffbc06`42b9b000 fffff804`68a9b46c : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
ffffba0b`218afa30 fffff804`68b6de36     : fffff804`6e660000 ffffbc06`42b9a6e0 ffffbc06`4ba58010 fffff804`68b45390 : dxgmms2!VidSchiSubmitPagingCommand+0x358
ffffba0b`218afb20 fffff804`68b4545a     : 00000000`00000000 fffff804`68b45390 ffffbc06`42b9b000 ffffbc06`35d75040 : dxgmms2!VidSchiRun_PriorityTable+0x28986
ffffba0b`218afb70 fffff804`557569f7     : ffffbc06`38f88440 fffff804`00000001 ffffbc06`42b9b000 004fe07f`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffba0b`218afbb0 fffff804`55833be4     : ffff9b00`a9b23180 ffffbc06`38f88440 fffff804`557569a0 00aced6c`00fdf0c6 : nt!PspSystemThreadStartup+0x57
ffffba0b`218afc00 00000000`00000000     : ffffba0b`218b0000 ffffba0b`218a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1a280

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.2050

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a280

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------

Elijah Sedqi 0 Reputation points

2023-08-09T04:25:55.18+00:00

Have you figured out the answer to this? My computer is having the same issue recently.

1 answer

Your answer

Elijah Sedqi 0 Reputation points

2023-08-09T04:25:55.18+00:00

Have you figured out the answer to this? My computer is having the same issue recently.

Answer 1

S.Sengupta 23,071 MVP

To resolve the "VIDEO_SCHEDULER_INTERNAL_ERROR," you can try the following steps:

Update Graphics Card Drivers: Make sure you have the latest drivers for your graphics card installed. You can download the drivers from the manufacturer's website and install them manually.

Reinstall Graphics Card Drivers: If updating the drivers doesn't work, try uninstalling the current graphics card drivers completely and then reinstalling them.

Ensure that your graphics card is not overheating. Clean the GPU and ensure proper airflow to prevent overheating.

If the problem persists, there might be a hardware issue with your graphics card. You can try reseating the graphics card in its slot or testing it in another system to see if the problem persists.

Lucas Groeneveld 0 Reputation points

2023-08-07T00:57:26.78+00:00

I've updated and reinstalled the drivers. The gpu isn't overheating. It's properly seated, and I had this exact same issue with my previous card as well, so it doesn't seem to be the gpu itself
Lucas Groeneveld 0 Reputation points

2023-08-07T00:59:07.1033333+00:00

Edit: Apologies for second comment, it was a repeat of the first

Share via

PC crashes when I launch games

1 answer

Your answer