Brother's computer stuck at BIOS screen, can't enter BIOS.

Doc Shaftoe

Space Marshal
Nov 29, 2014
304
800
2,360
RSI Handle
DocShaftoe
Hey all, my brother's computer took a shit tonight. He'd turned it off after browsing Reddit for a few hours, then when he turned it back on it was stuck on the BIOS screen and he was unable to enter the BIOS menu. So far we've tried disconnected his SSDs, resetting the CMOS, and running different RAM configurations. From what I've been able to find one the internet, it sounds like it might be a problem with his boot drive, when we don't have that connected his computer looks for one.

He's got an Asus ROG Rampage IV motherboard that's giving off a 0d q-code. I'm at the limits of my technical know-how on this one. Do you guys have any thoughts on solutions?
 

Mich Angel

Space Marshal
Donor
Sep 19, 2016
3,625
13,726
2,910
RSI Handle
ARCHANGEL_666
Try this make shore all power is off as in no external power source connected to computer then remove all as you did bootable devices then locate the motherboard battery and remove it and let it be out for at least 30 min so all electric current left the capacitors.
( this is so you empty any BIOS memory settings on some MB this don't work but could be worth a try )
This usually set back the BIOS to default startup so you need to configure it again if any changes was made.
If that don't help I'm out of ideas for now.. ;)
 
Last edited:

Bruttle

Space Marshal
Donor
Aug 20, 2016
655
2,498
2,600
RSI Handle
Bruttle
Yep, Mitch has it right. Give that a go and see what happens. If that doesn't work, I would then strip down the mobo and start running proven parts. I'd deconstruct the computer onto my bench, hook up a single stick of proven ram, a proven psu, cpu, and run it just like that. If you can access the bios, you can always load linux on a usb drive and run some tests there.

Honestly though, it sounds like your motherboard is borked. I've had a CPU fry, memory go bad, HDD catastrophically corrupt, PSU die, etc., but they all have different symptoms. All those either prevent the pc from starting up entirely, or present themselves after the bios has been loaded. Be careful about changing out the motherboard though. If I remember correctly, windows registers you based on the motherboard ID. So if you swap it out, windows might make you jump through some registration hoops.

I keep an updated version of Linux mounted on a usb drive for just such occasions. If you can get on the bios and set it to load from the USB first, you can run the entire thing off your usb. Then you can test out different components from a separate, proven drive.... among other things...
 

Doc Shaftoe

Space Marshal
Nov 29, 2014
304
800
2,360
RSI Handle
DocShaftoe
We're still not sure what the exact problem is, but we were able to save his system by installing Windows to his second SSD and completely disconnecting the first one. Everything is working for now. Fingers crossed it stays that way. Thanks for the suggestions TESTies, we both appreciate it!
 

WaterShield

Space Marshal
Oct 16, 2015
78
261
2,300
RSI Handle
WaterShield
If you do have to switch out the motherboard and had your Windows key tied to your Microsoft account then it actually isn't a big deal. I've rebuilt my machine 2 times since moving to Windows 10 and I'm still using the same key.

Also if the machine truly only shows the BIOS splash screen and fails to enter the BIOS menu then you are likely looking at an issue with (in order of likelihood) the motherboard, RAM, or CPU.
 

Mich Angel

Space Marshal
Donor
Sep 19, 2016
3,625
13,726
2,910
RSI Handle
ARCHANGEL_666
If you do have to switch out the motherboard and had your Windows key tied to your Microsoft account then it actually isn't a big deal. I've rebuilt my machine 2 times since moving to Windows 10 and I'm still using the same key.
Same here my win 10 install counting the one PC it's on now, have been on 4 different machine same key no change just moved SSD to new PC started up and do all new hardware updates then it was ready to go...

:beers: :beer:
 

Talonsbane

Space Marshal
Donor
Jul 29, 2017
5,308
18,361
3,025
RSI Handle
Talonsbane
He's got an Asus ROG Rampage IV motherboard that's giving off a 0d q-code. I'm at the limits of my technical know-how on this one. Do you guys have any thoughts on solutions?
Given that it happened after reading various things on Reddit, perhaps the 0d code means that it has 0 tolerance for dickheads currently & is taking a break from potential Reddit use until it decides it is ready.

Try this make shore all power is off as in no external power source connected to computer then remove all as you did bootable devices then locate the motherboard battery and remove it and let it be out for at least 30 min so all electric current left the capacitors.
( this is so you empty any BIOS memory settings on some MB this don't work but could be worth a try )
This usually set back the BIOS to default startup so you need to configure it again if any changes was made.
If that don't help I'm out of ideas for now.. ;)
This would be my suggestion as well. Great call @Mich Angel

Have you tried kicking it really hard and insulting its mother?
If he has @Han Burgundy , then perhaps he should try again while enjoying another sort of libation? Bottoms up after all.

Did you look in the manual to see what that code means?
Another great idea @Deroth !

There's not a problem in the world that can't be solved through the proper application of high explosives.
Except erectile dysfunction when said explosives are directly applied to the area failing to work properly.

All legitimate rules have an exception, I would say this is the case in this regard.

I don't know about you Blind Owl, but I dabble in PRECISION!
Precision does help cut down on the amount of collateral damage, but it isn't always as much fun @Wolfy . Well, not unless you're using det cord for the collars of space kitties. (that also have remote triggers) Then it's a thing of beauty in its own right.
 

Blind Owl

Hallucinogenic Owl
Donor
Nov 27, 2015
20,862
73,607
3,160
RSI Handle
BlindOwl
I don't know about you Blind Owl, but I dabble in PRECISION!
Ok then:
Theres not a problem in the world that can't be solved through the PRECISE application of high explosives.
Except erectile dysfunction when said explosives are directly applied to the area failing to work properly.

All legitimate rules have an exception, I would say this is the case in this regard.
I dunno, wrapping det cord sounds kinda exciting an kinky. No one said the high explosives had to be detonated . . .
Precision does help cut down on the amount of collateral damage, but it isn't always as much fun @Wolfy . Well, not unless you're using det cord for the collars of space kitties. (that also have remote triggers) Then it's a thing of beauty in its own right.
Det cord collars. Hehehehehe. "Pop goes the weasel!"
 
Forgot your password?