GA-Z77X-UD5H Intermittent Boot Hang / Failure

[sc489]

GA-Z77X-UD5H BIOS v16j, Windows 10 v1809

When booting my PC after it has been turned off at the mains for while, the boot screen and rotating logo sometimes displays too long and the PC eventually goes to Windows Automatic Repair. The PC then boots normally if I turn the PC off and back on at the mains. The boot problem is less likely to happen if I wait at least 15 secs before turning on the mains to he PC then pressing the PC on button. There are no error reports in Windows and chkdsk reports no problems on all drives.

Any ideas what is causing this issue?

[shadowsports]

Greetings,
Causes for this behavior:

Hardware:
Older, tired hardware.  failing disk, power supply, unmatched non QVL memory.

More likely however this is something software related.

Is this a new issue?  If so, try System Restore. 

Great you have checked your disk's over all health using chkdsk.

The next step is running SFC /scannow from an elevated command prompt.

Are any integrity violations reported?  Repairable?

If SFC reports issues which are not repairable, this DISM command might help.

DISM /Online /Cleanup-Image /RestoreHealth (Also run from elevated command prompt)

Corrupt start up files?

Try Windows Advanced Start Up > Troubleshoot > Advanced Options > Command Prompt

enter> C: cd Windows\System32\LogFiles\Srt. SrtTrail.txt

Review the output for critical or corrupt errors.  Delet if neccessary

Ultimately this is not likely related to your hardware.  Its probably a software issue.  If you are not backing up your system on a regular basis, I recommend you implement a back up solution.  Windows Back Up, Acronis, Macrium Reflect are all great choices.

Additional help here:

https://windowsreport.com/windows-10-automatic-repair-couldnt-repair-pc/

Some of which I already mentioned. 

[sc489]

I turned off Fast Boot in the BIOS on the advice of Gigabyte Support and the problem is now fixed

[shadowsports]

I turned off Fast Boot in the BIOS on the advice of Gigabyte Support and the problem is now fixed

Good to know.  Thanks for the follow up.