Two memory-related BSODs occurred on your new computer. Need assistance?
Two memory-related BSODs occurred on your new computer. Need assistance?
Hey there, I've been facing some issues with my PC lately. Everything seemed fine after four months of building it, but now I'm experiencing problems. Yesterday, YouTube loaded slowly even with Adblock enabled, which was unusual before. I updated my Windows and GPU drivers, but the issue persisted. Recently, I encountered two random BSODs—one saying "attempted execute of noexecute memory" (0xFC) and another with "memory management" (0x1A), indicating a corrupted PTE. I ran the diagnostic tool from Windows 10, but it didn't show any errors. I also used sfc /scannow, which repaired some files. The memory management BSOD happened when I switched from Baldur's Gate 3 to the desktop to close Chrome, and it crashed immediately afterward. I still need to run a chkdsk scan and possibly use memtest86 or disable XMP, though everything has been functioning well so far. I'm unsure what to do and why this is happening, so any advice would be greatly appreciated. Attached are the relevant reports. Note: perfmon /report didn't complete its scan, so I couldn't submit it. Thanks! OS - W10 x64 | Age of system: 4 months | OS install time: 4 months | i7 13700K RTX 4090 | Suprim X (Air cooled) | MSI PRO Z790-A WiFi DDR5 | MSI MPG A1000G PCIE5 1000W Corsair Vengeance 64Go 5200MHz CL40 Desktop PC | minidump.zip
Adjusting hardware acceleration in your browser may trigger BSODs. YouTube has been experiencing playback issues with ad blockers recently. You might find it helpful to search for bug fixes or code error checks online.
Both issues stem from memory problems. One involved storage drivers. RAM and storage often appear similar since low-priority data in RAM is written to disk in the page file, then moved back to RAM when needed—making it seem like storage until it's active again. The page file behaves much like RAM in many ways. Troubleshooting with just two dump files is uncertain; you usually need to search through many files for clues. The CPU might be the culprit because it has a memory controller. I question whether the GPU is actually the source. Remember, checkdisk only verifies NTFS structures, not the disk itself. I've encountered many bad drives where checkdisk fails to flag problems. If Memtest detects errors, that's a positive sign. Memory testing tools are less dependable with DDR4 and newer chips—Memtest86+ recently got an update for DDR5, though I'm unsure of its impact. A clean scan offers little value. I prefer running the system normally, one stick at a time. For drive checks, it seems you likely have a modern NVMe SSD; newer SSDs often lack robust self-diagnostics (SMART). I've seen hundreds of faulty NVMe drives, and SMART reports rarely show failures. The XMP profile for a 5200 is mild and remained stable for months. Windows typically omits smbios from dump files to reduce size, so I can't verify your BIOS version. A BIOS update might be beneficial. Your board includes a Flash BIOS button, which should allow recovery from a corrupted BIOS during an update.
I value the thorough explanation you provided. Memtest completed its four cycles after several hours and showed no errors, indicating a clean pass overall. Given the BSOD is tied to storage concerns, I’m unsure if NVMe is the root cause. CrystalDisk reports no hardware faults and stable temperatures in HWinfo. For the CPU, early tests showed stability at -0.100mV in XTU, but BIOS adjustments caused post-start failures and required CMOS resetting. Keeping the value steady in XTU resolved the issue. The CPU temperature hovers around 28-29°C during idle, but spikes to 40-50°C quickly with high Vcore (~1.326V), prompting a need for better control. On the GPU side, Afterburner allows simple undervolting to 2600MHz @0.925mV, with PL at 108% and a 88°C temperature cap. It seems XMP isn’t being used, as disabling it would increase base clock unnecessarily. Your BIOS version is A3 (updated 4 times since June 1, 2023), which should be compatible with current settings. I’ll rest for a while and try to reproduce the problem tomorrow, keeping an eye on any patterns. If you have further tips, I’d appreciate your help when I’m back. Thank you!
Restart Windows and check if the crash persists. I haven’t updated yet, as I’m worried it might cause issues. I used Windows 10 version 2004 before and never had any problems.
This might be the final fix for me since everything went wrong after a Windows update on January 12th. The issue popped up again—while playing BG3, I closed the game after about an hour and the memory management BSOD appeared right away. I’m confused about why this is happening now. I reached out to Amazon, and they said they’ll send replacement RAM on Tuesday so I can check if it’s the RAM problem or something else. I’m really hoping it’s just RAM since I don’t have other options right now.
Issue is I have 4 NVMe's and 2 HDDs and I can't exactly test the one holding my OS.. what a headache. The way I see it there's still Windows reset without data deletion, Windows full reset wiping everything clean and waiting for the new RAM kit arriving in 2 days. If it is drive related, I could maybe try disconnecting my HDDs.. Also I didn't think about mentioning this but one of my NVMe drives has a Windows installation on it because it was the one I took back from my laptop, could this be causing issues since my main NVMe has Windows too ? EDIT : Btw, I know how to reproduce that BSOD now, it always happens when I close Baldur's Gate 3, as soon as I click on quit game and I go back to the desktop, the mouse freezes and the MEMORY_MANAGEMENT BSOD happens instantly. Running on a single stick of RAM now to see which one might be causing that.. or if it's RAM at all..
It would be the process running with the page file if storage is involved, though the page file isn't always on the OS drive. You might also relocate it, which could trigger additional crashes or freezes if the affected drive is compromised. Use Disk Management to identify the partition containing the page file, scanning below each partition's size for "Page file." Inspect all partitions since it can span multiple drives. If found on several, consolidate them into one. Avoid external drives for this purpose; opt for NVMes instead. Restart your system after adjusting the page file settings.
RE: EDIT: That's interesting. This seems like an atypical RAM symptom, though it could indicate a large amount of memory being examined. It might resemble RAM if the issue lies elsewhere. I hadn't mentioned this before, but it's possible the memory controller inside the CPU appears as RAM.