PC Stuck in booting up after BIOS Splash screen and before win logo.

Hello, I recently upgraded to a Gigabyte B450M DSH3 3 weeks ago and everything was fine the first day but after I turned it off and tried to turn on the next day it got stuck after the Gigabyte logo in something that appeared to be a console window from MS_DOS (kinda like when the pc is trying to find where to boot from I think) and it just froze with the little type symbol and wouldn't do nothing , unless I turned it off and back on again, it would get past that screen and into the windows loading logo, and eventually into windows normally, its been doing this since that day, everytime I leave to work or go to sleep and I try to turn it back on, it will get stuck on that screen I mentioned before, but if I turn it off manually and back on again it will get past the screen, I can leave it off for an hour or so and it will normally boot but if I leave it off for too much like for 8 hours when I go to work or to sleep it will have that problem and I have to turn the pc on twice to boot to windows, the second time ALWAYS works.

Its driving me insane because I dont want to be having to turn off and on my pc again everytime I try to boot it up, I think its not normal and potentially dangerous to my hardware.

Which of the following steps have you done to resolve this? (In order of relevance/difficulty)

1. driver updates
2. startup repair
3. bios update
4. OS reinstall

zebal said:

Which of the following steps have you done to resolve this? (In order of relevance/difficulty)

1. driver updates
2. startup repair
3. bios update
4. OS reinstall

I'm pretty sure im up to date driver wise but I haven't tried any of the other 3, I'd like to try a Startup Repair but I don't know exactly how to, I would like to refrain from updating the BIOS since I've heard thats dangerous if not done properly, my BIOS revision is indeed out of date, its on revision F41 whilst the newest is F50 (2 updates below current update)

B450M DS3H (rev. 1.0) | Motherboard - GIGABYTE Global

I know how to perform a OS install but Id also like to leave that for last.

Well flushing bios requires to carefully follow procedure.

Startup repair is done by making bootable USB and putting Windows 10 installation files on it.

To make bootable USB follow bellow procedure:
https://docs.microsoft.com/en-us/win...sb-flash-drive

the only exception to above procedure is to replace format fs=ntfs quick
with format fs=fat32 quick

to get installation media:
https://www.microsoft.com/en-us/soft...load/windows10

mount iso file, and simply copy contents to USB.
then you would boot from it, and select "Repair my computer" option, and follow procedure.

zebal said:

Well flushing bios requires to carefully follow procedure.

Startup repair is done by making bootable USB and putting Windows 10 installation files on it.

To make bootable USB follow bellow procedure:
https://docs.microsoft.com/en-us/win...sb-flash-drive

the only exception to above procedure is to replace format fs=ntfs quick
with format fs=fat32 quick

to get installation media:
https://www.microsoft.com/en-us/soft...load/windows10

mount iso file, and simply copy contents to USB.
then you would boot from it, and select "Repair my computer" option, and follow procedure.

I will perform Startup Repair next and come back with results when I'm done I guess, HOWEVER, I do have one question...

I was just looking at my mobo BIOS available updates here:

B450M DS3H (rev. 1.0) | Motherboard - GIGABYTE Global

And I noticed this on an available update (My BIOS is on revision F41):

The changelog for update F42h reads:

1. Update AGESA 1.0.0.3 ABBA
2. Improve Destiny 2 gaming compatibility
3. Correction of PCIe Gen4 being disabled when using a 3rd Gen Ryzen (Matisse) CPU due to this AGESA

Note: Before updating BIOS to this new version, you MUST follow the steps as detailed under BIOS F40 discription

Can that be related to my issue? I think I might have something PCIE 4.0 around , my hardware is:

Ryzen 2600
8GB DDR4 Ram
1TB Seagate HDD
120Gb Seagate HDD
and GEFORCE GTX 970


I'd like to know if this update could help with my issue before trying any of the other options below, as it might seen there is a critical issue that has not been fixed in my BIOS version.

Please post full type and model of your processor.

to get type and model for your CPU execute following command in Powershell:
Get-WmiObject win32_processor

then post output of the command here.

Caption : AMD64 Family 23 Model 8 Stepping 2
DeviceID : CPU0
Manufacturer : AuthenticAMD
MaxClockSpeed : 3400
Name : AMD Ryzen 5 2600 Six-Core Processor
SocketDesignation : AM4

Matisse Processors include 3500-3950X processors, your CPU does not belong into that group.

So the fix mentioned in revision F42h point 3 does not affect you.
the rest of the bios fixes are not self explanatory and need more research.

I would recommend doing step 1 and 2, first before experimenting with the rest.

Thanks, I will try to perform a startup repair now and see if it can repair the issue.

- - - Updated - - -

Unfortunately Startup repair did not fix the issue , had to wait a day to see for real and I can confirm it did it twice again after running Repair

Hello, I would like to check error events on your system before doing anything else,
if nothing useful can be seen in these events, and if updating drivers doesn't solve the problem,
I would personally just clean reinstall windows.

because system restore is not supposed to resolve this problem since, as you described, this problem started happening
after an upgrade to new motherboard, which is a hardware change, not software change.
therefore this windows was running just fine on the motherboard where is was initially installed? right?

Btw. restore options are here:
https://support.microsoft.com/en-us/...covery-options

You may want to read about these recovery options in the mean time, the "Restore from a system restore point"
section is what you can try, but i don't believe it will work, for reasons said above.

Can you please run following 2 commands in elevated powershell: (open powershell as administrator)

Get-EventLog -LogName HardwareEvents -EntryType Error -Newest 600 -ErrorAction SilentlyContinue | Select * | Out-File C:\hardware.txt
Get-EventLog -LogName System -EntryType Error -Newest 600 -ErrorAction SilentlyContinue | Select * | Out-File C:\system.txt

This will create 2 text files in C:\ drive root.
zip them up, and attach here.

EDIT:
ah, flushing bios, that's an option too, but... bad things can happen if not done correctly, I leave this option to you.
I just don't like to recommend it unless you are willing to take a risk.