Windows 11 Hypervisor error

Question

My computer has been getting a BSOD almost daily. Usually happens when I'm playing the following games/apps: Genshin Impact, Honkai Star Rail, Wuthering waves, Capcut.

Here's what I've tried to do to resolve it.

• Uninstall nvidia drivers and install older and more stable versions
• Uninstall nvidia drivers and reinstall latest versions

The most consistent error in event view is: "Hypervisor launch failed; Either SVM not present or not enabled in BIOS."

Here is the minidump file records:

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: ffff8a8d254bf8e0 Arg4: ffffe70201cd8940

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0x210d9b, File: 0x210ec3 - C:\ProgramData\Dbg\sym\BTHport.sys\FE108757203000\BTHport.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1749

Key  : Analysis.Elapsed.mSec
Value: 6633

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x119

Key  : Bugcheck.Code.TargetModel
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: ffff8a8d254bf8e0

BUGCHECK_P4: ffffe70201cd8940

FILE_IN_CAB: 052524-13093-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:
ffff8a8d254bf778 fffff80267a35685 : 0000000000000119 0000000000000002 ffffffffc000000d ffff8a8d254bf8e0 : nt!KeBugCheckEx ffff8a8d254bf780 fffff80283e438cd : 0000000000000000 ffffe701f15f5580 ffffe701f15f5588 ffffe701f15f5590 : watchdog!WdLogSingleEntry5+0x3b45 ffff8a8d254bf830 fffff80283ecbc4e : ffffe70200000000 ffffe70201cd8900 ffffe70201c20000 ffffe70201cd8940 : dxgmms2!VidSchiSendToExecutionQueue+0x17f0d ffff8a8d254bfa00 fffff80283f2733c : ffffe70201cd8940 ffff8a8d254bfab9 ffffe70201c20000 fffff80283e296f0 : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a ffff8a8d254bfa30 fffff80283efd25c : fffff8026d740000 ffffe70201c1f010 ffffe70212d39010 ffffe70211889920 : dxgmms2!VidSchiSubmitPagingCommand+0x358 ffff8a8d254bfb20 fffff80283ed580a : 0000000000000000 fffff80283ed5740 ffffe70201c20000 ffffe701e997c040 : dxgmms2!VidSchiRun_PriorityTable+0x279fc ffff8a8d254bfb70 fffff8025096d8e7 : ffffe70201761080 fffff80200000001 ffffe70201c20000 004fe07fb4bbbdff : dxgmms2!VidSchiWorkerThread+0xca ffff8a8d254bfbb0 fffff80250a1d0f4 : ffffc680429c3180 ffffe70201761080 fffff8025096d890 c43348000464a305 : nt!PspSystemThreadStartup+0x57 ffff8a8d254bfc00 0000000000000000 : ffff8a8d254c0000 ffff8a8d254b9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+17f0d

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.3593

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 17f0d

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

Answer 1

didn't work, I said before I had already tried reinstalling it twice, doing it a third time didn't do anything as it occurred minutes later.