Windows 10: BSOD Crash: VIDEO_MEMORY_MANAGEMENT_INTERNAL 10E

Hi,


I'm crashing to a BSOD consistently about every hour. I've run the MEMORY.DMP file through a memory debugger and it's always the same after every crash. What's odd is the computer only crashes when I'm using Unity though it did once while using Maya, but does so very consistently. I've looked at dozens of forums and documentations but none of them seem to help. I've attached the debug from the MEMORY.DMP file at the bottom.


These are the things I've tried:

• Reinstalled and updated both Intel Graphics and NVIDIA graphics drivers
• Updated Direct X
• Updated Windows
• Disabled hardware acceleration in the Registry Editor
• Reinstalling Unity

My computer: Razer Blade 15 2018 Advanced

Intel i7-8750H

IntelR UHD Graphics 630

NVIDIA GTX 1060 Max-Q

16 GB RAM

512 GB SSD


Thanks for any help you can provide.


A download for the MEMORY.DMP file can be found here.


Debug:


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: 000000000000001d, The subtype of the bugcheck:Arg2: ffffac892c0e0b10Arg3: 0000000000000000Arg4: 0000000000000000


...



SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::UpdatePageTable+2ced0MODULE_NAME: dxgmms2IMAGE_NAME: dxgmms2.sysIMAGE_VERSION: 10.0.19041.546STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 2ced0FAILURE_BUCKET_ID: 0x10e_1d_dxgmms2!VIDMM_GLOBAL::UpdatePageTableOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {71cfaed7-afd6-912e-e10e-336c7c7acd87}Followup: MachineOwner

:)

 

Frequent BSOD's VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

Hi,

Thank you for posting your query in Microsoft Community.

I understand your concern regarding the issue that you are facing.

I suggest you to refer the link below and check if helps

BSOD Finding and fixing them



Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help

 

Frequent BSOD's VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

Hello there,

Since a few weeks I have been having trouble with frequent crashes on my pc.

These crashes only happen when I'm playing games (in this case both CS:GO and rocket league), and have never occured during any other activity.

I have already made sure to check that I have all the latest drivers installed and that windows had all the latest updates.

I have a computer with the following specs:

http://speccy.piriform.com/results/QdEpXIsqsdf2281bDW4Y8qI

Processor
Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz

Video Card 1
NVIDIA GeForce GTX 970

Video Card 2
Intel(R) HD Graphics 4600

Memory
8.1 GB

Operating System
Microsoft Windows 10 (build 10240), 64-bit

For the dump files please refer to this OneDrive folder:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

This is my most recent dump file:

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: 000000000000002e, The subtype of the bugcheck:

Arg2: ffffc00059e2b8e0

Arg3: ffffc0005c214010

Arg4: ffffd00171e14730
Debugging Details:

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

BUGCHECK_STR: 0x10e_2e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
LAST_CONTROL_TRANSFER: from fffff80104be3c3d to fffff80067162240
STACK_TEXT:

ffffd001`71e146c8 fffff801`04be3c3d : 00000000`0000010e 00000000`0000002e ffffc000`59e2b8e0 ffffc000`5c214010 : nt!KeBugCheckEx

ffffd001`71e146d0 fffff801`07f21e81 : ffffc000`630cbc00 ffffc000`59e2b8e0 ffffc000`59e2b8e0 ffffe000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xcd

ffffd001`71e14710 fffff801`07f80167 : ffffc000`59e2b8e0 ffffe000`8a979e40 ffffe000`8a979ec0 ffffc000`5c214010 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x121

ffffd001`71e14760 fffff801`07f5e885 : 00008086`000007d0 00000000`00000002 ffffd001`71e14959 00000000`000000a0 : dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x19b

ffffd001`71e14840 fffff801`0553c486 : ffffe000`8a9873b0 ffffd001`71e14959 00000000`00000010 fffff801`0553c410 : dxgmms2!VIDMM_GLOBAL::InvalidateAllVirtualAddresses+0x31

ffffd001`71e14870 fffff801`05552255 : ffffe000`8ceaa4c0 00000000`000000a0 ffffe000`8ceaa4c0 00000000`00000000 : dxgkrnl!DXGADAPTER:repareToReset+0x76

ffffd001`71e148c0 fffff801`07f2e481 : ffffe000`8ceaa4c0 ffffd001`71e14959 00000000`00cbb768 fffff801`07f86bea : dxgkrnl!TdrIsRecoveryRequired+0x1c5

ffffd001`71e148f0 fffff801`07f5b0cc : ffffe000`8a982000 ffffd001`71e14b00 ffffe000`8a982000 ffffe000`8a984000 : dxgmms2!VidSchiReportHwHang+0x3fd

ffffd001`71e149c0 fffff801`07f15cac : ffffe000`8a984000 00000000`00c9b133 00000000`00000001 00000000`00000002 : dxgmms2!VidSchiCheckHwProgress+0x137bc

ffffd001`71e14a00 fffff801`07f53403 : ffffe000`8a984000 ffffd001`71e14bc8 ffffe000`8c34b680 ffffe000`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x33c

ffffd001`71e14b90 fffff801`07f533e0 : ffffe000`8a984000 00000000`00000000 ffffe000`857af840 ffffe000`857af800 : dxgmms2!VidSchiRun_PriorityTable+0x1f

ffffd001`71e14bc0 fffff800`670fae88 : ffffe000`857af840 ffffd001`71e14c90 fffff800`67377180 fffff800`67167250 : dxgmms2!VidSchiWorkerThread+0x80

ffffd001`71e14c00 fffff800`67167326 : fffff800`67377180 ffffe000`8a985840 fffff800`673ed740 00000000`00000000 : nt!PspSystemThreadStartup+0x58

ffffd001`71e14c60 00000000`00000000 : ffffd001`71e15000 ffffd001`71e0f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:

dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121

fffff801`07f21e81 488bcb mov rcx,rbx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 55bec217
IMAGE_VERSION: 10.0.10240.16425
BUCKET_ID_FUNC_OFFSET: 121
FAILURE_BUCKET_ID: 0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange
BUCKET_ID: 0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x10e_2e_dxgmms2!vidmm_cpu_host_aperture::unmaprange
FAILURE_ID_HASH: {ebf2c813-41e1-4d73-9be7-00c514787ed3}
Followup: MachineOwner

I am really thankful for any help that can be given.

Thank you in advance.

 

BSOD with error code: VIDEO_MEMORY_MANAGEMENT_INTERNAL

This crash happens pretty regularly; never twice in a single day, but at least once or twice a month.

The code is always VIDEO_MEMORY_MANAGEMENT_INTERNAL.

The BSOD is also always colored strangely when I get the above code; it looks like the colors are inverted or somehow changed, and it definitely doesn't look like it's supposed to happen.

My computer always boots successfully after the crash.

My graphics card's drivers are up to date.

DMP Files

MSinfo File

I'd provide a photo of what the glitched BSOD looks like, but I forgot to take one.

Looking for a permanent fix; this crash has been happening for at least a year and a half.

***Original title: Video Memory Management Internal and a glitched "blue"screen.***