Question Can't boot to BIOS ?

[wallajalla]

Hi! I've encountered a very confusing issue with my PC recently and it's proving difficult to solve, here's the situation:

Yesterday, I tried restoring bluetooth to AtlasOS via a built in script, and upon restarting I noticed something strange. I couldn't boot windows without restarting a few times. Everytime I tried to boot, power flowed but I was stuck on a black screen.

After a bit of tinkering, I managed to get Windows to boot normally everytime, but I was permanently locked out of my bios menus. There was no boot screen with my bios displaying before windows starts, only a black screen, and pressing DEL on startup only left me stuck at said black screen.

For reference, my motherboard is an MSI B550 PRO 7D14

After that, I deleted my atlasOS partition and went over to my normal install of windows, which I wanted to reset entirely by doing a factory reset and clean wipe via window's inbuilt "Reset this PC" function. However, what ended up happening was that I'd be left at a black screen on restart, just like the bios. And when attempting to reboot, it simply told me that reinstalation was unsuccessful and nothing had changed.

Promptly, I also tried installing windows with a setup.exe file, which yielded the same result; with the error 0x3001A. I also tried installing it with a USB flash drive, which simply wouldn't boot no matter how I tried to launch it.

So essentially, what I've gathered is that any attempt to boot Windows outside of normal mode leads to an uninteractable black screen. I attempted a CMOS clear, which didn't save me. I also tried to reinstall my bios, but I couldn't boot the USB flash drive, so it yielded no result. I have also attempted to boot without a Windows partition attached, which only led to a black screen.

Does anybody know what's going on?

 

[35below0]

Welcome to the forum.

I don't really have an idea what's going on. But i'd like to ask you a few questions:

- are any status LEDs on the motherboard lighting up when you try to boot?
- are you sure BIOS cannot load, or is the display off? Maybe it's switching from GPU to internal graphics. I've had some experience with a badly behaved BIOS that refused to display anything on GPU or the iGPU. CMOS reset fixed it though.
- does your monitor turn on? does it complain about no signal?

It may help if you post all specs. Also add any other detail you can remember that may be useful.
You say you had to restart a few times after running the script. Were those restarts all the same? Was there something unusual about them? What made Windos boot again?

 

[wallajalla]

Welcome to the forum.

I don't really have an idea what's going on. But i'd like to ask you a few questions:

- are any status LEDs on the motherboard lighting up when you try to boot?
- are you sure BIOS cannot load, or is the display off? Maybe it's switching from GPU to internal graphics. I've had some experience with a badly behaved BIOS that refused to display anything on GPU or the iGPU. CMOS reset fixed it though.
- does your monitor turn on? does it complain about no signal?

It may help if you post all specs. Also add any other detail you can remember that may be useful.
You say you had to restart a few times after running the script. Were those restarts all the same? Was there something unusual about them? What made Windos boot again?

A few answers to your questions:
- LEDs labelled CPU, VGA and BOOT light up one after another when launching windows. the DRAM LED flickers before VGA lights up. The same thing happens when trying to load bios, except the DRAM doesn't flicker.
- I'm not sure, but it does halt the windows boot when attempting to boot bios, so it is probably atleast reading the input. Which probably means it is loading to some extent.
- CMOS changed nothing on my end.
_ When launching bios, it does complain about no signal.

 

[35below0]

Anyone have any ideas?

I'd like to help but i'm drawing blanks. I don't think i've ever heard of a motherboard with no BIOS.

wallajalla, if you have more drives besides the windows partition, remove them. It may be a drive error.
Hell, it might be a loose cable...
But if you still have the issue without drives at least they're eliminated as the cause.