Blue screen error

Question

When I alt + tab out of the game everything is good, but when I alt + tab to the game my PC crashes and gives me a blue screen. Below are the minidump values. please help!

Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\essa-\Desktop\060822-11062-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8064ae00000 PsLoadedModuleList = 0xfffff8064ba2a2b0
Debug session time: Wed Jun 8 22:53:35.058 2022 (UTC + 3:00)
System Uptime: 12 days 21:23:28.918
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8064b1f7d60 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8485b59fdf30=0000000000000119
11: 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: 0000000000000e00, The subtype of the BugCheck:
Arg2: ffffd5824568c000
Arg3: ffffd5824568bad0
Arg4: ffffd5824568bdd8

Debugging Details:

------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 8859  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 75276  

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

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

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

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: 060822-11062-01.dmp

BUGCHECK_CODE: 119

BUGCHECK_P1: e00

BUGCHECK_P2: ffffd5824568c000

BUGCHECK_P3: ffffd5824568bad0

BUGCHECK_P4: ffffd5824568bdd8

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8485b59fdf28 fffff806624e3ad0 : 0000000000000119 0000000000000e00 ffffd5824568c000 ffffd5824568bad0 : nt!KeBugCheckEx
ffff8485b59fdf30 fffff8066342a2c2 : ffffd5824568c000 0000000000000000 ffff8485b59fe370 0000000000000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8485b59fdf70 fffff8066342a931 : ffffd5824568bad0 ffff8485b59fe160 ffffd58251282240 ffffd5824568c000 : dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool+0x11e
ffff8485b59fdfa0 fffff8066342acd0 : ffff8485b59fe370 ffff848500000000 ffff8485b59fe160 ffffd58251282240 : dxgmms2!VidSchiEnqueueDeviceCommandToWorkerThreadAtDpc+0x5d
ffff8485b59fe060 fffff8066340dae6 : ffffd5823be02100 fffff8064b047cd2 ffffd5823be02340 fffff8064b7b23ff : dxgmms2!VidSchiExecuteMmIoFlipMultiPlaneOverlay3+0x2a4
ffff8485b59fe1b0 fffff8066340cb17 : ffffd582456a7708 0000000000989680 0000000000000000 0000000000000000 : dxgmms2!VidSchiExecuteMmIoFlip+0x216
ffff8485b59fec30 fffff8066342cbc4 : ffff8485b59ff0c0 ffffd58245694000 0000000000000000 ffffc18600000001 : dxgmms2!VidSchUnwaitFlipQueue+0x507
ffff8485b59fecd0 fffff8066340174c : ffff8485b59ff0c0 ffffd5824c876b60 0000000000000000 fffff80600000000 : dxgmms2!VidSchiSubmitIndependentFlip+0x908
ffff8485b59fedc0 fffff8066342f9b1 : ffffd5824c737010 ffff8485b59ff0c0 ffffd5824568cc00 ffffd5824568cd20 : dxgmms2!VidSchiProcessPresentHistoryToken+0x3ac
ffff8485b59fee90 fffff80663431d55 : 0000000000000000 ffffd5824568cc20 ffff8485b59ff0c0 ffffd5824568c000 : dxgmms2!VidSchiFlushPendingTokenList+0xe9
ffff8485b59feef0 fffff806634035a5 : 0000000000000000 0000000000000000 0000000000000000 ffffd58249888780 : dxgmms2!VidSchiTryEnterIndependentFlip+0x3d
ffff8485b59fef20 fffff8066342f6f8 : ffff8485b59ff0c0 0000000000000001 0000000000000000 ffffd5824b382000 : dxgmms2!VidSchiCompleteFlipEntry+0x915
ffff8485b59ff050 fffff8066348d561 : ffffd58249597500 ffffd582452df510 ffffd582456ec620 ffffd5824568bad0 : dxgmms2!VidSchiExecuteMmIoFlipAtPassiveLevel+0x368
ffff8485b59ffa80 fffff8066348d38a : ffffd5824568c400 fffff8066348d2c0 ffffd5824568c000 ffffe58160200100 : dxgmms2!VidSchiRun_PriorityTable+0x1c1
ffff8485b59ffad0 fffff8064b0eea75 : ffffd582456a8280 fffff80600000001 ffffd5824568c000 000fa4efbd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8485b59ffb10 fffff8064b1ff3b8 : ffffe58160200180 ffffd582456a8280 fffff8064b0eea20 0e17240c0120848e : nt!PspSystemThreadStartup+0x55
ffff8485b59ffb60 0000000000000000 : ffff8485b5a00000 ffff8485b59f9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool+11e

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1645

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 11e

FAILURE_BUCKET_ID: 0x119_e00_UNKNOWN_dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56d0fc26-28d6-4f29-b7c5-92f73ee710af}

Followup: MachineOwner
---------

Answer 1

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

Open start and search for feedback and open the Feedback Hub app and report this issue.
Run Windows Update and download and install all updates.
Try update your graphic card driver.
Try performing Clean Boot and see if the problem persists?
Have a look at:
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
If not enable services one by one to identify which one causing this issue.