Computer boots on second attempt only

Shapperd

Commendable
Aug 8, 2016
17
0
1,510
Hi!
I have a problem, basically when I first start my pc it won't get past the lock screen. I mean it seems it loading, everything seems good but after it gets to lock screen it does nothing more. I force turn it off then re-on and everything works fine. (Also lights on my mouse stays in "stand-by" stance, which means it thinks it's not connected to anything) It's not an old build, built around 2011-2012, everything worked fine till last week when this thing started happening.
My config:
Asrock B75-pro3
Intel Core i5 3330
Shapphire radeon 7770 GHZ Edition
8GB Corsair vengance 1600MHZ RAM
500GB WD HDD, 120GB Samsung 750 EVO SSD.
PSU: EVGA 500W
Windows 10

This behaviour is weird because it started suddenly, and coudnt be solved with a full clean (formatted) reinstall of windows.

Thank you in anticipation.
 
Solution
More than likely that's a driver error or conflict. What happens in fast boot is when you use Windows to turn off the pc, it caches everything on the ssd/hdd so when you hit the power button, it pulls all the info from the cache. With fast boot turned off, when you start the pc, it initiates all the drivers from scratch, so loads the original drivers right out of Windows etc. With a false start or pushing reset, the pc basically skips the fast boot cache and loads everything from scratch. No way it's a Windows driver that's corrupted, likely culprits are gpu drivers in conflict with YouTube codas or even IE.

So something, somewhere that's working/loaded/used after windows actually starts is corrupting a driver, which fast boot will...
Welcome to the TH Community, @Shapperd!

Since a clean install of Windows didn't help you resolve the issue, I'd strongly recommend you try resetting BIOS as well. This procedure will get the settings back to factory defaults, so you will need to re-configure all the manual changes you have made in BIOS so far.
If it still doesn't resolve the problem, go to the motherboard manufacturer's official website and check for any BIOS version updates. You might need to install the latest one available. Hopefully, that will end the struggle of booting on second attempt only.

Give these a try and let me know how it goes.
SuperSoph_WD
 

Shapperd

Commendable
Aug 8, 2016
17
0
1,510


Thank you for the answer. My UEFI says it's up to date, and resetting it didn't help. I'm not really having more idea about it :/
 


This seems unfortunate! :( I'd suggest you check your power supply unit in particular. If the BIOS update and reseating the connections didn't help, then it could be a sign of a faulty PSU.
If you don't feel tech savvy enough to do this by yourself, I'd suggest you turn to a professional PC repair service nearby. The guys there should be able to assist you with a complete diagnostics of your system.

Give it a try and let me know how it goes.
Best of luck!
SuperSoph_WD
 

Shapperd

Commendable
Aug 8, 2016
17
0
1,510


I'm testing something, I'll let you know when I'm sure about the result.

Update #1: Turned off Fast boot, it seems it fixed it, but i can't be sure for 1-2 days from now. If the problem will not return, then the answer is: "Turn off Fast boot option in windows" If it will return I'll delete this part of my comment.

Update #2 Yes it fixed the error, then as mentioned below, driver conflict should be the answer.
 

Karadjgne

Titan
Ambassador
More than likely that's a driver error or conflict. What happens in fast boot is when you use Windows to turn off the pc, it caches everything on the ssd/hdd so when you hit the power button, it pulls all the info from the cache. With fast boot turned off, when you start the pc, it initiates all the drivers from scratch, so loads the original drivers right out of Windows etc. With a false start or pushing reset, the pc basically skips the fast boot cache and loads everything from scratch. No way it's a Windows driver that's corrupted, likely culprits are gpu drivers in conflict with YouTube codas or even IE.

So something, somewhere that's working/loaded/used after windows actually starts is corrupting a driver, which fast boot will cache, but is not overwriting the original driver itself so false/reset works as normal.
 
Solution