BSOD with error Memory Management (1a)

Question

I get Memory Management crashes when playing games for a certain amount of time

I'm attaching the output of minidump file when run under windbg

28: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000411, The subtype of the BugCheck. Arg2: ffffd9811bdbc240 Arg3: 0000000514649880 Arg4: ffffd980f995ae10

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1515

Key  : Analysis.Elapsed.mSec
Value: 5705

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x1a

Key  : Bugcheck.Code.TargetModel
Value: 0x1a

Key  : Dump.Attributes.AsUlong
Value: 808

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Failure.Bucket
Value: 0x1a\_411\_dxgmms2!VIDMM\_RECYCLE\_RANGE::DebouncedDecommit

Key  : Failure.Hash
Value: {3cf167ce-a97f-6e02-59af-165134d0d3ef}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

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: 4853999

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

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: 1a

BUGCHECK_P1: 411

BUGCHECK_P2: ffffd9811bdbc240

BUGCHECK_P3: 514649880

BUGCHECK_P4: ffffd980f995ae10

FILE_IN_CAB: 042824-15421-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EpicWebHelper.

STACK_TEXT:
ffffc7039f786378 fffff8012c84ca41 : 000000000000001a 0000000000000411 ffffd9811bdbc240 0000000514649880 : nt!KeBugCheckEx ffffc7039f786380 fffff8012c641ae1 : 0000000000000000 0000000100000000 ffffc7039f7864e0 ffffa20c00000000 : nt!MiLockTransitionLeafPageEx+0x13a501 ffffc7039f7863e0 fffff8012cae53c0 : ffffa20c24830790 ffffa20c26ed5548 0000000000000000 fffff8012c693d4c : nt!MiDecommitPages+0xb51 ffffc7039f786e30 fffff8012cae619b : 0000000000000000 0000000000000000 ffffc7039f786f20 0000000000000000 : nt!MiDecommitRegion+0x80 ffffc7039f786ee0 fffff8012cae5e65 : 0000000000000000 fffff8012c655f89 ffff808b7c800380 ffff808b89382cff : nt!MmFreeVirtualMemory+0x2fb ffffc7039f787020 fffff8012c82c9e8 : ffffa20c233f3240 0000000000040000 0000000000000004 ffff808b7c800000 : nt!NtFreeVirtualMemory+0x95 ffffc7039f787080 fffff8012c81d290 : fffff801ae5b19e1 ffff808b97f5aee0 fffff801ae5c356b ffff808b97f5aee0 : nt!KiSystemServiceCopyEnd+0x28 ffffc7039f787218 fffff801ae5b19e1 : ffff808b97f5aee0 fffff801ae5c356b ffff808b97f5aee0 ffffa20c26451010 : nt!KiServiceLinkage ffffc7039f787220 fffff801ae5c34cd : 0000000000050000 ffffa20c26451628 ffff808b97f5a408 ffffa20c0492ec80 : dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+0x155 ffffc7039f787270 fffff801ae5c3278 : ffffa20c00000000 ffffa20c26451010 ffffc7039f787480 0000000000000001 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0x19d ffffc7039f7872d0 fffff8012c753665 : ffffa20c0492ec80 ffffc7039f787400 ffffa20c00000000 ffffa20c00000000 : dxgmms2!VidMmRangeCurationThread+0x88 ffffc7039f787380 fffff8012c6ed757 : ffffa20c233f3240 0000000000002f94 ffffa20c233f3240 fffff8012c753510 : nt!ExpWorkerThread+0x155 ffffc7039f787570 fffff8012c81c944 : ffffe10032aa2180 ffffa20c233f3240 fffff8012c6ed700 0000000000000000 : nt!PspSystemThreadStartup+0x57 ffffc7039f7875c0 0000000000000000 : ffffc7039f788000 ffffc7039f781000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+155

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.3296

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 155

FAILURE_BUCKET_ID: 0x1a_411_dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3cf167ce-a97f-6e02-59af-165134d0d3ef}

Followup: MachineOwner

Answer 1

Yes, please do.

Answer 2

Hi Yudhishthir,

I'm Sumit, here to answer your query at the Microsoft Community.

The problem is the GPU driver.

Please see the Display driver troubleshooting below:

Option 1: Try Rolling back the Display driver.

Right-click the Start button and select Device Manager.

Navigate to Display devices and expand it. Right-click your Display adapter.

Choose Properties.

On the Driver tab, click the Rollback Driver button to go back to the previous version.

Option 2. Remove the Display drivers completely and Install the newest copy of the driver, available from the OEM or the GPU maker. The steps for it are here:

https://www.yourwindowsguide.com/2022/02/troubl...

Eventually, after Windows restarts, check for Windows updates, or download the display driver from the computer manufacturer:

Download Intel Drivers and Software

https://www.intel.com/content/www/us/en/downloa...

Official Drivers | NVIDIA

https://www.nvidia.com/download/index.aspx

AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

https://www.amd.com/en/support

After the installation, see if your issue is resolved.

Disclaimer:

The links include a non-Microsoft website that would provide accurate and safe information. There is no need to buy paid products to fix your computers as they sometimes do more harm than good.

Answer 3

I've been consistently updating my nvidia game ready drivers and the has been happening before that so not exactly sure which version to rollback to, and the device manager doesn't even give me the option to rollback as the button is disabled.

I also get errors when trying to update windows - I'm installing the windows update 2024-04 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5036980) and it gives me Install error - 0x80070002

Answer 4

Thank you. Can you use Method 2 to use DDU to remove all the drivers.

We will fix the 23H2 update later.

Answer 5

I used DDU to re-install the drivers but there was still crashes when running games.