Hi guys, I'm having this BSOD issue when waking up my PC from a sleep state.
- The dump will be in the end.
- This happens occasionally and it feels like it only happens when the PC stays asleep for 8+ hours.
- I can put the PC asleep 50 times in a row and wake it up a few seconds later, and there wouldn't be a single issue.
- My config:
- ASUS TUF RTX 3070ti (old part, I didn't upgrade it and it worked completely fine with an old CPU+MOBO+RAM configuration).
- ASUS ROG STRIX B650E-E (new part)
- 7800x3d (new part)
- G.Skill DDR5-6000 65536MB PC5-48000 (Kit of 2x32768MB) (F5-6000J3040G32GX2-TZ5NR) (new part) --- I know this RAM is not in the QVL list of this motherboard. But, before buying this RAM I saw a lot of people running this particular combination of RAM and motherboard. I wrote a letter to G.Skill where they confirmed they tested that RAM kit with that motherboard and they had no issues, and it is not in the QVL list, as they think ASUS don't test every single available kit.
- 750W Chieftec PSU. --- This is very old, at least 10 years old, most likely 13 because I ran it with my first i7-920, PSU.
- Multi-screen (3 screens) setup. - What has been done and tried until now:
- Upgraded bios version from 1809 to 2413.
- Reinstalled windows.
- Installed only WHQL drivers (if such are available) from the ROG website.
- Reinstalled video drivers using DDU and JayzTwoCents tutorial on how to use it. I used the latest drivers, previous versions of drivers, and drivers from the ROG website.
- Disabled iGPU in bios.
- Disabled Chrome Hardware acceleration.
- Tried EXPO II.
- Ran all kinds of stress tests: Linx Linpack (85000 problem size) to test RAM, OCCT Linpack, OCCT memory test, 3dmark Speed Way, MSI Kombustor (GL) msi-01 and Furmark Donut 6500. And most likely there were other tests I already forgot about. There was not a single issue, nothing when I was running those tests. I play games on a daily basis, and there are no issues either.
- Right now I'm running without hardware acceleration in Windows, and with EXPO disabled in BIOS (this is the last suggestion I had, if these two fail, I'm done, looks like faulty hardware).
Code:
*******************************************************************************
* *
* 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
---------
Facebook
Twitter
Instagram