Computer sometimes experiences "BSOD" when waking up from sleep mode.

Question

This is an issue I'd like to get fixed before it does any real damage to my device. I am forced to hold down the power button to get out of this particular situation, since my device doesn't actually go into a BSOD, but rather fails to display anything until I restart. The problem is that this crash happens during the wake-up process of sleep mode. The bad actor seems to be msedgewebview2.exe that makes dxgmms2.sys trigger a BSOD.

Device specifications partially derived from dxdiag:

• Operating system: Windows 11 Home 64-bit (10.0, Build 22631)
• Motherboard: B650 Gaming X AX V2
• BIOS: F2
• Processor: AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs), ~4.2GHz
• Memory: 65536MB RAM (DDR5 6600MT/s 32CL)
• GPU: RTX 4070 Super

Minidump file contents:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000033, The subtype of the BugCheck:
Arg2: ffffac04f495d2b0
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x49452b, File: 0x4943ff - C:\ProgramData\Dbg\sym\dxgkrnl.sys\B222A642488000\dxgkrnl.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1296

    Key  : Analysis.Elapsed.mSec
    Value: 4646

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    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: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

    Key  : Failure.Hash
    Value: {590e82e4-fa32-3e14-0943-e6b01c6637c4}

BUGCHECK_CODE:  10e

BUGCHECK_P1: 33

BUGCHECK_P2: ffffac04f495d2b0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  050624-10062-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:  msedgewebview2

STACK_TEXT:  
ffff828c`300fe378 fffff803`7ad95685     : 00000000`0000010e 00000000`00000033 ffffac04`f495d2b0 00000000`00000000 : nt!KeBugCheckEx
ffff828c`300fe380 fffff803`7a70bcbf     : 00000000`00000000 ffff8483`ffcfb180 ffff8483`ffcfb188 ffff8483`ffcfb190 : watchdog!WdLogSingleEntry5+0x3b45
ffff828c`300fe430 fffff803`7a646646     : 00000000`00000001 ffffac04`f495d2b0 00000000`00000001 ffffac04`f495d2b0 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x2ca07
ffff828c`300fe840 fffff803`7a6f75a7     : ffffac04`f5363490 00000000`00000000 00000000`00000001 00000000`00000b80 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe
ffff828c`300fe870 fffff803`7a6342b2     : ffffac04`f5363490 ffff828c`300fe9d0 ffff8484`086fb630 00000000`00000001 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0x34927
ffff828c`300fe8a0 fffff803`7aa9f531     : 00000000`00000118 ffff828c`300fe9d0 ffff8484`028806b8 ffff8484`028806c0 : dxgmms2!VidMmTerminateProcess+0x12
ffff828c`300fe8d0 fffff803`7aa9d5eb     : ffffac04`f47d0010 00000000`00000000 00000000`00000001 fffff803`3252a140 : dxgkrnl!DXGPROCESS::Destroy+0x1d1
ffff828c`300fea70 fffff803`7aa9e765     : ffffac04`f47d0010 ffffac04`f47d0010 00000000`00000113 ffff8484`08fbfdd0 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0xfb
ffff828c`300febb0 ffffbcd4`f37217d9     : ffff828c`300ff1c8 ffffac04`f40b0b30 00000000`00005600 ffffac04`f40b0b30 : dxgkrnl!DxgkProcessCallout+0x1c5
ffff828c`300fed40 ffffbcd4`f2c700ca     : 00000000`000056d0 00000000`00000000 ffffbcd4`f2e73c10 00000000`00000000 : win32k!DxDdProcessCallout+0x69
ffff828c`300fed70 ffffbcd4`f3028134     : ffffac04`e6ae8000 ffffd5ff`4f400000 ffff828c`300feea0 ffffbcd4`f302153e : win32kbase!GdiProcessCallout+0x2ca
ffff828c`300fedf0 ffffbcd4`f2c7049d     : 00000000`00000000 00000000`00000000 ffff828c`300fef40 00000000`00000000 : win32kfull!W32pProcessCallout+0x1d4
ffff828c`300fee40 ffffbcd4`f37210cb     : 00000000`00000001 00000000`00000000 ffff8484`08986df0 fffff803`3252c9b8 : win32kbase!W32CalloutDispatch+0x1dd
ffff828c`300ff090 fffff803`32570fb1     : ffff828c`300ff1c8 00000000`00000000 fffff803`32a37c40 ffffac05`1a1acc20 : win32k!W32CalloutDispatchThunk+0x2b
ffff828c`300ff0c0 fffff803`32570f13     : 00000000`00000000 ffff828c`300ff2b9 00000000`00000000 00000000`00000000 : nt!ExCallCallBack+0x3d
ffff828c`300ff0f0 fffff803`32576a09     : ffff8484`08986df0 00000000`00000000 ffff828c`00000000 00000000`00000000 : nt!PsInvokeWin32Callout+0x33
ffff828c`300ff120 fffff803`32539768     : 00000000`00000022 00000000`00000001 00000000`00000000 ffff8484`16888080 : nt!PspExitThread+0x5e5
ffff828c`300ff220 fffff803`320beb3d     : 00000000`00000000 00000000`00000000 00000cbf`0010005b 0000001c`740ff000 : nt!KiSchedulerApcTerminate+0x38
ffff828c`300ff260 fffff803`3221e810     : 0000001c`740ef601 ffff828c`300ff320 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x47d
ffff828c`300ff320 fffff803`3222d9df     : ffff8484`16904080 ffff8484`16aa4560 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffff828c`300ff460 00007ff9`a8bef3e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
0000001c`740ef9c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`a8bef3e4

SYMBOL_NAME:  dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+2ca07

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.1272

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2ca07

FAILURE_BUCKET_ID:  0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {590e82e4-fa32-3e14-0943-e6b01c6637c4}

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

Answer 1

Hi 3Meta,

Welcome to the Microsoft community and thank you for asking your question in the community!

Thank you for the log information! Based on the information you provided, I analyzed that the reason for the blue screen when you resume use in sleep mode may be due to your graphics card driver.

dxgmms2.sys is a graphics card related driver, please uninstall both the core and solo drivers in the device manager, and then get the latest driver from the official website of the device brand and install it to try to solve the problem.

Please let me know if I have misunderstood. Tell us the results and we will get back to you as soon as possible. We look forward to hearing from you.

Best regards,

Zhang Yang - MSFT | Microsoft Community Support Specialist