Glad to help!
BSOD Memory_Management mainly while using browser, need help
Started a few months ago which happens randomly while I'm using chrome
But the past few days it has gotten worse to the point that I'm having multiple crashes a day
Sometimes it even crashes immediately after reboot before I did anything
I tried updating my gpu driver and using other browsers, didn't work
I've created and analyze the minidump file as follow:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008886, The subtype of the BugCheck.
Arg2: ffffea8007fbeca0
Arg3: ffffea8007f8ecd0
Arg4: 0000000000000401
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1655
Key : Analysis.Elapsed.mSec
Value: 1660
Key : Analysis.IO.Other.Mb
Value: 14
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 26
Key : Analysis.Init.CPU.mSec
Value: 2265
Key : Analysis.Init.Elapsed.mSec
Value: 94184
Key : Analysis.Memory.CommitPeak.Mb
Value: 97
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Failure.Bucket
Value: 0x1a_8886_dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit
Key : Failure.Hash
Value: {a1380b1b-41df-9652-55a8-bdc8d44043bc}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 8886
BUGCHECK_P2: ffffea8007fbeca0
BUGCHECK_P3: ffffea8007f8ecd0
BUGCHECK_P4: 401
FILE_IN_CAB: 111923-12828-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: chrome.exe
STACK_TEXT:
ffffc182`b93ce848 fffff806`4122fbf0 : 00000000`0000001a 00000000`00008886 ffffea80`07fbeca0 ffffea80`07f8ecd0 : nt!KeBugCheckEx
ffffc182`b93ce850 fffff806`4129649a : 00000000`00000002 00000000`00000000 00000000`002a94ee fffff806`4129bb9e : nt!MiUnlinkPageFromList+0xcb0
ffffc182`b93ce8e0 fffff806`412879c2 : 00000002`a94eeb80 00000000`00000000 ffffc182`b93cea11 fffff279`00000000 : nt!MiDeleteTransitionPte+0x12a
ffffc182`b93ce960 fffff806`4165c4dd : ffffaf8a`031df040 ffffaf8a`0727aa98 ffffaf8a`00000001 ffffaf8a`00000000 : nt!MiDecommitPages+0xc32
ffffc182`b93cf530 fffff806`4165bb43 : ffffc182`b93cf6b0 00000000`00000000 ffffc182`b93cf6b0 ffffaf8a`0727aa70 : nt!MiDecommitRegion+0x7d
ffffc182`b93cf5b0 fffff806`4165b435 : ffffd903`54a00100 fffff806`4123c3b2 ffffd903`54a00340 ffffc182`b93cf9ff : nt!MmFreeVirtualMemory+0x6d3
ffffc182`b93cf700 fffff806`41410ef5 : ffffaf8a`031df040 00000000`00000000 00000000`00000103 00000000`00000000 : nt!NtFreeVirtualMemory+0x95
ffffc182`b93cf760 fffff806`41402310 : fffff806`764c8abc ffffaf8a`023afba0 ffffaf8a`023af5a0 00000000`00000300 : nt!KiSystemServiceCopyEnd+0x25
ffffc182`b93cf8f8 fffff806`764c8abc : ffffaf8a`023afba0 ffffaf8a`023af5a0 00000000`00000300 fffff806`764cafb7 : nt!KiServiceLinkage
ffffc182`b93cf900 fffff806`764cbbfa : 00000000`00020000 ffffd903`5d671248 ffffd903`5d650420 ffffaf8a`023af5a0 : dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+0x160
ffffc182`b93cf950 fffff806`764cbca6 : fffff806`00000000 ffffaf8a`023af5a0 00000000`00000000 fffff806`41d25440 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0x12a
ffffc182`b93cf9c0 fffff806`764cbac1 : fffff806`41d25440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::CurationThread+0x7a
ffffc182`b93cfa40 fffff806`412c46b5 : ffffaf8a`031df040 fffff806`4170bcb0 ffffaf89`ed119a60 ffffaf89`00000000 : dxgmms2!VidMmRangeCurationThread+0x11
ffffc182`b93cfa70 fffff806`413078e5 : ffffaf8a`031df040 00000000`00000080 ffffaf89`ed0b1200 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffffc182`b93cfb10 fffff806`41406368 : ffff9980`7fee6180 ffffaf8a`031df040 fffff806`41307890 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc182`b93cfb60 00000000`00000000 : ffffc182`b93d0000 ffffc182`b93c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+160
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.3684
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 160
FAILURE_BUCKET_ID: 0x1a_8886_dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a1380b1b-41df-9652-55a8-bdc8d44043bc}
Followup: MachineOwner
Hope someone can help me with this
Windows for home | Windows 10 | Performance and system failures
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.
6 answers
Sort by: Most helpful
-
Anonymous
2023-11-19T17:23:48+00:00 Hi, I did exactly what you suggest, ddu and install a stable driver
Now I'll wait and see if this work
Thank you
-
DaveM121 891.6K Reputation points Independent Advisor2023-11-19T16:35:52+00:00 Your minidump file does indicate that it is the device driver on your graphics card that is causing the system to crash
You should completely remove the current graphics card device driver using the widely available free DDU utility, then restart your PC and go to the support page for your PC on the manufacturer's website to download and install their recommended version of the graphics card device driver.
A slightly older version of that driver is more stable than the latest version.
-
Anonymous
2023-11-19T16:33:40+00:00 Hi, I uploaded the minidump here:
https://1drv.ms/u/s!Aior97a1vtZayVVDGPYY0Yjtk7My?e=apiCWD
Thank you for helping
-
DaveM121 891.6K Reputation points Independent Advisor2023-11-19T12:17:27+00:00 Hi, I am Dave, I will help you with this.
Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.
Open Windows File Explorer.
Navigate to C:\Windows\Minidump
Copy any minidump files onto your Desktop, then zip those up.
Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.
Then post the link here to the zip file, so we can take a look for you.