Getting into Safe Mode or Advanced Startup Options When Windows 11 Won’t Boot
Here’s where I hit a snag — my Windows 11 PC kept crashing to a blue screen during boot-up. The first challenge was getting into Safe Mode or those advanced recovery options, which isn’t always straightforward when Windows refuses to load. Usually, you need to force a shutdown: hold the power button until it switches off, then repeat that about three times. This quick power cut prompts Windows to recognise something’s wrong and eventually boot into Automatic Repair mode. You might see a message like “Preparing Automatic Repair”—which can become a bit of a loop if it keeps spinning. If that doesn’t do the trick, you can also try booting from a recovery drive or a Windows installation USB to access recovery options manually.
Another handy trick: hold Shift and click Restart from the login screen or the power menu. This often brings up recovery options faster. In older BIOS systems, F8 would trigger legacy recovery, but on Windows 11, it’s hit or miss — sometimes it just loads Windows normally or shows a blank screen. If nothing works, creating a bootable USB using the Windows Media Creation Tool and booting from that can be a lifesaver. Remember to tweak your BIOS—temporarily disable Secure Boot, and if your motherboard supports it, switch on Legacy Boot mode. To access these settings, you typically press Del or F2 during startup.
Once in recovery mode, go to Troubleshoot > Advanced Options. Here, you’ll find tools like Command Prompt, Startup Repair, System Restore, and Bootrec. To use Command Prompt, just select it — running commands such as chkdsk /r C: or sfc /scannow can help identify disk errors or corrupted system files. Also, check your UEFI firmware settings — disabling Fast Boot or Secure Boot might resolve issues with recovery media not loading correctly. If your recovery environment isn’t recognising your hardware properly, adjusting BIOS settings can help — but don’t forget to reset those later once you’re done troubleshooting.
Unplug All Peripherals — They Might Be the Culprit
If Windows refuses to boot, try disconnecting all unnecessary peripherals—external drives, printers, USB sticks, and even wireless mouse and keyboard if possible. Peripherals can sometimes cause conflicts during startup, especially if their drivers crash or hang the system. Keep only your keyboard and monitor plugged in. Reboot and see if Windows will load into Safe Mode or at least show some signs of life. Once you’re in, reconnect devices one at a time. Often, a faulty or incompatible driver triggers the issue. Updating drivers via Device Manager (Win + X > Device Manager) can help if a specific device is the problem.
Updating Drivers for Your Peripherals
If unplugging peripherals fixed the initial boot problem but reconnecting them causes crashes again, it’s likely a driver issue. Drivers for mice, keyboards, external drives — all of these can cause BSODs if they’re outdated, corrupted, or incompatible. Boot into Safe Mode (if you aren’t already there), open Device Manager, find your device, right-click, and choose “Update driver”. If Windows can’t update automatically, visit the manufacturer’s website to download the latest or a more stable driver version. Sometimes, older or beta drivers work better — just watch out for unsigned drivers, as Windows might block them for security reasons.
In my experience, updating drivers fixes a lot of blue screens — especially for storage controllers and graphics cards — so it’s a good step when troubleshooting startup crashes.
Rolling Back Recent Windows Updates — Sometimes They Break Things
Another common cause of blue screens shortly after an update. If the issue appeared after a recent Windows update, rolling it back often helps. Head into recovery options, go to Troubleshoot > Advanced Options > Uninstall Updates. Try removing the latest quality update or feature update, whatever was installed most recently. That can often restore stability. To find out which update might be causing trouble, check the list in Control Panel under Programs & Features > View Installed Updates. Sometimes, driver or security patches interfere — especially with AMD or Intel chipset drivers or graphics drivers.
Using Safe Mode to Roll Back Your Graphics Drivers
If your screen flickers, blacks out, or you get a BSOD during driver updates, rolling back your graphics driver is a good move. Boot into Safe Mode (or use recovery options), then open Device Manager (Win + X > Device Manager), locate your display adapter, right-click, and select “Properties”. Under the Driver tab, click “Roll Back Driver”. If that option is available, it’ll revert to the previous driver version immediately. If it’s greyed out, you might need to uninstall the driver completely and let Windows reinstall a basic one on reboot. Checking the GPU manufacturer’s website for stable or legacy drivers can help prevent future issues.
Fixing Boot Configuration Using BCD Commands
If your blue screen shows errors like 0xc0000185 or your system reports missing boot files, the Boot Configuration Data (BCD) might be corrupted. Boot into recovery, open Command Prompt, and run commands like bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd. You might also need to run bcdboot C:\Windows /l en-au /s S: /f UEFI to restore boot files (adjust drive letters as needed). Be cautious — double-check your drive letters with diskpart beforehand to avoid messing things up further. This is more advanced, so if you’re unsure, it’s worth verifying your disk info or seeking help.
Using a Bootable USB to Troubleshoot Deep Problems
If all else fails, creating a bootable Windows USB using the Media Creation Tool is a solid move. Booting from this USB bypasses the broken OS altogether. When Windows won’t start normally, plug in the USB, access your BIOS (F12, F11, or Esc), select the USB from the boot menu, and choose Repair your computer. From there, you can run Startup Repair, open Command Prompt, or restore your system. This method is especially handy if Windows won’t boot into Safe Mode or recovery modes via usual methods.
Repairing System Files and Running System File Checker
Troubleshoot > Advanced Options > Command Prompt. Then run sfc /scannow. This checks protected system files and repairs any issues it finds. Often, it fixes problems caused by buggy updates or corrupted DLLs. If it reports fixing files, great — if not, try running DISM /Online /Cleanup-Image /RestoreHealth first, then rerun SFC. These tools are a good starting point, though they don’t fix everything.
Startup Repair — Let Windows Attempt to Fix Its Own Boot Issues
If Windows refuses to start, Startup Repair can diagnose and fix common boot problems automatically. You can trigger it via recovery media or if Windows detects a startup failure and suggests repair. It scans for missing or damaged boot files and attempts to fix them without manual intervention. It’s a good first step before trying more complex fixes.
System Restore — Roll Back to a Earlier, Stable Point
If you’ve set up restore points previously, System Restore can revert your system to a known-good state. Access it through recovery, then navigate to Troubleshoot > Advanced Options > System Restore. Pick a restore point made before the issues started. This can undo problematic drivers, updates, or corrupted files without doing a full reinstall. Just make sure you have recent restore points, as older ones may not be helpful.
Reinstall Windows — When All Else Fails
If other troubleshooting steps don’t resolve the issue, a clean install might be necessary. Use a bootable USB created with the Media Creation Tool, boot from it, and follow the prompts. Keep in mind, this will wipe your current system — back up your data first if possible. It’s a last resort but can fix severe OS problems or compatibility issues. Be prepared to reinstall your programs and reconfigure your settings afterward.
Hardware Troubleshooting — Don’t Overlook the Physical Stuff
Not all blue screens are software-related — failing hardware can also be the culprit. If you see errors like “Memory Management” or SMART errors on your disks, hardware issues might be to blame. Testing RAM with MemTest86 (created on another PC) can reveal faulty sticks. Tools like CrystalDiskInfo or your SSD manufacturer’s diagnostics (Samsung Magician, WD Data Lifeguard) can check drive health. If tests show problems, try reseating or replacing the hardware. Often, hardware faults are the root cause of boot loops or persistent BSODs that won’t resolve through software fixes. Keep hardware health in mind as part of your troubleshooting.
From my experience, hardware faults often cause stubborn blue screens or boot problems that software repairs can’t fix. So, run hardware diagnostics early if software steps don’t do the trick.
TL;DR & Final Tips
Start by disconnecting peripherals, then try forcing Windows into Safe Mode or recovery options—using forced shutdowns or bootable media if needed. Check for driver conflicts, especially for graphics and storage — rollback drivers if necessary. Run system file repairs with sfc and DISM. Remove recent updates if they caused problems, and consider system restore or a clean reinstall if nothing else works. Don’t forget to test your hardware if the issue persists — often, this is the real culprit. Stay calm, back up your data, and take it step by step. Most issues are fixable, even if they look daunting at first.