Repeated BSODs with different memory related bug checks. Possible DDR5/EXPO/XMP or hardware instability?

Question

System:

• Motherboard: MSI X870E P PRO WiFi
• CPU: AMD Ryzen 7 9850X3D
• RAM: Corsair CMH32GX5M2M6000Z36
  • 32 GB total
    • 2 × 16 GB
      • DDR5-6000
        • XMP enabled
          • VDD/SWA voltage averages around 1.360 V
• GPU: NVIDIA RTX 5060ti 8GB
• OS: Windows 11

Ive been having a few random crashes and im not sure what is triggering it. I'd attach my minidump zip file for reference and if someone could take a look and advise on next steps i'd appreciate it.

Answer 1

Your minidump files were not attached, please use this method to upload your minidump files for analysis.

Please do not upload a very large Memory.dmp file.

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... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 2

Random BSODs with memory-related stop codes can be caused by hardware, drivers, or software. For MEMORY_MANAGEMENT, Windows documents that bug check 0x0000001A indicates a severe memory management error occurred, and some parameter values specifically point to corrupted page tables, PTEs, PFNs, or hardware-related corruption.

A practical next path is:

1. Check the exact stop code and bug check details from the dump files
   • If a dump file was created, analyze it with WinDbg and the !analyze extension.
   • Dump files can contain the memory state at the time of the crash and may help identify whether a driver is involved.
2. Run Windows Memory Diagnostic
   • Open Control Panel.
   • Search for Memory.
   • Select Diagnose your computer's memory problems.
   • After the test completes, open Event Viewer and review the results.
   • In Event Viewer, memory diagnostic results can be found under Application and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug.
   • Event ID 2001 means no memory errors were detected.
3. Check Event Viewer around the crash time
   • Review the System log for critical errors that occurred at the same time as the BSOD.
   • Look for any faulting driver or related device errors.
4. Check Device Manager for driver or device faults
   • Open Device Manager.
   • Look for devices marked with an exclamation point.
   • Review the device properties and events for any driver failures.
5. If any drivers or system services were recently added or updated, remove or update them
   • Stop code errors are commonly triggered by new device drivers or system services.
6. If any hardware was recently added or changed, test without it if possible
   • New hardware or hardware incompatibility is a documented cause of bug checks.
7. Run manufacturer hardware diagnostics
   • If available from the motherboard or system vendor, run the supplied hardware diagnostics to help isolate RAM or other hardware faults.

For MEMORY_MANAGEMENT specifically, documented parameter examples include:

• 0x31: image relocation fix-up table or code stream corrupted, probably hardware error.
• 0x3f: inpage operation failed with CRC error.
• 0x403: page table and PFNs out of sync, probably hardware error.
• 0x411: a PTE has been corrupted.
• 0x41284: a PTE or the working set list is corrupted.
• 0x61946: an MDL being created is flawed, and the driver calling MmProbeAndLockPages is typically at fault.

That means the dumps matter: some 0x1A variants point more toward memory corruption or hardware, while others can point to a faulty driver.

If minidumps are available, the supported next step is to review them with WinDbg rather than guessing from XMP alone. If Windows Memory Diagnostic reports errors, that strongly supports a physical memory problem. If it reports no errors, focus next on dump analysis, Device Manager, Event Viewer, and any recently changed drivers or hardware.

---

References:

• Bug Check 0x1A: MEMORY_MANAGEMENT
• Bug check code reference
• Troubleshooting Windows unexpected restarts and stop code errors
• How to fix Error 0xA: IRQL_not_less_or_equal
• Bug checks (stop code errors)
• Advanced troubleshooting for stop code errors