BSOD on Asus Z270 after BIOS upgrade (unable to boot)
BSOD on Asus Z270 after BIOS upgrade (unable to boot)
I’m feeling frustrated and a bit scared right now because I’m struggling with the BIOS settings. After updating the Asus BIOS, I encountered an error saying the boot device isn’t accessible. I tried looking up solutions for an SSD setup on Windows, but it seemed to be related to a different motherboard. Since I have a Nonverbal learning disability, I find it hard to explain things clearly or follow detailed instructions. I’ll share some pictures from my BIOS and hope they help you figure out the right settings. Also, when I try boot override, the system crashes instead of fixing the issue. Thanks.
The system is starting from the right partition, but Windows is experiencing issues. Consider turning off your HDD and other peripherals in the BIOS to disable them as boot options.
Check the settings to turn off the additional storage. Since you only have two drives, consider removing the second one to free up space or avoid conflicts.
I managed to reach my desktop briefly after typing in the password (before I even reached the login section without seeing a blue screen). The login interface appears entirely blue, which is unusual. After arriving on the desktop, a few seconds later the system crashes again with this error message.
I encountered a comparable issue on my mother’s Z-270i Mobo. Here are the steps that resolved it. Disabling Driver Signature Enforcement in the settings helped. On the options screen, choose “Troubleshoot,” then “Advanced options.” Click “Startup Settings” and press “Restart” to bring the PC back to startup mode. Enter “7” or “F7” on the Startup Settings screen to enable the feature. Also, I attempted to revert the BIOS, restore from a point, adjust ACHI/RAID settings, remove unnecessary drives, clear CMOS via the PCI-E jumper, run Get-Packages, and reset defaults. Let me know if this assists!
I faced the same problem after trying to upgrade my GPU and updating Windows. When I boot into safe mode and restart, the issue disappears temporarily, but it returns when I try to adjust the overclock settings again. It's acting like a temporary solution until I discover the root cause.
It helped to launch the program in Startup settings, begin it in Safe Mode, and then restart. The reboot brought it back to normal Windows. Previously, disabling driver signature enforcement didn’t resolve the issue.