Encountered a BSOD or system crash during startup.
Encountered a BSOD or system crash during startup.
Hey there. After several attempts and trying to eliminate possibilities, I’m still facing some challenges and would appreciate suggestions on what else you might consider. OS – Windows 11 (also crashes when booting flash drives from Windows installation media or Macrium) x86 (32-bit) or x64 - 64 bit What OS was originally installed? Nothing, Windows 11 just installed fresh Is the OS an OEM version (installed before purchase) or a full retail version (bought from a store) - Was it purchased by me Age of system hardware - All parts are new except RAM, which I bought on January 10th, 2019 Age of OS installation - Have you reinstalled the operating system? Brand new CPU model - Ryzen 5600G Video card - Integrated graphics Motherboard - (if not a laptop) - Gigabyte B550I AORUS PRO AX Mini ITX AM4 Motherboard Power Supply - brand & wattage (skip if it's a laptop) - EVGA SuperNOVA 650 GM 650 W 80+ Gold System Manufacturer - Myself Exact model number (if OEM or laptop) - N/A Laptop or Desktop Problem: I experience either an immediate BSOD or shortly after trying to boot media. I’ve tested a brand new SSD with fresh Windows 11, a flash drive with installation media, and another with Macrium Reflect. All of them have the same issue. I’ve received several BSODs, each detailed below. First incident: Installed some Windows updates, rebooted post-install, but couldn’t boot again. It seems this might be random, especially since crashes occur when booting from flash drives. BSODs seen: CRITICAL_PROCESS_DIED (only a couple times, Macrium managed to crash later or during shutdown). ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY KMODE_EXCEPTION_NOT_HANDLED PAGE_FAULT_IN_NONPAGED_AREA What I’ve tried: Removed all hardware except what’s essential, including the SSD, just to test flash drives (removing SSD ruled out faulty driver). Switched power supply from my old system that’s been working fine for 5 years. Updated motherboard. Changed RAM to one from my previous setup, same problems. Started with a new set of RAM, tested in different slots. Updated UEFI BIOS I believe covers most of what I’ve tried. Currently running memtest again, planning a 24+ hour test. I’m not very optimistic since the old system hasn’t crashed in years, but it’s possible. I’m left with replacing the CPU as a last resort. Any other ideas you have would be greatly appreciated.
It seems like the system is functioning properly overall. You haven’t reported any issues with the parts or storage. Have you attempted to start from the Windows recovery tool and used Startup Repair? That could be a viable path. Another approach might be to perform a clean install of Windows 11 without using Macrium, to check if that resolves the problem. Can you still access the BIOS to choose boot devices? If not, it may indicate a bricked device, though the error messages don’t confirm that.
I've attempted to start the Windows installation from a flash drive, but it triggers an immediate BSOD. The OS installation media was removed from the system, so I'm not affected. I can access the BIOS and memtest is functioning properly. I also tried a Linux USB drive to test something other than Windows, but that one crashes during boot as well.
Consider trying a CPU swap to see if it resolves the BSOD. Check whether an error code appears after the change.
Checked the attempted execution of a non-execute memory issue in the Microsoft Community. It might not resolve the problem, but searching relevant error codes could provide more insight.
I placed the order and it should arrive tomorrow morning for testing. It's challenging to pinpoint the most frequent type, but likely between ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY and KMODE_EXCEPTION_NOT_HANDLED. It doesn't display an actual error code, just a worded stop message. Example:
I'm also checking, but I don't expect much because the memory isn't the main issue—I've used two different configurations over the years in older systems without any crashes during heavy use. Of course, it's still possible and I'll keep running memtest until tomorrow morning to check for errors. I'll update once the new CPU arrives to see if that fixes the problem.