• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Strange boot issue.

Joined
Jan 8, 2017
Messages
9,813 (3.22/day)
System Name Good enough
Processor AMD Ryzen R9 7900 - Alphacool Eisblock XPX Aurora Edge
Motherboard ASRock B650 Pro RS
Cooling 2x 360mm NexXxoS ST30 X-Flow, 1x 360mm NexXxoS ST30, 1x 240mm NexXxoS ST30
Memory 32GB - FURY Beast RGB 5600 Mhz
Video Card(s) Sapphire RX 7900 XT - Alphacool Eisblock Aurora
Storage 1x Kingston KC3000 1TB 1x Kingston A2000 1TB, 1x Samsung 850 EVO 250GB , 1x Samsung 860 EVO 500GB
Display(s) LG UltraGear 32GN650-B + 4K Samsung TV
Case Phanteks NV7
Power Supply GPS-750C
Alright, this is a strange one.

At every cold boot once it gets to the Asrock logo screen it just hangs there forever, can't even access the BIOS. Now if I reboot a second time everything starts up just fine, goes past the Asrock logo and all that, Windows boots up no problem. This started happening ever since I reinstalled Windows a couple of days ago and had to mess with boot priority. My first thought was that I messed something up with regards to that and the first time the PC boots up it's looking for a particular boot device and it doesn't find it, even though everything seems fine inside the BIOS. But the thing is, even after resetting the BIOS to the defaults that still happens, moreover I actually saved my BIOS settings before I began reinstalling Windows and even with those settings the issue is still there.

Another unusual thing that I have noticed (and I have a hunch this has something to do with my problem) is that instead of having my drive listed as the first boot device as it was before (850 EVO) it now says : "Windows boot manager (850 EVO)".

What are your thoughts ?
 
remove any boot options other than the OS , make sure it isnt cycling thru boot possibilities.
maybe try disabling or enabling "full screen logo option" in bios?
tinker with fast boot, or faster boot options as well.
 
So it turns out that fast boot was indeed the problem. Totally forgot about that, I would always turn it off and now I remember why.

Can't understand why after so much time this features is still completely broken.
 
The OPs problem sounded the similar problem i was getting after upgrading windows 10 then going back to windows 10 1803 (fresh install)

now last time i tried to install windows 10 1803 it kept saying unsupported CPU ?

Im sure it's something to with SecureBoot and TPM 1.2 chip

in the end I just thought "you what, sod windows 10, hello Linux"

i've given up windows, it was a bad habit anyway.
 
Back
Top