cancel
Showing results for 
Search instead for 
Did you mean: 

B650E-E BSOD (VIDEO_SCHEDULER_INTERNAL_ERROR) when waking up from sleep.

werneo
Level 8

Config:
7800x3d
2x32GB g.skill cl30 6000mhz 
Strix B650E-E 
Asus TUF 3070ti
750W (very old CHIEFTEC PSU, around 10-13 years old, I have it since i7-920) PSU
Multi-monitor setup. 

After upgrading from Z370F-gaming, 8700k and 32gb ram to what I wrote above I started getting BSOD with VIDEO_SCHEDULER_INTERNAL_ERROR error. It only happens when I wake up my PC from sleep.

What I tried to resolve an issue:
- Uninstalled the VIDEO driver with DDU and installed another version of the driver. 
- Reinstalled windows. 
- Updated BIOS from 1809 to 2413.
- Did all kind of stress tests:
    - 3dmax (1+ hour, no issue, 99.5% frame success rate with above-average score).
    - Cinebench (no issues).
    - OCCT Linpack with 95% of memory load (no issues). 
    - OCCT Memory test with 95% of memory load (no issues).
    - LINX Linpack with 85000 data set. 4 passes (I got bored to wait longer, and there were no issues).
- There are no issues while gaming. I completed TLOU with 99% GPU load with no crashes or issues. I completed Hogwarts Legacy, no issues. Playing daily CS2 with high CPU and GPU load, no issues. 

The issue only occurs when I wake my PC up from SLEEP. 

Here is a dump:

 

*******************************************************************************
*                                                                             *
*                        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: fffffb0326d182a0
Arg4: ffffe686a2c08160

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1156

    Key  : Analysis.Elapsed.mSec
    Value: 92803

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffb0326d182a0

BUGCHECK_P4: ffffe686a2c08160

FILE_IN_CAB:  022324-49781-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffffb03`26d18138 fffff801`290a5685     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffb03`26d182a0 : nt!KeBugCheckEx
fffffb03`26d18140 fffff801`683c54fa     : 00000000`00000000 ffffe686`9c3f4210 ffffe686`9c3f4218 ffffe686`9c3f4220 : watchdog!WdLogSingleEntry5+0x3b45
fffffb03`26d181f0 fffff801`6844b50a     : ffffe686`00000000 ffffe686`a2c08100 ffffe686`a2b6f000 ffffe686`a2c08160 : dxgmms2!VidSchiSendToExecutionQueue+0x1c08a
fffffb03`26d183c0 fffff801`684a5bdc     : ffffe686`a2c08160 fffffb03`26d18479 ffffe686`a2b6f000 fffff801`683a7bbc : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
fffffb03`26d183f0 fffff801`6847d6b2     : fffff801`6b000000 ffffe686`9ffce7e0 ffffe686`c3d60010 fffff801`684586c0 : dxgmms2!VidSchiSubmitPagingCommand+0x358
fffffb03`26d184e0 fffff801`6845878a     : 00000000`00000000 fffff801`684586c0 ffffe686`a2b6f000 00000000`00050213 : dxgmms2!VidSchiRun_PriorityTable+0x24ed2
fffffb03`26d18530 fffff801`22707317     : ffffe686`a2bd9480 fffff801`00000001 ffffe686`a2b6f000 005fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffb03`26d18570 fffff801`2281bcc4     : ffffc000`a6d98180 ffffe686`a2bd9480 fffff801`227072c0 342d3837`33362d32 : nt!PspSystemThreadStartup+0x57
fffffb03`26d185c0 00000000`00000000     : fffffb03`26d19000 fffffb03`26d12000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1c08a

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.3155

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c08a

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
---------

 

Hope you can help me. TY.



382 Views
1 ACCEPTED SOLUTION

Accepted Solutions

werneo
Level 8

In my case, it was RAM-related. Either don't use EXPO, or don't use SLEEP. I decided to stop using sleep, hibernation works just fine. 

View solution in original post

10 REPLIES 10

Jiaszzz_ROG
Customer Service Agent

Hello, @werneo 

Thank you for reaching out to us and sharing the detailed specs and logs.
May I ask if the situation you described happened after any changes were made? For example, adjusting the BIOS settings or connecting an external device
Based on the log, "MODULE_NAME: dxgmms2," and since dxgmms2.sys is related to the graphics card driver. 
May I ask what the current version of the driver you have installed is?
We recommend trying to update to the version released on December 15, 2023, which is Version 546.29, from the TUF Gaming GeForce RTX™ 3070 Ti official website and checking again if the issue persists after the update.
If necessary, please also try cross-testing with different graphics cards or PCIe slots.

Thank you.

- The latest driver is installed.
- I tried 3 different driver versions - no fix.
- It was happening on the older version of BIOS and is happening on the newest available version of BIOS.
- It only happens occasionally. I can send the PC to sleep and wake it up 100 times, but at one moment during wakeup, the Nvidia driver will crash as a result it ends up with BSOD. 
- I did all kinds and tastes of stress tests, Linpack, Linx, 3dmark, Furmark, and so on. I already can't even name all of them, there were so many. I did RAM tests, VRAM tests, CPU tests, GPU tests, and PSU tests in combined tests and there was not a single error during any of those tests. 

What I did lately. I disabled the integrated graphics card. And run "sfc /scannow" and "dism /Online /Cleanup-Image /RestoreHealth" in CMD as admin. 
- Error only happens when waking up the PC from sleep, and it happens occasionally, once every few days. Today driver crashed upon waking up from sleep and recovered on its own. I guess this is some kind of progress, as far as there were no BSOD. 

Just checked the JayzTwoCents on the proper way to use DDU. I turned off the internet, disabled the automatic driver updater, restarted in a safe mode, disabled the driver updater this time in DDU, uninstalled the AMD integrated graphics driver, and uninstalled the Nvidia driver. Shut down my PC, turned it on, checked if the Windows updater wasn't updating drivers on its own, and it wasn't, installed Nvidia graphics drivers from the ROG website (the link you provided), disabled integrated graphics, shut down and turn on my PC. As the issue occurs once every few days we'll wait to see if it was fixed. 

jonahhere
Level 7

Experiencing the B650E-E BSOD (VIDEO_SCHEDULER_INTERNAL_ERROR) when waking up from sleep indicates a problem with the video scheduler. To address this issue, consider updating your graphics drivers to the latest version. Graphics driver updates often include bug fixes and improvements that can resolve such errors. Additionally, check for any relevant updates for your operating system, as they may address compatibility issues. If the problem persists, you may want to investigate further or seek assistance from technical forums or the support resources of your device manufacturer.

werneo
Level 8

Update for today. When waking up PC from a sleep got BSOD again. 
Now I changed the EXPO profile to EXPO II and turned off iGPU in bios. Tested memory with LINX, 5 cycles, problem size 85000, no errors. I'll keep you updated. 

Jiaszzz_ROG
Customer Service Agent

Hello, @werneo 

Thank you for providing the relevant information and updates.
Based on the description of the situation, it seems that this issue doesn't always occur. 
We would also recommend you try cross-testing with other GPU or PCIe slots.

Thank you.

Same with other GPU. Right now testing with EXPO off, and no hardware acceleration in Windows. So far 72+ hours without BSOD. I will wait for at least 7 days. 

5 days so far no BSOD. 
So, I guess one of these was the solution:
- EXPO off (my memory is not in that board QVL list).
- Windows hardware acceleration.
- Maximum performance for GPU in Nvidia control panel. 

I'll let it run for a few more days to see if the issue appears again, maybe I'm just lucky there were no BSODs for 5 days. I'll update this thread later when I figure out which of these 3 was the solution. 

7 DAYS NO BSOD. 
I left hardware acceleration in windows as off, and maximum performance on for GPU. We'll now see if it is EXPO related issue or not. EXPO is now on.