Windows 10: Error "video memory management internal" causing PC to crash

Many instances while I was playing games my pc would crash, my monitors would retain the image for some 30s and the pc would restart, when that happens my audio would still be playing but everything else freezes. Also most of these crashes happened while COD: Warzone was getting into a game lobby but some other while I was closing the game or playing other games.


Here's the crash file:


[COLOR=rgba30, 30, 30, 1]************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff807`6aa00000 PsLoadedModuleList = 0xfffff807`6b62a2f0Debug session time: Thu Jan 21 01:01:28.989 2021 UTC - 5:00System Uptime: 0 days 8:27:25.619Loading Kernel Symbols.............................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list............For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff807`6adf5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff081`7736e090=000000000000010e2: kd> !analyze -vERROR: FindPlugIns 8007007b******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_MEMORY_MANAGEMENT_INTERNAL 10eThe 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 thatsomebody can pinpoint what lead to this condition.Arguments:Arg1: 0000000000000033, The subtype of the bugcheck:Arg2: ffffd98d7359ddb0Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5264 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-6L7VHAO Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 24950 Key : Analysis.Memory.CommitPeak.Mb Value: 87 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 10eBUGCHECK_P1: 33BUGCHECK_P2: ffffd98d7359ddb0BUGCHECK_P3: 0BUGCHECK_P4: 0CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: dwm.exeSTACK_TEXT: fffff081`7736e088 fffff807`7c7b3ad0 : 00000000`0000010e 00000000`00000033 ffffd98d`7359ddb0 00000000`00000000 : nt!KeBugCheckExfffff081`7736e090 fffff807`7ee67f45 : 00000000`00000000 ffffd98d`7359deb0 ffffb788`0f7e7000 00000000`00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0fffff081`7736e0d0 fffff807`7edd253a : ffffd98d`7359ddb0 00000000`00000000 ffffd98d`785fc320 00000000`00000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27879fffff081`7736e110 fffff807`7ee406a9 : ffffd98d`7359ddb0 00000000`00000000 ffffd98d`785fc320 ffffb788`0f6c5010 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xefffff081`7736e140 fffff807`7ee40115 : 00000000`00000000 ffffd98d`785fc320 ffffd98d`7359ddb0 ffffb788`10310080 : dxgmms2!VIDMM_PROCESS:estroyAdapterInfo+0xe5fffff081`7736e170 fffff807`7edd257e : ffffd98d`7879a220 fffff081`7736e329 ffffb788`0f6c5010 01000000`00100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9fffff081`7736e230 fffff807`7c5545b9 : 00000000`00000030 00000000`00000799 00000000`80007500 00000000`00000000 : dxgmms2!VidMmCloseAdapter+0x1efffff081`7736e260 fffff807`7c51323f : ffffb788`0c713000 00000000`00000000 ffffb788`0f97ea90 fffff807`6ac61553 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2dfffff081`7736e290 fffff807`7c4d9c55 : ffffd98d`7879a220 ffffd98d`00000002 ffffd98d`7879a220 ffffb788`0f6c5010 : dxgkrnl!DXGPROCESS:estroyAdapterInfo+0x143fffff081`7736e390 fffff807`7c4d873d : ffffb788`0f6c3000 fffff807`00000001 ffffb788`0f6c3000 ffffd98d`73e92ed0 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9fffff081`7736e420 fffff807`7c5186c9 : ffffb788`19ccb620 fffff081`7736e570 00000000`00000288 ffffd98d`73e92de0 : dxgkrnl!DXGADAPTER:estroyHandle+0x11dfffff081`7736e470 fffff807`7c5138e5 : ffffd98d`73e92de0 00000000`00000000 ffffd98d`73e92de0 00000000`00000000 : dxgkrnl!DXGPROCESS:estroy+0x341fffff081`7736e6e0 fffff807`7c406b67 : 00000000`00000000 ffffd98d`73e92de0 ffffb788`0c6bb430 00000000`00000000 : dxgkrnl!DXGPROCESS:estroyDxgProcess+0x105fffff081`7736e830 fffff807`6b03759f : 00000000`00000000 ffffb788`1030e080 00000000`000005bc 00000000`00000000 : dxgkrnl!DxgkProcessNotify+0xf7fffff081`7736e890 fffff807`6b062894 : ffffb788`1030e000 ffffb788`1030e080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213fffff081`7736e960 fffff807`6b106562 : ffffb788`103104b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70fffff081`7736e990 fffff807`6b109a9e : ffffb788`d00002fe 00000000`00000001 00000000`00000000 0000009f`e913b000 : nt!PspExitThread+0x5b2fffff081`7736ea90 fffff807`6ae076f1 : ffffb788`1030e080 ffffb788`10310080 fffff081`7736eb80 ffffffff`ffffffff : nt!NtTerminateProcess+0xdefffff081`7736eb00 00007ffa`e0a6c534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc0000009f`e927f978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`e0a6c534SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+27879MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]dxgmms2[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: dxgmms2.sysIMAGE_VERSION: 10.0.19041.1134STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 27879FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFOOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}Followup: MachineOwner---------[/COLOR]

:)

 

video memory management internal

video memory management internal

I keep getting this error causing my machine to reboot. It just began this week.

Windows 10

MSI laptop

 

Crash- "VIDEO MEMORY MANAGEMENT INTERNAL" Error

Hi everyone.

I'm having a problem with my laptop. I have a hp 15-ac128ns with a i7-6500U and video card AMD Radeon r5 m330 running Windows 10. My computer will crash with a 'VIDEO MEMORY MANAGEMENT INTERNAL' error. I tried to update my video card drivers but didn't work,
I asked for help in the Microsoft support answer desk and the person who attended me tried to update the drivers and tried other solutions but it didn't work. But this is not all, the problem has gone worst. Before I could use the computer with relative normality
because this problem didn't appear very often but know it will crash a couple of minutes since I start using it.

Can someone help me please?

Thank you!

 

Crashes with the Video memory management internal error

Original title:- new computer problems

I got a new acer aspire all in one computer zc-700g and I keep getting a video memory management internal error and computer restarts and I can't get my drivertuner program to work at all anyone got any ideas what is wrong with this thing?