VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) error and my PC no longer detects my GPU

Question

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) error and my PC no longer detects my GPU

Anonymous

Hello,

I have a 2 month old PC I built myself with an Nvidia GeForce RTX 4060 GPU. Periodically the GPU has had issues where the PC can't detect it, and the only thing that has fixed it has been reseating the GPU. Today the computer crashed and now even with reseating it no longer detects the GPU. I've tried reinstalling my drivers with DDU and Nvidia but they can't install without detecting the GPU, and I can also no longer detect it in BIOS or Device Manager. The GPU fans turn on but I can't detect other function from it. I analyzed the dump file and received the following (full file linked here: 012725-11812-01.dmp). Thanks so much in advance for any advice you're able to provide.

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: 0000000000000034, The subtype of the BugCheck:
Arg2: 000000000000000e
Arg3: 0000000000000003
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 765

    Key  : Analysis.Elapsed.mSec
    Value: 876

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    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_34_dxgmms2!VIDMM_RECYCLE_HEAP::RemoveRangeFromTree

    Key  : Failure.Hash
    Value: {24389f0c-d0ce-ca8b-ab73-4431ef73e95e}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 24a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

BUGCHECK_CODE:  10e

BUGCHECK_P1: 34

BUGCHECK_P2: e

BUGCHECK_P3: 3

BUGCHECK_P4: 0

FILE_IN_CAB:  012725-11812-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff910ec60e5080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NVIDIA app.exe

STACK_TEXT:  
fffff885`0fe5e448 fffff804`73ac1316     : 00000000`0000010e 00000000`00000034 00000000`0000000e 00000000`00000003 : nt!KeBugCheckEx
fffff885`0fe5e450 fffff804`758524a2     : ffffe505`f76539b8 00000000`00000002 ffff910e`ada7b020 ffffe506`0b59c690 : watchdog!WdLogSingleEntry5+0x156
fffff885`0fe5e4e0 fffff804`7584ea87     : 00000000`00000003 ffff910e`ada7b020 ffffe506`0b59c690 fffff804`75793c8b : dxgmms2!VIDMM_RECYCLE_HEAP::RemoveRangeFromTree+0x82
fffff885`0fe5e520 fffff804`75849f63     : ffffe506`1ed2e340 fffff885`0fe5e619 ffffe506`0b59c690 ffffe505`ecb58220 : dxgmms2!VIDMM_RECYCLE_HEAP::ShiftTreeMembershipOnDebouncedStateChange+0x1bf
fffff885`0fe5e570 fffff804`75849b5e     : ffff910e`ada7b010 ffff910e`ada7b618 ffffe505`f7b72ee8 ffffe506`1ed2e340 : dxgmms2!VIDMM_RECYCLE_RANGE::FinalizedUnlock+0xdf
fffff885`0fe5e5a0 fffff804`75794134     : ffffe506`1af25140 00000000`00000001 00000000`00000000 ffff910e`ada7b010 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::~VIDMM_RECYCLE_HEAP_MGR+0x10e
fffff885`0fe5e680 fffff804`7583f844     : ffffe505`f6116810 fffff885`0fe5e709 00000000`00000000 00000000`e0676499 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::`vector deleting destructor'+0x14
fffff885`0fe5e6b0 fffff804`757946c2     : ffff910e`abcf3010 ffffe505`f6116810 ffff910e`a30fcbb0 00000000`00000001 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0xdc
fffff885`0fe5e770 fffff804`757946ee     : ffffe505`f76538a0 fffff885`0fe5e900 ffff910e`a3273000 fffff804`e067431a : dxgmms2!VIDMM_PROCESS::`scalar deleting destructor'+0xe
fffff885`0fe5e7a0 fffff804`73994095     : 00000000`00000118 00000000`ffffffff 00000000`00000353 ffffe505`f76539b8 : dxgmms2!VidMmTerminateProcess+0xe
fffff885`0fe5e7d0 fffff804`7388cb59     : 00000000`00000000 fffff885`0fe5e900 ffff910e`a3279058 00000000`00000000 : dxgkrnl!VidMmTerminateProcessX+0x59
fffff885`0fe5e800 fffff804`73944e1d     : ffffe506`02979758 ffffe505`f76538a0 ffffe505`f76538a0 ffffe506`02979700 : dxgkrnl!DXGPROCESS::Destroy+0x795
fffff885`0fe5ea40 fffff804`73943cbf     : ffffe505`f76538a0 ffffe505`f76538a0 ffffe506`02979758 ffffe505`e51ad000 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0xe5
fffff885`0fe5eb20 fffff804`bafb6cae     : ffffe506`02979600 ffffe506`02979660 00000000`00006e7c ffffe505`de781720 : dxgkrnl!DxgkProcessCallout+0x11f
fffff885`0fe5ecd0 fffff804`76047d3e     : ffffe506`02979660 ffffe506`02979660 fffff804`76255480 fffff804`760db39a : win32k!DxDdProcessCallout+0x6e
fffff885`0fe5ed00 fffff804`7525757e     : fffff885`0fe5f090 00000000`00000001 fffff885`0fe5f090 ffff910e`b2880930 : win32kbase!GdiProcessCallout+0x2be
fffff885`0fe5ed80 fffff804`760ed2b4     : 00000000`00000000 00000000`00000001 00000000`00000000 ffff910e`c24b5080 : win32kfull!W32pProcessCallout+0x15e
fffff885`0fe5edb0 fffff804`760ed03f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatchWorker+0x268
fffff885`0fe5ef20 fffff804`bafb1547     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatch+0xf
fffff885`0fe5ef50 fffff804`bafb1303     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!W32SessionAttachAndCalloutDispatch+0x67
fffff885`0fe5efe0 fffff804`e0d8b289     : ffff824f`0815a708 fffff885`0fe5f090 ffff910e`c24b5080 00000000`00000001 : win32k!W32CalloutDispatchThunk+0x13
fffff885`0fe5f020 fffff804`e0cbc95e     : ffff910e`c24b5080 fffff885`0fe5f0b0 00000000`00000000 fffff804`e0d5fb31 : nt!ExCallCallBack+0x3d
fffff885`0fe5f050 fffff804`e0d5ecf2     : ffff910e`a7ab6de0 00000000`00000000 ffff910e`a7ab6de0 ffff910e`c60e5080 : nt!PspExitLastThread+0x216
fffff885`0fe5f0e0 fffff804`e0d5e394     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x772
fffff885`0fe5f1d0 fffff804`e066e00c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x34
fffff885`0fe5f210 fffff804`e0a7e930     : 00000059`4360f6c0 fffff885`0fe5f2b0 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x47c
fffff885`0fe5f2b0 fffff804`e0a8d40d     : ffff910e`c60e5080 fffff885`0fe5f4e0 00000059`4360f5a8 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff885`0fe5f3f0 00007ffa`f0c9acb4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xad
00000059`4360f588 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`f0c9acb4

SYMBOL_NAME:  dxgmms2!VIDMM_RECYCLE_HEAP::RemoveRangeFromTree+82

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.2454

STACK_COMMAND:  .process /r /p 0xffff910ec24b5080; .thread 0xffff910ec60e5080 ; kb

BUCKET_ID_FUNC_OFFSET:  82

FAILURE_BUCKET_ID:  0x10e_34_dxgmms2!VIDMM_RECYCLE_HEAP::RemoveRangeFromTree

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {24389f0c-d0ce-ca8b-ab73-4431ef73e95e}

Followup:     MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

Hi RyanKD

Welcome to the Microsoft Community

Understanding that your GPU periodically has issues that are not detected by your PC

The dump analysis you provided shows a system crash with a VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x10E) error check. This particular error check is related to the Video Memory Manager experiencing an unrecoverable condition. The following are the key details of the dump analysis:

Error check code: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

This indicates a problem with the video memory management system. Subtype Arg1: 0000000000000034 Indicates a specific problem in the internal operation of the Video Memory Manager.

Faulty module: dxgmms2.sys

The module at fault is dxgmms2.sys, which is a system file for the DirectX graphics memory management subsystem. This file is responsible for managing video memory and is part of the Windows graphics subsystem.

Fault function: VIDMM_RECYCLE_HEAP::RemoveRangeFromTree+82

The crash occurs in the RemoveRangeFromTree function of the VIDMM_RECYCLE_HEAP class, which indicates a problem with video memory management or reclamation.

Process name: NVIDIA app.exe

The process running at the time of the crash is related to the NVIDIA application, which may indicate that the crash is related to the NVIDIA graphics driver or software.

Virtualization Flag:

The presence of the virtualization flag indicates that the system may have virtualization enabled. While this is not necessarily the cause of the crash, it may interact with graphics operations.

Solutions

Driver issues:

Try uninstalling the driver and reinstalling it in Device Manager, find your GPU in your Device Manager right click Uninstall Device and check Remove this device driver. Restart your computer and go to NVIDIA's website to download and install the latest driver for your graphics card model.

Corrupted system files:

Try to run the System File Checker and DISM utility to repair possible system file corruption

At the administrator command prompt, run

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Hardware issues:

Although uncommon, hardware issues such as GPU failure or insufficient power can cause similar crashes. Consider testing the GPU on another system or using a different GPU on the same system to troubleshoot hardware problems.

Software conflicts:

Check for recently installed software that may conflict with the graphics driver, such as third-party tools that modify system settings or graphics performance.

Virtualization settings:

If virtualization is not necessary for your workload, consider disabling it in the BIOS/UEFI setup to see if that solves the problem.

Windows Updates:

Make sure your Windows operating system is up-to-date, as updates may contain important fixes for system stability and compatibility.

If the problem persists after trying the above solutions, consider contacting NVIDIA Support or your system manufacturer for further assistance, especially if the problem seems to be related to a specific hardware or software configuration.

Contact me if you need anything else.

Best wishes

Merek.Z - MSFT | Microsoft Community Support Specialist