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.
Bad update: occurred once more today. Likely just a coincidence yesterday. I opened powershell immediately after noticing the pagefile shifted back to D, but by then it was in C. I've attached a fresh copy of the minidump folder. Also included are screenshots from crystaldiskinfo. I struggled to run several instances simultaneously or maximize the window, so I relied on the save as image feature to capture images, which I've also attached. These steps worked before, and currently the drives appear normal. Appreciate your ongoing help. minidump 3.zip
The D: drive is beginning to fail, which could account for the reduced crashes after changing the page file. The C: drive seems normal and still has the stable SMART status around 80% reliability. The logs mention a storage driver issue and a memory error in the page file, suggesting similar problems before. I recommend disconnecting D: to determine if it stops causing crashes.
Hey Bjoolz, sorry for the delayed response. I’m willing to give it a shot—it’s a pretty extreme step since there’s data on the D drive that would be inconvenient to lose, but it’s much better than taking out either of the other drives. It’s odd how my D drive is messing up the whole Windows setup. I’ll try disconnecting it now and will update you on what happens.
Disconnect the D: drive and see which drive is used for the page file. Then relocate it. These issues appear across different memory errors when handling virtual memory locations. I’m not a programmer, just trying to troubleshoot for enjoyment. There are two Windows features related to memory: one handles virtual RAM, and another manages a virtual memory pool. On older systems, the system had to manage free space carefully to avoid crashes or data loss. Now Windows automatically creates a virtual pool, letting the memory manager handle addresses correctly. I’m not entirely sure which one applies here.
It isn’t halted just because the D drive is unplugged. I have some fresh minidump files, though I know they might not provide new data right now. I’ve encountered various error messages other than MEMORY_MANAGEMENT. After swapping the motherboard and RAM, I experienced strange issues; previously I received many error codes, but now only MEMORY_MANAGEMENT appears. I keep trying the powershell command, but it always points to the C drive. C still shows more than 100GB free space. I attempted to make a shortcut so the command would run just before a crash, but I couldn’t figure out the method, so I can only execute it when the system doesn’t blue screen. minidump 5.zip
I dislike when several issues appear at once. The D: drive showed errors and originally seemed like the main culprit. The latest dumps reveal Memory_Management problems, stack anomalies indicating virtual RAM issues, and Kernel_Data_Inpage_Error suggesting corruption in the page file. IRQL_Not_Less_Or_Equal points to a page fault unrelated to the page file, hinting at RAM trouble. Memory_Management checks again match previous findings but now seem more about RAM. It appears the D: drive likely isn't the cause, but both RAM and the drive could be faulty. The drive definitely has errors, so I wouldn’t rely on it. If we locate bad RAM, reconnecting it might help. Keep the page file on C:.
First run SFC to verify OS integrity—corrupted files often trigger crashes. Some corruption happens after many failures, leading to BSODs that complicate testing. If SFC fails, proceed with DISM then SFC. To test RAM, consider tools like Memtest; since DDR4 has frequent bad RAM reports, a clean scan isn’t guaranteed. Avoid false positives—this method still holds value.
Prefer normal operation with one stick at a time to identify problematic units. If only one stick causes crashes, it’s a faulty RAM module. Dual failures may indicate CPU memory controller issues. Ensure PBO is turned off in the BIOS overclocking settings. Recent BIOS updates can improve memory compatibility—test them. Your board has flashback capability, allowing recovery from corrupted BIOS during updates.
I’m pulling out the old corsair 16GB drives from the machine and checking if it starts up. It’s frustrating because I’m not sure these parts are still covered under warranty anymore. I’ll update you once I’ve tried it.