Question Random BSOD with RTX 2060 makes me suffer

[Arg4f]

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.

• 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?
• 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.

That's "all" that I have. Below you'll find the last minidump file. Let me know if you need any other detail.
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 = 0xfffff80427800000 PsLoadedModuleList = 0xfffff8042842a310
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:
fffff80427bfa110 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe703b09db890=0000000000000119
2: 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:
ffffe703b09db888 fffff80436d93ad0 : 0000000000000119 0000000000000002 ffffffffc000000d ffffe703b09db960 : nt!KeBugCheckEx
ffffe703b09db890 fffff804387a8399 : ffffd588624b8000 00000000c000000d ffffe703b09db999 000000000000000d : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffe703b09db8d0 fffff80438824bcd : ffffd58800000000 ffffd588624bacd0 ffffd588623b9000 ffffd5886d6f1010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffffe703b09dba00 fffff8043882d54a : ffffd5886d6f1010 ffffd588623b9000 0000000000000000 ffffd5886247e620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffe703b09dbb80 fffff8043882d3ba : ffffd588623b9400 fffff8043882d2f0 ffffd588623b9000 ffffb28158563100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffe703b09dbbd0 fffff80427a55485 : ffffd5886243a380 fffff80400000001 ffffd588623b9000 000f8067b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffe703b09dbc10 fffff80427c02d48 : ffffb28158563180 ffffd5886243a380 fffff80427a55430 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffe703b09dbc60 0000000000000000 : ffffe703b09dc000 ffffe703b09d6000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


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.

 

[Colif]

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.

Using 2 sets of ram can cause strange errors. Sticks in sets only tested to work with the sticks in that set. More you add, more chance of errors. Especially on Ryzen systems. More likely to work fine on Intel.
did the errors occur before swapping ram? Try removing it and see if the errors continue

can you upload the minidumps to a file sharing website and show link here?

 

[Arg4f]

Using 2 sets of ram can cause strange errors. Sticks in sets only tested to work with the sticks in that set. More you add, more chance of errors. Especially on Ryzen systems. More likely to work fine on Intel.
did the errors occur before swapping ram? Try removing it and see if the errors continue

can you upload the minidumps to a file sharing website and show link here?

Hello Colif,
Thanks for replying.

Here you can find the zip with all the minidump files I have (the 4 ones from 2023 I mentioned + 2 from 2021, even though I don't think they are related).

As for the RAM, the black screens occurred even before I added the new set, although they stopped after I mounted the new PSU (I only had 1 black scren on boot after).
Do you think the black screens and the BSOD are 2 separate issues?
Maybe the black screens were caused by the old PSU while the BSOD from the new set of RAM?

At the moment I'm waiting to see if a new BSOD show up even though I have installed a downgraded GPU driver from November, when everything was fine. Even though this cannot possible be a permanent solution.
Do you think this is not a driver-related problem but only hardware-side?

Thanks again and have a great day.

 

[Colif]

One solution is to run DDU again and instead of using Geforce experience to get drivers, run windows update as it will get older drivers that are perhaps more stable.

if all BSOD say same things, its probably best to do above.

its always possible PSU fixed the black screens. If they haven't happened since. Changing multiple pieces of hardware around can make it difficult to isolate cause.



conversion of dumps

report - click run as fiddle to read (mostly for me)


File: 040423-10671-01.dmp (Apr 5 2023 - 01:19:22)
BugCheck: [VIDEO_SCHEDULER_INTERNAL_ERROR (119)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 7 Hour(s), 05 Min(s), and 28 Sec(s)

File: 033023-10453-01.dmp (Mar 31 2023 - 00:46:41)
BugCheck: [VIDEO_SCHEDULER_INTERNAL_ERROR (119)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 8 Hour(s), 01 Min(s), and 12 Sec(s)

File: 032723-9984-01.dmp (Mar 27 2023 - 19:25:03)
BugCheck: [VIDEO_SCHEDULER_INTERNAL_ERROR (119)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 58 Min(s), and 39 Sec(s)

File: 121521-6234-01.dmp (Dec 15 2021 - 18:50:21)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
Probably caused by: memory_corruption (Process: OriginWebHelperService.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 44 Sec(s)

File: 121521-24765-01.dmp (Dec 15 2021 - 18:38:58)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
Probably caused by: memory_corruption (Process: OriginWebHelperService.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 50 Sec(s)

Comment: 2 or more types of RAM are installed.

I assume Driver verifer is off now.

only way to know if ram is cause is to remove it. The dumps may not reveal it as such. Memtest likely shows no errors either. As the compatibility error caused by ram often doesn't mean the sticks are bad, just that the PC has problems with them.

its not exactly the same

8192MB	2133MHz	Unknown	F4-3000C16-8GVRB
8192MB	2133MHz	Unknown	F4-3000C16-8GISB
8192MB	2133MHz	Unknown	F4-3000C16-8GVRB
8192MB	2133MHz	Unknown	F4-3000C16-8GISB

although there isn't much difference
https://www.gskill.com/specification/165/185/1535968498/F4-3000C16S-8GISB-Specification

F4-3000C16S-8GVRB - Specification - G.SKILL International Enterprise Co., Ltd.

Ripjaws V DDR4-3000 CL16-18-18-38 1.35V 8GB (1x8GB)

www.gskill.com

the only real difference is in the naming
IS = Aegis memory whereas V = Ripjaw

Info - Meaning of RAM Product Item Numbers/Codes

If you are looking at differences between RAM modules being sold or if you are just checking some RAM models of your motherboard's Memory QVL that have been tested, you may have come across with these hard-to-figure-out RAM Product Items/Codes such as: "HX430C15SB2/8" or "TED416G2133C1501" or...

forums.tomshardware.com

Still could be enough.

 

[Arg4f]

its always possible PSU fixed the black screens. If they haven't happened since.

Only happened once after I installed the new PSU, so I guess it might have worked.

One solution is to run DDU again and instead of using Geforce experience to get drivers, run windows update as it will get older drivers that are perhaps more stable.

I haven't used Geforce Experience to get drivers, but I directly downloaded from NVIDIA website the one that was running on my PC when it was stable last time (november) - I also installed Geforce Experience to use the shadowplay, but I'm not downloading drivers from there.

So, now I'll wait to see if a BSOD shows up, which is probable.
If it does, I'll run DDU again and install the driver through Windows. How should I do this? Device Manager > GPU > Properties > Update driver?
If the BSOD shows up again, I'll remove the new RAM.

I'll keep you updated, hopefully with good news.

 

[Colif]

How should I do this? Device Manager > GPU > Properties > Update driver?
If the BSOD shows up again, I'll remove the new RAM.

Settings/windows update. It will find the drivers there. I have done it myself.

 

[Arg4f]

Settings/windows update. It will find the drivers there. I have done it myself.

Oh, you mean by simply launching "Check for Updates"?

 

[--SID--]

What BIOS version is the motherboard running?

 

[Arg4f]

What BIOS version is the motherboard running?

The latest, from the 11th of August, 2022: E7B86AMS.HG0
The previous one was 3 versions older, from the 25th of May, 2021: E7B86AMS.HC0

 

[Colif]

Oh, you mean by simply launching "Check for Updates"?

yes. It will recognise fact gpu doesn't have a driver.

 

[Arg4f]

Update:
So, new BSOD right now: KERNEL_SECURITY_CHECK_FAILURE (139)
I haven't had the old one since the last time I mentioned (VIDEO_SCHEDULER_INTERNAL_ERROR (119).
This time it happened while I was playing a game.

Here is the minidump file, and below some preview:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff8011649a650, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff8011649a5a8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

I haven't removed the RAM yet because first I wanted to check if the downgrade of the GPU driver would work.

Also, checking the Event Viewer I noticed the following errors and warnings:

• Error, Event 7000, Service Control Manager
  The MBAMService service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
• Error, Event 7000, Service Control Manager
  The AGSService service failed to start due to the following error: The system cannot find the path specified.
• Warning, Event 10016, DistributedCOM
  The impostazioni specifiche dell'applicazione permission settings do not grant Locale Attivazione permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}
  and APPID
  {8BC3F05E-D86B-11D0-A075-00C04FB68820}
  to the user T800\Andrea SID (S-1-5-21-2581140494-33717019-2658192237-1001) from address LocalHost (tramite LRPC) running in the application container Non disponibile SID (S-1-15-2-2034283098-2252572593-1072577386-2659511007-3245387615-27016815-3920691934). This security permission can be modified using the Component Services administrative tool.

The last one got repeated a lot of times.
Here you can download the screenshots of the errors/warnings.

How bad is the new BSOD?
And how serious are those errors/warnings? Are they any related to the BSOD?

I'm probably going to reset clean the system in the next days, I'm afraid there are some corrupted files, besides any issues with RAM.

Any help would be extremely appreciated.
Thank you all.

 

[HeerZakdoeK]

Update:
So, new BSOD right now: KERNEL_SECURITY_CHECK_FAILURE (139)
I haven't had the old one since the last time I mentioned (VIDEO_SCHEDULER_INTERNAL_ERROR (119).
This time it happened while I was playing a game.

Here is the minidump file, and below some preview:

I haven't removed the RAM yet because first I wanted to check if the downgrade of the GPU driver would work.

Also, checking the Event Viewer I noticed the following errors and warnings:

• Error, Event 7000, Service Control Manager
  The MBAMService service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
• Error, Event 7000, Service Control Manager
  The AGSService service failed to start due to the following error: The system cannot find the path specified.
• Warning, Event 10016, DistributedCOM
  The impostazioni specifiche dell'applicazione permission settings do not grant Locale Attivazione permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}
  and APPID
  {8BC3F05E-D86B-11D0-A075-00C04FB68820}
  to the user T800\Andrea SID (S-1-5-21-2581140494-33717019-2658192237-1001) from address LocalHost (tramite LRPC) running in the application container Non disponibile SID (S-1-15-2-2034283098-2252572593-1072577386-2659511007-3245387615-27016815-3920691934). This security permission can be modified using the Component Services administrative tool.

The last one got repeated a lot of times.
Here you can download the screenshots of the errors/warnings.

How bad is the new BSOD?
And how serious are those errors/warnings? Are they any related to the BSOD?

I'm probably going to reset clean the system in the next days, I'm afraid there are some corrupted files, besides any issues with RAM.

Any help would be extremely appreciated.
Thank you all.

"[VIDEO_SCHEDULER_INTERNAL_ERROR (119)]
Probably caused by: memory_corruption"

Unless with help you mean the English dictionary, I think you may be in denial.

It's Nvidialzheimer's. I'm sorry.