BSOD memory_management

Sonofbear · May 4, 2025

Hi,

can anyone help me on the bsod memory_management

i just swap my 32gb RAM to 64GBRAM . after 3 weeks, i starting getting the BSOD (happen 2 times in 3 days)

i suspect i got a defect RAM

is there a way to tell which slot of the RAM is faulty as the BSOD happen randomly and i not able to test 1 by 1

here are the dump file and the perfmon https://drive.google.com/file/d/1vl-ntpKbQl8iLAttbrSIEIRMrSUvch4K/view?usp=sharing

this is what i got when i try debug the minidump

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  notepad.exe

STACK_TEXT:  
ffffab04`7c8aef48 fffff800`7206fe1a     : 00000000`0000001a 00000000`00041792 ffffbe3f`fabb4430 00000800`00000000 : nt!KeBugCheckEx
ffffab04`7c8aef50 fffff800`7200cfc6     : 00000000`00000000 00000000`00000000 00000000`0000039f ffffbe3f`fabb4430 : nt!MiDeleteVa+0x153a
ffffab04`7c8af050 fffff800`7200d0db     : ffffbe5f`1ffd5da0 ffffe285`928ed700 ffffab04`00000000 ffffab04`7c8af4c0 : nt!MiWalkPageTablesRecursively+0x776
ffffab04`7c8af0f0 fffff800`7200d0db     : ffffbe5f`00000000 ffffe285`928ed700 ffffab04`00000001 ffffab04`7c8af4d0 : nt!MiWalkPageTablesRecursively+0x88b
ffffab04`7c8af190 fffff800`7200d0db     : ffffbe5f`00000000 ffffe285`928ed700 ffffab04`00000002 ffffab04`7c8af4e0 : nt!MiWalkPageTablesRecursively+0x88b
ffffab04`7c8af230 fffff800`7200a0db     : 00000000`00000000 ffffe285`928ed700 00000000`00000003 ffffab04`7c8af4f0 : nt!MiWalkPageTablesRecursively+0x88b
ffffab04`7c8af2d0 fffff800`7206e6b1     : ffffab04`7c8af470 ffffe285`00000000 ffffbe3e`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffffab04`7c8af3d0 fffff800`7201d2c8     : 00000000`00000001 ffffe285`00000000 ffffe285`928ed550 ffffe285`8c54d080 : nt!MiDeletePagablePteRange+0x4f1
ffffab04`7c8af6e0 fffff800`72501199     : ffffe285`00000000 00000000`00000000 ffffe285`00000000 ffffe285`928ed080 : nt!MiDeleteVad+0x378
ffffab04`7c8af7e0 fffff800`724ffd78     : ffffe285`9c4d6810 ffffe285`95da88a0 ffffe285`8c54d080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffab04`7c8af810 fffff800`724564c3     : ffffe285`9c4d5eb0 ffffe285`9c4d5eb0 ffffe285`9c4d6810 ffffe285`928ed080 : nt!MiCleanVad+0x30
ffffab04`7c8af840 fffff800`724dfaf0     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffe285`928ed080 : nt!MmCleanProcessAddressSpace+0x137
ffffab04`7c8af8c0 fffff800`724fb4fa     : ffffe285`928ed080 ffff928b`718066b0 00000000`00000000 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffffab04`7c8af950 fffff800`72509f2e     : ffffe285`00000000 00000000`00000001 00000000`00000000 000000b3`757de000 : nt!PspExitThread+0x5f6
ffffab04`7c8afa50 fffff800`72211f08     : ffffe285`928ed080 ffffe285`8c54d080 ffffab04`7c8afb40 ffffe285`928ed080 : nt!NtTerminateProcess+0xde
ffffab04`7c8afac0 00007ffe`ee66da74     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b3`754bf8b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`ee66da74


MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND: .process /r /p 0xffffe285928ed080; .thread 0xffffe2858c54d080 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Bjoolz · May 4, 2025

With Memory_Management we rarely care about stack, unlike almost all other crash errors where the stack is the most important part, because we already know that it's a memory error. What's more interesting with these is the the arguments (Arg1-4 at the top of the automatic analysis). If it mentions page file or inpage error, it's from the page file (storage). If not, it happened in RAM or the memory controller (CPU).

And you want to check this over multiple crashes because a memory issue isn't necessarily instantly detected, it could have happened in RAM and not detected until it was on storage or vice versa.

It's not letting me download the dump file without signing in to google, attach it to the forum post instead. And if you have more than one dump file, attach all of them. If you have any issues doing so, these are the instructions I normally give which should work:

Quote

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.