Computer boot loop / bios

K

koralis

Well-known member
So... I noticed that Rebar was not enabled on my computer in the Nvidia control panel, so went to look at the bios setting. Huh... Auto, not enabled. I changed it to Enabled, and the problems begin.

The next boot, no video. Otherwise seems to be behaving normally. Short press of the power button and the system appears to shut itself down. Push the button again, presumably back into windows, shut down again, etc. So, the setting was not good. But I have no video to change it. Shit. OK, the motherboard has a Clear Cmos button... I will just do that and reconfigure things. Wrong.

Now the system is perpetually rebooting itself every few seconds, which isn't the way it behaved when I first set it up. Still no video.


Ideas? Only thing I can think of now is remove the video card, use the q-flash firmware utility to reflash the bios via the button, then put the video card back in and hope that fixes things.

Guess I should have left well enough alone
 
Last edited:
Further thought, maybe clear cmos undid secure boot, etc, and windows is rebooting? Video card still not working to see it though.

No. Repeat tapping of the del key does not interrupt the loop, which it would if it was a boot configuration thing.

Lights on mb... Cpu, dram, vga... Cpu, dram, vga... Then reboot
 
Last edited:
Q flash saved my bacon. Not sure why the cmos clear didn't, but I noticed the manual says that's a multifunction button.
 
I think I know what happened. I did a search in the bios for rebar and enabled it. Apparently it's supposed to be hidden if these two settings aren't enabled.
  • Above 4G Decoding -> Enabled
  • Above 4GB MMIO BIOS assignment -> Enabled
​Don't know if I have the nerve to try it again. Hah


Update: I tried it... with those other two settings enabled first (I added them one at a time, rebooted, etc), Resizable Bar appeared. When Resizable Bar was enabled in this way, no problems.
 
Last edited:
OMG, the BIOS flash invalidated Windows! I just spent a couple of hours trying to get it relicensed. Do NOT flash your Bios if using a "Digital key." Microsoft has serious issues in transferring licenses, and keeping track of things.​

None of the automated systems worked, and they don't make it easy to even FIND a phone number to talk to people. After googling a phone number to talk to the bot, I eventually convinced it that I needed to talk to a support person. That one took me through all of the steps I'd already done, and eventually transferred me to an actual technical person. That still didn't work, though by the end they offered a solution that I wasn't convinced was going to work either.


They assert that if I reinstall WIndows from scratch that may fix it, but who the hell wants to go through all that? As it happens, after purchasing the Digital Key I was going through my Newegg purchases to itemize the old system and I found my old purchased key for the previous system (if I'd found it before, I wouldn't have needed this one at all.) Ultimately I could only get it relicensed because I recently found my OLD Win10 license product key that they allowed me to use. The "Digital key" is basically a ghost now.

I highly recommend NOT buying things from the MS store. Get a paper trial and/or physical goods.
 
Lots of complaints about weird goings on lately... instability or black/green screens. Here I had to go from Vega 64 to Rx 480 to R290 to get stable. Glad I kept that old shit I even played the ancient HD 6950 and its rock solid but its too slow for almost anything so I run the R290. The older the HW the more stable it was... with vega64 being the worst. Almost think I should dump win 11 and go back to win 10 see if it helps.
 
andino said:
Not to sound like an ass but some computer specs would be nice.
Click to expand...

For me?

Gigabyte Z790 UD AC
i5-13500KF
32 GB DDR5 @ 6000 MHz
Giabyte 4080 OC

Not that I'm blaming the hardware (much)... my issues were:

1) Not enabling the setting correctly, shortcutting a process in a way that the BIOS didn't anticipate (but the BIOS really shouldn't allow that combination to be set in the first place to eliminate user-error)

2) Windows considering the system new hardware after the BIOS flash. Probably has something to do with TPM resetting to a new ID after the BIOS flash... MS problem in making it so damned difficult to reactivate, but Gigabyte could have copied the TPM settings and reapplied them doing the BIOS update instead of setting up a new ID.


Basically, some bad choices on Gigabyte's part caused my issues and they could/should remedy that. Maybe Asus, MSI, etc, already have those holes taken care of.




Regarding PAX's problem, yeah... seems like there are problems that might be addressable with more information.
 
Last edited:
pax said:
Lots of complaints about weird goings on lately... instability or black/green screens. Here I had to go from Vega 64 to Rx 480 to R290 to get stable. Glad I kept that old **** I even played the ancient HD 6950 and its rock solid but its too slow for almost anything so I run the R290. The older the HW the more stable it was... with vega64 being the worst. Almost think I should dump win 11 and go back to win 10 see if it helps.
Click to expand...

FWIW, if I have a working system, I will not go to a new OS until required. So, stick with XP until the bitter end, then Win7, then finally Win10. I won't go to 11 until 10 is discontinued, by which point hopefully the bugs are worked out.
 
Ya to be specific have one rig with win10 and another with win 11... got win 11 to go along with the 5800X3D but the mobo being old maybe I took some chances but the problem started before win 11 tho only got worse after. The win 10 rig with RX480 has a similar problem (as did the win 11 vega rig before on win 10) but it doesnt lock up the rig like the win 11 one. Still trying to narrow it down as the vega was actually still decent at 1440p and we need to wait these insanity pepper gpu prices out.
 
You must log in or register to reply here.
Back
Top