Question Blank screen after update to 1809 windows 10

lingarajug

Distinguished
Dec 21, 2013
139
3
18,695
was stable on 1803, recently performed update to 1809 and since then if i start my computer after not using for a while BIOS screen completes and then windows boot screen should come but screen goes blank and nothing happens and q code doesn't display any errors and if i hit reset button, it boots normally and it has been happening only if i boot PC after not using for few hours, asus rog rampage vi apex mobo, 7900x cpu, 32gb 3000mhz ram, samsung 970pro 512gb nvme, all drivers up to date, what might be causing this issue, any help appreciated.
 
This is probably a corrupted startup application. The fact your computer boots regularly after the failed boot would seem to indicate Windows is reverting back to it's last successful boot. Best to run sfc /scannow from an Administrator level command line. If it doesn't complete in Windows, go to Settings>Update and Security >Recovery> Restart. This will take you to the Startup Options where you can login to a Command Line outside of windows and run sfc /scannow again. Here are some other things to check https://www.reginout.com/help-center/windows-10-booting-black-screen-tackle/
 

Colif

Win 11 Master
Moderator
Could also be a driver, see if turning fast startup off resolves the need for a restart - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

what are specs of PC? Can you run driverview and in its options, set it to not show microsoft drivers - we may be able to find some old drivers that may cause this. Take a screenshot and upload it to an image sharing website and show link here.

normally, if SFC cannot correct everything, you run DISM and let it replace the files that SFC uses to fix files, then run SFC again. So something like this:

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

SFC doesn't always work well from outside windows.
 

lingarajug

Distinguished
Dec 21, 2013
139
3
18,695
Rog rampage vi apex x299 mobo, i9 7900x cpu, 3000mhz 32gb ram, samsung 970 pro nvme, zotac 2080ti amp, it started happening after updating to 1809, will try sfc and other mentioned solutions, not sure why the pc would start if powered off at the wall socket or press reset button and subsequent restarts have no issues, only occurs when PC not used for few hours.
 
It's likely the issue is your upgrade and "Fast Start up" aka fastboot. When you upgrade Windows leaves some of the old version behind, which can cause some corruption issues. With Fast Start, your computer "saves the current system state to the hibernation file, and turns off the computer. When you start the computer again, Windows does not have to reload the kernel, drivers, and system state individually. Instead, it just refreshes your RAM with the loaded image from the hibernation file and delivers you to the login screen. However sometimes the saved system state becomes corrupted. This can happen when your computer completely powers down, which does not happen right away when the computer shuts down. To see this turn off and unplug your computer, then with the side plate of your computer removed, push on switch the on switch and you will see the CPU start to spin and then stop); it may take several hours to drain this last bit of electricity. Again this is normally not an issue because Fast Start saves the system state in flash memory (or similar) which is not supposed to be volatile when powered down. When the Fast Start fails (and does not shut down properly), your computer boots without fast start, which is why it is successful the second time. To turn off Fast Start go to the control Panel, choose Power Options>Choose what the power buttons do> Change Settings that are Currently Unavailable> and uncheck "Turn on fast start up". While this is not a sure fix, it should have a good chance working. The is more to read at this link..

 
Last edited: