Hello there,
Since Dicember 2022 I started having some black screens and then from March 2023 multiple BSOD: VIDEO_SCHEDULER_INTERNAL_ERROR (119) - Arg1: 0000000000000002, The driver failed upon the submission of a command - WARNING: Unable to verify checksum for win32k.sys
This led me to understand that this most probably is a problem involving either drivers, GPU or RAM.
I'll leave below all issues caused and all details I can give, as well as minidump files and PC spec.
I spent a lot of time trying different things to fix it and still nothing. Hopefully there's a person out there who can help me. Thanks in advance!
Premise: never had and still never have issues while playing, even for 3+ hours, but only when working.
Please guys, any help would be appreciated. This problem is driving me nuts and most of all makes me waste hours of work.
Thanks a lot in advance!
------- MINIDUMP -------
------------------------------
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040423-10671-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804
Debug session time: Tue Apr 4 17:19:22.491 2023 (UTC + 2:00)
System Uptime: 0 days 7:05:28.138
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804
2: 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: ffffe703b09db960
Arg4: ffffd588624bacd0
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 31485
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 1
Key : Analysis.Init.CPU.mSec
Value: 374
Key : Analysis.Init.Elapsed.mSec
Value: 7511
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Bugcheck.Code.DumpHeader
Value: 0x119
Key : Bugcheck.Code.Register
Value: 0x119
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 040423-10671-01.dmp
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffe703b09db960
BUGCHECK_P4: ffffd588624bacd0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe703
ffffe703
ffffe703
ffffe703
ffffe703
ffffe703
ffffe703
ffffe703
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.2728
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: a99
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
EDIT: correction to PCI info.
Since Dicember 2022 I started having some black screens and then from March 2023 multiple BSOD: VIDEO_SCHEDULER_INTERNAL_ERROR (119) - Arg1: 0000000000000002, The driver failed upon the submission of a command - WARNING: Unable to verify checksum for win32k.sys
This led me to understand that this most probably is a problem involving either drivers, GPU or RAM.
I'll leave below all issues caused and all details I can give, as well as minidump files and PC spec.
I spent a lot of time trying different things to fix it and still nothing. Hopefully there's a person out there who can help me. Thanks in advance!
Premise: never had and still never have issues while playing, even for 3+ hours, but only when working.
- My specs:
- MOBO: MSI B450 GAMING PLUS MAX
- GPU: ASUS TUF RTX 2060 OC Edition 6 GB GDDR6
- CPU: AMD Ryzen 7 3700X with Wraith Prism, 4,4 GHz
- RAM: 32GB: GSkill (2 x 8 GB) DDR4, 3000 MHz, CL16D, C16 + GSkill (2 x 8 GB) DDR4, 3000 MHz, CL16 Ripjaws V, C16D
- PSU: Cooler Master MWE 750 Bronze 230V V2
- Storage: 2 SSDs + 1HDD (internal) + 1HDD (external)
- Monitors: Lenovo L27i-28 (1920x1080@75Hz) + HP 23cw (1920x1080@60Hz) + an old projector MStar Demo (1280x720@60Hz)
- OS: Win10 Pro
- First issue - fan speed:
I bought the GPU in 2020. I noticed that every time PC booted the GPU fan speed went maximum, but after a few seconds, when the BIOS actually took control, the fan speed went normal.
I read online and reviews stating it was something common for RTX 2060 to start at full speed until MOBO takes control, so I ignored it (but maybe I shouldn't have done that?). Anyway, I didn't have any problem that I remember. - Black screens:
Starting around December 2022 my PC had random black screens in 2 ways:- During boot (PC seemed being started but screens were black)
- Randomly while working. PC was still running, even though I couldn't do or hear anything. I couldn't tell if it was still going but I couldn't interact or if it was actually something similar to a BSOD (without blue screen). This happened random times, very rarely (probably 4 times), for months, until March;
- New RAM and new GPU driver on 5th of January 2023:
Since I thought that 16 GB might be not enough and causing some issue, I installed a very similar RAM to the already 2 I had: GSkill (2 x 8 GB) DDR4, 3000 MHz, CL16 Ripjaws V, C16D - it's basically just a new model of the one I had already installed: GSkill (2 x 8 GB) DDR4, 3000 MHz, CL16D, C16. I beforehand checked if it was compatible with my specs and it was.
That day I also updated my GPU driver with a version released that day.
Later the same day, the monitors went black. I don't know if that was part of the problem. But the next info is weird: - Critical errors in Event Viewer only since the 5th of January 2023:
I checked the Event Viewer and the system has no tracking of any info or errors before the 8th of December 2022, but it has a couple of minidumps from 2021.
The first critical error (due to forced reboot because of black screen) was on 5th of January 2023. - New PSU:
Since I thought the issue might have been caused by a very old PSU I had (450w), I bought and installed a new one: Cooler Master MWE 750w Bronze 230V V2.
Black screens went away for almost 2 weeks, until the 20th of March. Then nothing, until: - First and last BSOD:
- 2023/03/27, while working, open apps: Discord, Spotify, Hexels (a pixel art software to work).
I tried to update all drivers and OS since the issue was pointing to mainly drivers; - 2023/03/30, while working, open apps: Discord, Spotify, Hexels, maybe Steam;
Scanned with Avira Security and Malwarebytes, last one found one which got in quarantine. - 2023/04/01, while working, open apps: Discord, Spotify web (I thought it was the app), Hexels
I installed the latest BIOS version (I had skipped 3-4 versions); rebooted in safe mode, used DDU to uninstall clean all graphic drivers, reinstalled the last GPU version downloading it from the NVIDIA website; - 2023/04/04, while working, open apps: Discord, Hexels.
Like before, but this time I downgraded to the November GPU driver, when I had no issues with black screens or BSOD.
Thought it was Spotify, so I tried working without any music. I always used all those softwares in the past and never had any problem except some crash by Hexels (only the app crashed), so I don't think they are the problem.
A friend told me he had a BSOD different from mine but which was caused by the audio device by NVIDIA. Do you think this could be the case?
Also, I didn't experience any more black screen since the BSOD (maybe once but I'm not so sure), so I'm starting to think that the black screens were actually BSOD which wouldn't show up for some reason (the last BSOD was a bit bugged in resolution too).
Lastly, I always install GeForce Experience app too which I use to capture gameplays and shadowplay. The app gets ready when I also launch Hexels, which is something that it started doing not so long ago - might this be causing issues too?
- 2023/03/27, while working, open apps: Discord, Spotify, Hexels (a pixel art software to work).
- Things I think they might fix the problem:
- Check if GPU is firmly installed or switch PCI (I have 2 slots on the mobo and I think they are the same);
- Avoid GeForce Experience to work with Hexels;
- Try using for a couple of weeks minimum a different software from Hexels;
- Remove the new set of RAM;
- Reset OS clean;
- Buy new GPU.
Please guys, any help would be appreciated. This problem is driving me nuts and most of all makes me waste hours of work.
Thanks a lot in advance!
------- MINIDUMP -------
------------------------------
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040423-10671-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804
27800000 PsLoadedModuleList = 0xfffff804
2842a310Debug session time: Tue Apr 4 17:19:22.491 2023 (UTC + 2:00)
System Uptime: 0 days 7:05:28.138
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804
27bfa110 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe703
b09db890=00000000000001192: 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: ffffe703b09db960
Arg4: ffffd588624bacd0
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 31485
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 1
Key : Analysis.Init.CPU.mSec
Value: 374
Key : Analysis.Init.Elapsed.mSec
Value: 7511
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Bugcheck.Code.DumpHeader
Value: 0x119
Key : Bugcheck.Code.Register
Value: 0x119
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 040423-10671-01.dmp
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffe703b09db960
BUGCHECK_P4: ffffd588624bacd0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe703
b09db888 fffff804
36d93ad0 : 0000000000000119 00000000
00000002 ffffffffc000000d ffffe703
b09db960 : nt!KeBugCheckExffffe703
b09db890 fffff804
387a8399 : ffffd588624b8000 00000000
c000000d ffffe703b09db999 00000000
0000000d : watchdog!WdLogEvent5_WdCriticalError+0xe0ffffe703
b09db8d0 fffff804
38824bcd : ffffd58800000000 ffffd588
624bacd0 ffffd588623b9000 ffffd588
6d6f1010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99ffffe703
b09dba00 fffff804
3882d54a : ffffd5886d6f1010 ffffd588
623b9000 0000000000000000 ffffd588
6247e620 : dxgmms2!VidSchiSubmitPagingCommand+0x2edffffe703
b09dbb80 fffff804
3882d3ba : ffffd588623b9400 fffff804
3882d2f0 ffffd588623b9000 ffffb281
58563100 : dxgmms2!VidSchiRun_PriorityTable+0x17affffe703
b09dbbd0 fffff804
27a55485 : ffffd5886243a380 fffff804
00000001 ffffd588623b9000 000f8067
b4bbbdff : dxgmms2!VidSchiWorkerThread+0xcaffffe703
b09dbc10 fffff804
27c02d48 : ffffb28158563180 ffffd588
6243a380 fffff80427a55430 00000000
00000000 : nt!PspSystemThreadStartup+0x55ffffe703
b09dbc60 00000000
00000000 : ffffe703b09dc000 ffffe703
b09d6000 0000000000000000 00000000
00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.2728
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: a99
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
EDIT: correction to PCI info.
Last edited: