Question PC Crashes under load

May 2, 2021
3
0
10
Hi guys, my PC seems to shutdown for the past year when stressed. There are no problems with the temperature / dust, changed PSU, etc. If i wont play anything for a month, i can stress it a couple days and it starts again. It got to the point it crashes from Roblox. Latest shutdown, i kept pressing the power button and nothing happened, for 3min. I used WinDbg to check the memory dump file, this came up

***
  • *
  • 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: ffffbb8f7d244db0
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-3F7B3S6

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 10e

BUGCHECK_P1: 33

BUGCHECK_P2: ffffbb8f7d244db0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
fffff58336876d58 fffff804461b3ad0 : 000000000000010e 0000000000000033 ffffbb8f7d244db0 0000000000000000 : nt!KeBugCheckEx
fffff58336876d60 fffff80448767f45 : 0000000000000000 ffffbb8f7d244eb0 ffff9285ff08b000 0000000000000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff58336876da0 fffff804486d253a : ffffbb8f7d244db0 0000000000000000 ffffbb8f7c613e10 0000000000000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27879
fffff58336876de0 fffff804487406a9 : ffffbb8f7d244db0 0000000000000000 ffffbb8f7c613e10 ffff9285fef5c050 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::scalar deleting destructor'+0xe fffff58336876e10 fffff80448740115 : 0000000000000000 ffffbb8f7c613e10 ffffbb8f7d244db0 ffff928603ebf080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5 fffff58336876e40 fffff804486d257e : ffffbb8f7c848f80 fffff58336876ff9 ffff9285fef5c050 0100000000100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9 fffff58336876f00 fffff80445f545ba : 0000000000000030 0000000000000799 ffffbb8f7c630e88 0000000000000000 : dxgmms2!VidMmCloseAdapter+0x1e fffff58336876f30 fffff80445f1323f : ffff9285fc952000 0000000000000000 ffff9285ff1f8690 fffff8042d061553 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2e fffff58336876f60 fffff80445ed9c55 : ffffbb8f7c848f80 ffffbb8f00000002 ffffbb8f7c848f80 ffff9285fef5c050 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143 fffff58336877060 fffff80445ed873d : ffff9285fef3d000 fffff80400000001 ffff9285fef3d000 fffff80400000001 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9 fffff583368770f0 fffff80445f186c9 : ffffbb8f7c630ea0 fffff58336877240 0000000000000323 ffffbb8f7c630d70 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d fffff58336877140 fffff80445f138e5 : ffffbb8f7c630d70 0000000000000b59 ffffbb8f7c630d70 ffff9285fef57690 : dxgkrnl!DXGPROCESS::Destroy+0x341 fffff583368773b0 fffff80445e06b67 : 0000000000000000 ffffbb8f7c630d70 ffff9285f72aff80 fffff8042daec3c8 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105 fffff58336877500 fffff8042d43759f : 0000000000000000 ffff9285ffb38080 000000000000ff00 ffff9285ff2f4c90 : dxgkrnl!DxgkProcessNotify+0xf7 fffff58336877560 fffff8042d462894 : ffff9285ffb38000 ffff9285ffb38080 0000000000000000 0000000000000000 : nt!PspCallProcessNotifyRoutines+0x213 fffff58336877630 fffff8042d506552 : ffff928603ebf4b8 0000000000000000 fffff58336877820 0000000000000000 : nt!PspExitProcess+0x70 fffff58336877660 fffff8042d4d22e8 : 00000000e0464645 0000000000000001 ffff9286000e3c01 0000000ff3a46000 : nt!PspExitThread+0x5b2 fffff58336877760 fffff8042d067fb7 : fffff58336870101 0000000000000000 ffff9285ff262650 0000000000000000 : nt!KiSchedulerApcTerminate+0x38 fffff583368777a0 fffff8042d1f9d20 : 0000012bf3e47260 fffff58336877850 0000000ff42ff548 ffff928500000000 : nt!KiDeliverApc+0x487 fffff58336877850 fffff8042d20725f : 0000000000000c38 0000000000000000 0000000000000000 ffff9285ff262650 : nt!KiInitiateUserApc+0x70 fffff58336877990 00007ff85e1afa04 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x9f 0000000ff42ff4f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff85e1afa04


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27879

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 27879

FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner


Reinstalled the GPU drivers, did a 8h Memtest86+ run (7 passes, no errors). And did pretty much anything i could find on the internet. If anyone who can better read the log could give me some extra ideeas, i will pray for your immortality.