Question Windows not booting up in normal mode

Razzzor

Reputable
Aug 15, 2019
47
5
4,535
After pressing power button, motherboard logo appears and then the loading wheel appears for a second after that screen goes full blank mode.
But when I load in safe mode (pressing F8), it works fine.
Any idea what's causing it? and solution.

Running Windows 10 and also tried reinstalling it but it didn't fix.

opening in safe mode and then using these commands like "sfc /scannow, dism /online /cleanup-image /scanhealth, dism /online /cleanup-image /restorehealth" etc. does help in booting normally only for the next time but again the next day it's back to square one

Thanks.

Video Clip
 
If it is running fine in Safe Mode that's typically an indication that something 3rd party is causing it to mis-behave.

1) What changes have you made recently? Any new software or hardware added? Any updates to anything?
2) When did it initially start doing this? Has it ever done it previously?
 
If it is running fine in Safe Mode that's typically an indication that something 3rd party is causing it to mis-behave.

1) What changes have you made recently? Any new software or hardware added? Any updates to anything?
2) When did it initially start doing this? Has it ever done it previously?
I reinstalled the OS again with minimal software installed.
About hardware, recently I changed mobo, psu, rams, nvme
 
@Razzzor

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, used, refurbished)?

Disk drive(s): make, model, capacity, how full?
  1. CPU: Ryzen 5 3600
  2. GPU: MSI RX 6500 XT MECH 2X 4GB OC
  3. RAM: Corsair Vengeance 3000MHz 2x8GB DDR4
  4. MoBo: ASRock B550M-HDV
  5. NVMe: WD Blue NVMe SN570 500GB
  6. PSU: Cooler Master MWE Gold 750 Full Modular
CPU and GPU are six months old.
the rest are newly upgraded (not even a month old).
and the disk isn't full at all, only the OS is installed.
 
With the system being able to boot into safe mode it is possible that Reliabiity History/Monitor and/or Event Viewer may be capturing some error codes, warnings, or even informational events regarding the full boot failures.

Look for entries/events just before or at the time of known full boot failures.

Per @hedwar2011 's post start by verifying that all 3rd party drivers are correct and up to date. Verify by visiting the applicable manufacturer's website and manually downloading drivers. Reinstall and reconfigure. No third party tools or installers.

Also be sure that the website is indeed the manufacturer's real website. Just because the name of the manufacturer appears in the URL that does not mean that the site is tlhe true manufacturer.

Check Update History for any failed or problem updates.

Run "dism" and "sfc /scannow" to find and fix corrupted files.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161
 
After pressing power button, motherboard logo appears and then the loading wheel appears for a second after that screen goes full blank mode.
That is not blank mode (misleading).
It says - no signal.
If you have multiple screens connected, then desktop is being displayed on the other screen.

If you have only single screen connected, then
connect to your pc via remote desktop and install graphics card driver.
 
If that still doesn't help do the following:
1) Go back into Safe Mode.
2) Go into msconfig again, this time go to the Startup tab.
3) On this page, uncheck anything that you don't recognize or you can even uncheck everything for the time being. Some stuff will automatically recheck itself (this is ok).
4) Go to the Services tab, check the box titled "Hide all Microsoft Services", uncheck everything else.
5) Click Apply and restart.

NOTE: The computer may look weird and load different than before but that is because we are disabling EVERYTHING non-essential that could possibly be causing the issues you're experiencing. If you are still having the issue after doing this, you will need to re-install your OS after backing up but do so with nothing plugged up or installed except keyboard, mouse, monitor, and power and then test once again.
 
If that still doesn't help do the following:
1) Go back into Safe Mode.
2) Go into msconfig again, this time go to the Startup tab.
3) On this page, uncheck anything that you don't recognize or you can even uncheck everything for the time being. Some stuff will automatically recheck itself (this is ok).
4) Go to the Services tab, check the box titled "Hide all Microsoft Services", uncheck everything else.
5) Click Apply and restart.

NOTE: The computer may look weird and load different than before but that is because we are disabling EVERYTHING non-essential that could possibly be causing the issues you're experiencing. If you are still having the issue after doing this, you will need to re-install your OS after backing up but do so with nothing plugged up or installed except keyboard, mouse, monitor, and power and then test once again.
Just now installed fresh Windows and didn't do anything after installation, still the same thing keeps happening.

And also I was trying install Linux (Endeavor OS), after verbose it again went to blank mode.
 
Let me make sure I understand correctly:
1) You reinstalled Windows w/o adding anything else afterwards and it reverted back to showing the BIOS splash and then goes right to the spinning wheel?
1.1) Did you completely format the drive and remove the partitions or simply copy it over the same partition? If you didn't remove the partitions, etc. that is what is considered a "dirty" install and can simply amplify the problems you're experiencing.
2) So are you trying to dual boot with Linux or you tried to install Linux after installing Windows?
 
Let me make sure I understand correctly:
1) You reinstalled Windows w/o adding anything else afterwards and it reverted back to showing the BIOS splash and then goes right to the spinning wheel?
1.1) Did you completely format the drive and remove the partitions or simply copy it over the same partition? If you didn't remove the partitions, etc. that is what is considered a "dirty" install and can simply amplify the problems you're experiencing.
2) So are you trying to dual boot with Linux or you tried to install Linux after installing Windows?
1. yes
1.1. yes deleted the partitions too.
2. No. Couldn't install linux as the screen went blank (like how it goes) when I tried to load linux installation files from USB.
 
not right now with the fresh install that I did recently.
But earlier installation had graphics card drivers installed.
Make sure you install graphics driver.
And turn off automatic driver updates, so windows doesn't force installation of incompatible drivers.

 
Interesting that it let you get completely through the installation and then started acting up.
1) How are you doing the reinstall? Via USB? Have you tried re-creating the USB?
yes via USB.
I use Ventoy, so no need to flash every time. just have win 10, 11 and endeavor OS in it.
 
You might be dealing with a corrupt file somewhere in those.

Not questioning your ability but I recommend following the link below and trying a fresh install that way and seeing if the same thing occurs.
 
You might be dealing with a corrupt file somewhere in those.

Not questioning your ability but I recommend following the link below and trying a fresh install that way and seeing if the same thing occurs.
I did this.
but issue still persists.

One thing I noticed is that the wheel appears for a bit longer (like 2-3 seconds from the earlier 1 second) and I kept my HDD unplugged while booting up.
 
For kicks and giggles (considering everything else that has been tried), go HERE and download the graphics driver listed at the very top. Yes, I know it's an older driver but I want to see if it does the same thing with the previous driver as it's doing with the current one.

It should be AMD Software: Adrenalin Edition v23.10.2
 
This issue has been resolved by getting a new CPU.
It seems the CPU became faulty.

WARNING: Just before this started, I was running WINDOWS 11 DEV CHANNEL, which oneday crashed and corrupted CPU, motherboard & SSD.