Boot issues on the boots lasting for weeks, even after major hardware upgrades. Successfully restored after reinstall.
Boot issues on the boots lasting for weeks, even after major hardware upgrades. Successfully restored after reinstall.
Hey there, I’m back with another update on an ongoing problem that’s kept evolving through multiple hardware updates and a full system reset. The situation just becomes more puzzling the longer it continues. So far, everything I’ve tried doesn’t align with what my debugging tools suggest should work. If you keep going through, you’ll grasp what I’m saying. Looking at the DM logs, it seems this issue might be tied to Windows 11, even after a complete system wipe.
In short, my machine frequently crashes during startup. It won’t happen if I simply power off and turn it back on—it suggests it happened after a period of inactivity. I’ve adjusted settings like DOCP, resized the bar, and tweaked BIOS options, but nothing seems to prevent the blue screen. The code changes often, sometimes showing different messages over several attempts.
Looking back at the changes, I realized some key updates:
- New motherboard with a different chipset.
- ProArt B550 (offered Thunderbolt ports and PCIe Gen 4 support).
- I had to reinstall Windows because of the blue-screen during boot.
- All drive health checks show no problems, yet the issue persists.
Hardware-wise, the motherboard is new, and RAM switched from generic sticks to Corsair Vengeance RGB Pro units. The upgrade to Windows 11 coincided with this problem starting. I haven’t altered any BIOS settings recently, and my RAM now matches exactly what I had before.
Interestingly, I managed to get past the first four common codes—MEMORY_MANAGEMENT PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, and DRIVER_OVERRAN_STACK_BUFFER. BAD_POOL_CALLER. But these still appear in varying patterns each time.
I also tried turning on DOCP, which might have improved RAM performance, but the blue screen still occurred. The RAM size increased from 48GB to 64GB, and I suspect that could be relevant. Also, my CPU is damaged, but that doesn’t explain the boot issues.
Other than that, everything in my original specs still holds up. Still, I’m stuck trying to figure out what’s causing this. The “memory” problem is tricky—many parts of a computer use memory, and a failure there doesn’t always point to the exact component.
If anyone has insights or suggestions, I’d really appreciate it.
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the entire Minidump folder to your Downloads folder (use the desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to the instructions since Windows doesn't allow file manipulation there.
Timing well, since I recently experienced a tough boot sequence. I reached my desktop a couple of times before hitting blue screen. I've saved some footage to help you understand the problem. Attached are all the files from my minidump folder. minidump.zip
Many issues stem from memory mistakes, with one case showing signs of corruption while reading the hibernation file. About half of these errors involve the page file rather than actual RAM. Memory and storage often appear similar due to the page file's role. The appearance depends on where the corruption is found. Since you've swapped in new RAM and are running at standard speeds, I suspect the problem lies with storage. The hibernation file corruption isn't as obvious as it seems because it transfers RAM to the file and restores it upon startup. If you're using multiple drives, ensure both the page file and hibernation file reside on the same drive—this would point to the main issue. By default, the page file is set to C:, though its location can shift. In PowerShell, use Get-WmiObject to check usage; if both are on C:, storage is likely involved. If they're not, you may have faulty hardware or the memory controller could be the culprit.
Hey bjoolz, seems like these drives aren't connected together. The PowerShell output showed: Name ---- D:\pagefile.sys My local SSD is a budget model with roughly 450GB and hasn’t changed after reinstalling Windows. I’ve also included the minidump folder from today’s blue screen events. I’ve observed that every time I reach the desktop and see a blue screen, the MEMORY_MANAGEMENT code appears consistently. It’s also important to mention that the blue screen when I get to the desktop doesn’t seem linked to quicker boot times. Sure, the boot is faster now, but it still takes a long time after powering up before the screen flashes. Is this indicating faulty RAM or a defective CPU? I’m pretty sure it’s the RAM, since the 5950X isn’t covered under warranty anymore and would cost a lot to replace. I was really hoping I could keep using this CPU until I needed a newer one with a better socket. The minidump file is attached.
Adjusted the page file location to C: and checked if the crashes persisted. Reviewed the two files from the 19th; one appears corrupted as a hibernation file, another shows memory errors pointing to the page file. Ensure sufficient space remains on C:. The page file may need an additional 20GB, but avoid filling SSDs fully to prevent excessive writes and shorten lifespan. Aim for about 20% free space. Also, disable Fast Startup—Windows handles it well with modern SSDs, though it can still cause problems occasionally. Navigate to Power Plan settings in Windows, select "Choose what the power buttons do" on the left, and uncheck "Turn on fast startup." If grayed, proceed to the admin settings shield at the top for further adjustments.
I completed everything I needed to do. My C drive is typically 10-30 gigabytes away from being full, so I’ll attempt to free up some space. Interestingly, my page file has already moved into my C drive after I cleared out a lot of space. Does it shift each time you restart? I’ll update you on the results. Thanks for the assistance!
Uncertain. It could work better with C, likely due to limited space.
I'm experiencing some uncertainty about one of your drives since the page file and hibernation files were on separate drives and both had problems. It seems there might be a transfer happening where the page file could move to the hibernation file, which triggered a corruption alert. Be aware of the drive connections if more issues arise. You can share screenshots from CrystalDiskInfo for each drive (make sure to open the full window) showing the details below the general info. The numbers listed are technical specs—just keep in mind that the manufacturer decides when a drive fails. The percentage value refers to how much of the promised write capacity has been used, not actual health. Modern SSDs lack self-diagnostics and don't store useful data about problems.