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
***
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:
fffff583
fffff583
fffff583
fffff583
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.
***
- *
- 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:
fffff583
36876d58 fffff804
461b3ad0 : 000000000000010e 00000000
00000033 ffffbb8f7d244db0 00000000
00000000 : nt!KeBugCheckExfffff583
36876d60 fffff804
48767f45 : 0000000000000000 ffffbb8f
7d244eb0 ffff9285ff08b000 00000000
00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0fffff583
36876da0 fffff804
486d253a : ffffbb8f7d244db0 00000000
00000000 ffffbb8f7c613e10 00000000
00000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27879fffff583
36876de0 fffff804
487406a9 : ffffbb8f7d244db0 00000000
00000000 ffffbb8f7c613e10 ffff9285
fef5c050 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::scalar deleting destructor'+0xe
fffff583
36876e10 fffff80448740115 : 00000000
00000000 ffffbb8f7c613e10 ffffbb8f
7d244db0 ffff928603ebf080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5
fffff583
36876e40 fffff804486d257e : ffffbb8f
7c848f80 fffff58336876ff9 ffff9285
fef5c050 0100000000100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9
fffff583
36876f00 fffff80445f545ba : 00000000
00000030 0000000000000799 ffffbb8f
7c630e88 0000000000000000 : dxgmms2!VidMmCloseAdapter+0x1e
fffff583
36876f30 fffff80445f1323f : ffff9285
fc952000 0000000000000000 ffff9285
ff1f8690 fffff8042d061553 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2e
fffff583
36876f60 fffff80445ed9c55 : ffffbb8f
7c848f80 ffffbb8f00000002 ffffbb8f
7c848f80 ffff9285fef5c050 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143
fffff583
36877060 fffff80445ed873d : ffff9285
fef3d000 fffff80400000001 ffff9285
fef3d000 fffff80400000001 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9
fffff583
368770f0 fffff80445f186c9 : ffffbb8f
7c630ea0 fffff58336877240 00000000
00000323 ffffbb8f7c630d70 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d
fffff583
36877140 fffff80445f138e5 : ffffbb8f
7c630d70 0000000000000b59 ffffbb8f
7c630d70 ffff9285fef57690 : dxgkrnl!DXGPROCESS::Destroy+0x341
fffff583
368773b0 fffff80445e06b67 : 00000000
00000000 ffffbb8f7c630d70 ffff9285
f72aff80 fffff8042daec3c8 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
fffff583
36877500 fffff8042d43759f : 00000000
00000000 ffff9285ffb38080 00000000
0000ff00 ffff9285ff2f4c90 : dxgkrnl!DxgkProcessNotify+0xf7
fffff583
36877560 fffff8042d462894 : ffff9285
ffb38000 ffff9285ffb38080 00000000
00000000 0000000000000000 : nt!PspCallProcessNotifyRoutines+0x213
fffff583
36877630 fffff8042d506552 : ffff9286
03ebf4b8 0000000000000000 fffff583
36877820 0000000000000000 : nt!PspExitProcess+0x70
fffff583
36877660 fffff8042d4d22e8 : 00000000
e0464645 0000000000000001 ffff9286
000e3c01 0000000ff3a46000 : nt!PspExitThread+0x5b2
fffff583
36877760 fffff8042d067fb7 : fffff583
36870101 0000000000000000 ffff9285
ff262650 0000000000000000 : nt!KiSchedulerApcTerminate+0x38
fffff583
368777a0 fffff8042d1f9d20 : 0000012b
f3e47260 fffff58336877850 0000000f
f42ff548 ffff928500000000 : nt!KiDeliverApc+0x487
fffff583
36877850 fffff8042d20725f : 00000000
00000c38 0000000000000000 00000000
00000000 ffff9285ff262650 : nt!KiInitiateUserApc+0x70
fffff583
36877990 00007ff85e1afa04 : 00000000
00000000 0000000000000000 00000000
00000000 0000000000000000 : nt!KiSystemServiceExit+0x9f
0000000f
f42ff4f8 0000000000000000 : 00000000
00000000 0000000000000000 00000000
00000000 0000000000000000 : 0x00007ff8
5e1afa04SYMBOL_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.