The computer frequently experiences BSOD errors, typically daily.
The computer frequently experiences BSOD errors, typically daily.
Hey there, I see you're dealing with frequent BSODs. It sounds like a tough situation. With the components you listed—ranging from the CPU to the storage devices—it’s possible several factors could be at play. Let me know if you want help narrowing it down!
I experienced problems with BSODs during heavy RAM usage while running Prime95 on a DELL G5 5587 equipped with two 32 GB DDR4 CMSX32GX4M1A2666C18 modules. The RAM modules lacked built-in temperature sensors, but the laptop had a thermal sensor near the RAM area. After short stress tests, the sensor logged 75 °C and then triggered a BSOD repeatedly. The actual RAM temperature was likely much higher. The fix came from installing active cooling and adjusting the bottom chassis cover. Once those changes were made, the RAM sensor stayed at 55 °C even after two hours of Prime95 testing, and no more BSODs occurred.
To retrieve BSOD logs on Windows 11:
1. Open Event Viewer by pressing Win + X and selecting Event Viewer.
2. Navigate to Windows Logs > System, then click Filter Current Log.
3. Under Event sources, choose BugCheck and apply.
4. Alternatively, use Reliability Monitor by typing `perfmon /rel` in the Run dialog and checking for red "X" symbols indicating errors.
5. For deeper analysis, run WinDbg via PowerShell as admin and examine crash dumps at C:\Windows\Minidump.
These steps help identify crash causes and improve system stability.
I reviewed the Reliability Monitor (connected screen) and noticed a recurring issue with the ArmouryCrate from ASUS. It might be related, but the timing doesn’t match. There’s also a file linked to one of the key events. 070225-14203-01.dmp
Sure thing! Here’s a revised version of your message:
Hey, thanks for the screenshots. From what I observe—particularly around July 13 with the BSOD and system freezes—it seems like a genuine hardware fault rather than just a software issue. Based on past experiences, this kind of problem can often stem from XMP profile conflicts (overclocking too high for your motherboard), overheating RAM, especially with high-density or fast DDR5 kits, VRM temperature caps on the motherboard, or even unstable background services like Armoury Crate, which I saw crashing repeatedly in your logs.
I recommend trying these steps:
- Uninstall Armoury Crate and its associated services
- Enter BIOS and turn off XMP settings to test at JEDEC speeds
- Open the case side panel if possible to boost airflow
- Place a fan near the RAM or VRM area and see if stability improves
- Run MemTest86 overnight on a bootable USB drive—any memory instability will be detected
- Use HWInfo64 to monitor temperatures, focusing on VRM, RAM, and DIMM readings
Let me know what you find!
Appreciate the uploaded dump file—it gives a clear picture. The crash occurs during Windows memory management tasks, such as MiDecommitPages and MiFreeVirtualMemory, ultimately leading to a KeBugCheckEx. This indicates a major memory-related failure, likely due to RAM instability or poor memory handling. Next steps: turn off XMP settings in the BIOS and use standard JEDEC speeds (e.g., 4800 MHz) for your RAM. Even premium DDR5 modules may struggle at speeds above 6000 MHz depending on the motherboard firmware. Perform MemTest86+ overnight via a bootable USB drive to detect subtle memory issues that might not appear immediately. Check case ventilation, directing airflow toward the RAM and VRM areas—overheating can exacerbate problems, particularly with DDR5. Ensure your BIOS is up to date. Re-seat or swap RAM slots to test for faults. Use HWInfo64 to monitor temperatures and verify any DIMM or VRM temperature sensors. If possible, run the system with a single RAM stick before swapping, repeating the test. If issues persist, verify if Memory Integrity (Core Isolation/HVCI) is enabled in Windows Security—it can sometimes cause instability with high-speed DDR5 and XMP profiles. Temporarily disable it to see if the crash improves.
Have you looked for a software upgrade for the WD Black NVMe storage? It seems this particular version faced issues with 24H2 at first, but WD issued a patch to fix it.
The ASUS TUF Z690-Plus WiFi works well in most situations, but some users have noted occasional problems when using high-speed DDR5 at 6000+ MHz with XMP enabled. Under continuous load, VRM temps may rise, which can affect memory performance indirectly. XMP settings aren’t always optimized for every RAM-CPU pair. Even if the chip supports it, certain 12900KF modules might struggle at 6000 MHz due to silicon quality. For now, try running without XMP enabled. If stability improves, you can later adjust timings manually or use lower speeds like 5600 MHz with tighter settings. Begin by setting memory frequency to 5600 MHz, primary timings 34-36-36-76, Command Rate 2T, Gear Mode 2. Adjust VDD/VDDQ to 1.25–1.30 V, VCCSA to 1.10–1.20 V based on your IMC, and VDDQ_CPU around 1.15 V if possible. Keep secondary timings like tRFC and tFAW in Auto unless you plan further tweaks. Also, consider removing Armoury Crate, as it’s known for instability and crashes. Ensure your BIOS is fully updated, since ASUS has released several Z690 versions to enhance DDR5 support and memory training consistency. Let us know how this develops.
Verify your GPU drivers. The Radeon driver from 5-8-2025 caused a blue screen, so consider using a previous version.
Bugcheck Analysis Summary
Typically triggered by drivers handling invalid memory descriptor lists, such as calling MmUnlockPages multiple times with the same list. If a debugger is available, retrieve the stack trace.
Parameters:
- Arg1: 0000000000000099
- PTE/PFN: Corrupted
- Page Frame: 000000000071e20e
- Current Page: 0000000000000001
- State: 00000000007f910e
- Value: 32000
- Debugging Info:
Key Values:
- CPU usage: 3796 ms
- IO.Other.Mb: 0
- Write MB: 31
- Init CPU: 32000 ms
- Memory commit peak: 163 MB
- Version: 10.2505.01.02 amd64fre
Bug Details:
- Key: 1, CPU usage: 3796 ms
- Elapsed time: 33881 ms
- IO: Read/Mb: 9 MB
- Init: 32000 ms
- Memory: 163 MB peak
- Version: 10.0.27871.1001
Version Info:
- Code: LegacyAPI (0x4e)
- Target Model: 0x4e
- Debug Attributes:
- Error code: 0
- Progress: 100% completed
- Key attributes: CPU, IO, memory, version, etc.
Other Observations:
- No critical errors recorded.
- Possible causes include unstable RAM settings, driver conflicts, or faulty hardware.
You removed ArmouryCrate, selected XMP I, fetched the HWinfo file, and plan to perform a memory test during the night. The WD firmware was also updated. Appreciate your help!