Question PC Takes 10 Minutes to Reboot

Toggle sidebar Toggle sidebar
S

Snakes1000

Reputable
Dec 15, 2015
42
0
4,530
I have had this issue for a few months now. I did some research and came to the conclusion that it must be a hard drive that was causing the issue, especially as I could hear one of my drives spinning up just before the boot finally concluded and the login screen appeared. Up until then I just get the default windows desktop screen with the whirring circular dots.

I did the various checkdisk routines on all my drives and whilst I found some potential issues these were fixed using the repair processes and/or replaced. This did not solve it so I finally got around to disconnecting every drive except my SSD C drive. The problem still continued. So, it is not a disk drive issue.

I, again, Googled the issue and followed a load of possible culprits that others had found but, to be honest, I've now become completely confused by the whole thing. And, having to test every solution tried, when it takes 10 minutes each time, becomes a bit wearing!

So, as well as pasting my PC spec below I did also create a boot log in the hope that this might show a cause (details HERE). Examination of that shows that there appears to be a problem loading some drivers (these rows are marked with the prefix >>>>>>>>>>>) but when I tried to investigate that issue I got even more confused!

So could someone try to help me identify the possible cause of this lengthy reboot time which is consistently 10 minutes?

The boot log may be a red herring.

Many thanks in advance.

Clive

PC Spec:-

OS Version: Microsoft Windows 10 Pro, 64 bit
Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, Intel64 Family 6 Model 94 Stepping 3
Processor Count: 8
RAM: 16340 Mb
Graphics Card: NVIDIA GeForce GTX TITAN X, -1 Mb
Hard Drives: C: 893 GB (93 GB Free); E: 465 GB (357 GB Free); F: 5588 GB (5364 GB Free); G: 1397 GB (823 GB Free); H: 1862 GB (985 GB Free); I: 5588 GB (1249 GB Free); J: 7451 GB (1835 GB Free); K: 465 GB (445 GB Free); L: 1863 GB (1860 GB Free);
Motherboard: Gigabyte Technology Co., Ltd., Z170X-Gaming 7
Antivirus: Avast Antivirus, Enabled and Updated
 
Last edited:
Sort by date Sort by votes
is it slow before or after login screen?

seems to have problems loading directX as it tries about 6 times, do you have latest Nvidia drivers?

see if this helps
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
 
Upvote 0 Downvote
I am running through the SFC /scannow routine as I type but, in the meantime, to answer your initial question, it is slow before the login screen. I get the motherboard screen then immediately it moves to the "standard" window logo/icon (as per your signature) with the whirring dots where it sits for 10 minutes before the logon screen appears. That's just after I hear a disk drive spin up and it recognises my iPad attached by USB. After that it is quick. I'll report back once the above routines are completed
 
Upvote 0 Downvote
do these things:-

1) disable fast startup by following https://www.petri.com/how-to-disable-windows-10-fast-startup-and-why-you-might-want-to . fast startup can mess up some things

2) do memtest to test memory

3) install hard disk sentinel and crystaldiskinfo to test health of all hard disks

4) do this command in addition to sfc /scannow:-
dism /online /cleanup-image /restorehealth
(u should be in elevated command prompt to do both commands)
 
Upvote 0 Downvote
Just concluding the advice from Colif. And thank you Colif for trying to help!

I did as you suggested and have inserted the outcome of the Powershell window below. I have also got the CBS log but cannot find how to attach it. I realise I could paste the contents below but it is a long document. Anyway, despite the corrupted files being repaired it still takes 10 minutes to reboot.

48445398182_4f6f2acec5_b.jpg
 
Upvote 0 Downvote
However, after getting the system to work I would really recommend that you backup all your personal files and then format the system drive. Your corrupt file are fixing and that is taking time for rebooting process.
 
Upvote 0 Downvote
it appears that sfc fixed them the 2nd time anyway since the middle command fixed the files that sfc uses to scan for problems. That is what is meant to happen.

how slow is it if you unplug all unessential USB devices, like that ipad. it could be a device is slow to respond to windows and it waits until it times out
 
Upvote 0 Downvote
Thanks everyone for trying to help and I will try all your suggestions but I'm just going to answer Colif first.

I did note that the corrupt files were fixed and di understand that was how the process should work but the PC still takes 10 minutes to reboot. I have, in the past, disconnected everything including internal drives, iPad, etc. and the timescale is the same.

Is there a way to attach the log file?

Now answering Shadi. Fast start already disabled. Just about to do memtest (so, that will be a 10 minute wait until I get the answer! I have done all those disk tests, etc. before and, as I have said, the problem persists even when all but the C drive SSD detached. I will try the "restore health" routine after the reboot and mem test.
 
Last edited:
Upvote 0 Downvote
Shadif........ no memory issues - test completed successfully. I did the dism /online /cleanup-image /restorehealth routine and got this

48445572841_a97186965f_b.jpg


Will now try another restart. Back in 10 minutes!
 
Upvote 0 Downvote
his restore health routine was the same as the Repair-WindowsImage -Online -RestoreHealth I suggested already, just in a different format

to upload the cbs log, which should be clear now cause 2nd SFC fixed the problem, you would need to upload it to a file sharing website and show link here

Do you have latest bios for motherboard?
have you tried to run display off motherboard, remove gpu, only have 1 stick of ram attached. Try to run with as little inside PC to see if we can narrow down the cause. slowness at boot stage, as I said, can mean a part is slow to respond. Could be GPU given the bootlog
 
Upvote 0 Downvote
Hi Colif,

I did wonder if Shadif's routine was the same as yours. Anyway, no improvement.

Original CBS log is HERE
Subsequent one after completing routines is HERE

I haven't updated the mobo BIOS but, to be honest, I'm a bit wary of doing so given all the "health" warnings from Gigabyte about doing so. Do I need to be concerned?

Could you expand on your suggestion "have you tried to run display off motherboard" for me so I can try that?

I assume you are suggesting that I should then try removing the nVidia graphics card next?

Then remove one stick of RAM?

When I get the answer to the first query I'll try each suggestion and report back.

Thanks again everyone for suggestions.
 
Last edited:
Upvote 0 Downvote
your CPU has graphics cores (most intel CPU do), https://ark.intel.com/content/www/u...-6700k-processor-8m-cache-up-to-4-20-ghz.html
your motherboard has a displayport and HDMI port on back (HDMI port says it needs an intel driver to work)

Integrated Graphics Processor-Intel® HD Graphics support:
  1. 1 x DisplayPort, supporting a maximum resolution of 4096x2304@60 Hz
    * Support for DisplayPort 1.2 version.
Integrated Graphics Processor+MegaChips MCDP2800 chip:
  1. 1 x HDMI 2.0 port
    Requires the latest Intel® Graphic Driver from GIGABYTE website.
I am not 100% sure, you may need to go into bios to enable the connections, but you should be able to run display off the motherboard connections and see if that makes any difference.
 
Last edited:
Upvote 0 Downvote
Colif, I am a little uneasy about trying some of your suggestions so I need to be sure I have understood them correctly.

I want to try taking out the nVidia GPU first. And, therefore need to get a monitor working from the motherboard first.

But I have 3 monitors. One only has a DVI connector so that won't work with the motherboard sockets. The second has both an HDMI and a Display Port connector but it is too large for the motherboard driver (it states max 4096 x 2034 @ 60Hz whereas mine is 5440 x 1440 @ 60Hz). I did try connecting this but got nothing but a blank screen (no signal). The third monitor has an HDMI connector so that would work with the motherboard HDMI socket but that requires the Intel driver. I have looked at the website and I assume it should be on THIS PAGE but I can't see it. There is a VGA driver and there is also an HDMI 2.0 FW Update Tool under the Utilities section. I have downloaded that but it states I should update VGA driver first (in the note) and should update the BIOS as well beforehand. I haven't yet run that Utility. I'm nervous about doing any of these things but will if I get clear guidance.

Also, do I need to remove the graphics card before any of the motherboard sockets will become live? I wouldn't have thought so.

Cheers in advance.
 
Last edited:
Upvote 0 Downvote
if you removed gpu, it would only be for a test. not long term. (i hope).
as such you would only need 1 monitor attached anyway. not all 3

don't do it yet, I get some other people to look at thread.

which bios version are you on? as if its an older version, it could be your bios doesn't recognise an item in PC and takes this long to start up. PLease don't say F2 as that is the release version and there are 11 versions since then.
Gigabyte use Q flash, this page contains link to a pdf that shows steps on how to upgrade bios. - https://www.gigabyte.com/MicroSite/121/tech_qflash.htm

its fairly safe to do provided you don't live in an area that gets random blackouts, and I wouldn't suggest during a thunderstorm. I only suggest BIOS updates if you are having problems.
 
Upvote 0 Downvote
Hi Colif, thanks for your continued support. Bios version is F21. I think the latest (which I have downloaded but not updated yet) is F22m. I have read all about how to update the BIOS using Q-flash. But I will wait until I have exhausted other possibilities I think.

I realise I only need one monitor attached but the only one that would work with the connectors is the one that needs the driver and that is why I asked your advice to check the website to see if you could identify it.

In the meantime, I have found this website that appears to be the most comprehensive description of how to identify and fix what is causing my problem (ever the optimist!). Do you agree?

I'll wait until I hear back from you.
 
Upvote 0 Downvote
Obvious question: do you have latest Nvidia drivers?
https://answers.microsoft.com/en-us...d/c6b2dd1f-d44e-4e88-b162-fddcdf3b5265?auth=1

another fix I found was update windows, you are on the November update from 2018, there is a newer version of win 10 that might help.
another suggested fix is reinstall windows.

Do you get a picture while waiting at start up, or just a black screen?

asking for a 2nd opinion, I didn't before cause I thought you be away longer.
 
Last edited:
Upvote 0 Downvote
Hi Colif. I definitely have the latest nVidia drivers (I regularly check and keep updated).

I will try updating Windows today but I have a feeling that the issue has preceded that last update.

I explained in one of my earlier posts that during the 10-minute startup time I get a black screen with the blue window pane logo/icon similar to your signature image.

One very strange thing to report. I have this query running on the TechGuy forum and someone suggested doing a Shift/click/Restart to get to the Troubleshoot>Advance>Startup Repair routine. I tried this and received the message "Diagnosing your PC" then "Attempting Repairs" then "Startup Repair couldn't repair your PC". This is the weird bit - "Log file in K\Windows\System32\logfiles\Srt\srttrail.txt" - I DON'T HAVE A K: DRIVE!.

I have looked at that location (but on my C drive) and there is a srttrail file (of yesterday's date) there. Looking at that I have found the reason for the failure of the attempt to repair:-

Root cause found:
---------------------------
Boot critical file k:\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 1906 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 426438 ms

Once again, I don't have a K drive so where is this coming from?

Could it be the confusion between the C and a K drive naming error? Is it the bootres.dll in the C drive that is corrupt?

P.S. What did you think of the website link I provided in my previous post?
 
Last edited:
Upvote 0 Downvote
When you did this - Shift/click/Restart - and booted into the windows recovery mode, the boot order of drives gets messed up as windows isn't running off the boot drive, its running off a ram drive. So K is C Drive, especially given you probably only have windows on 1 ssd (it is)


did you run chkdsk before? it is one fix for that problem

open command prompt (with admin rights)
type
chkdsk c: /f
and press enter
That command will fail, as Windows cannot check your disc while Windows is running, you will be asked if you want to run check disc at startup, choose yes

Then shut your system down and restart it to run disc check . . .

another is SFC which we have done already.

some other suggestions - https://answers.microsoft.com/en-us...-corrupt/582bd0ba-e29f-46b3-b347-2fd73c8556e3

methods 2 & 3 in your link similar to another site I often offer for errors with boot files - https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508
 
Last edited:
Upvote 0 Downvote
OK, just waiting for it to complete... In the meantime, assuming there is no C drive versus K drive issue, what about the failure found in the text file.....

Root cause found:
---------------------------
Boot critical file k:\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 1906 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 426438 ms
 
Upvote 0 Downvote
Snakes1000 said:
OK, just waiting for it to complete... In the meantime, assuming there is no C drive versus K drive issue, what about the failure found in the text file.....

Root cause found:
---------------------------
Boot critical file k:\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 1906 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 426438 ms
Click to expand...

I covered that here
Colif said:
did you run chkdsk before? it is one fix for that problem

open command prompt (with admin rights)
type
chkdsk c: /f
and press enter
That command will fail, as Windows cannot check your disc while Windows is running, you will be asked if you want to run check disc at startup, choose yes

Then shut your system down and restart it to run disc check . . .

another is SFC which we have done already.

some other suggestions - https://answers.microsoft.com/en-us...-corrupt/582bd0ba-e29f-46b3-b347-2fd73c8556e3

methods 2 & 3 in your link similar to another site I often offer for errors with boot files - https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508
Click to expand...

but as I said last post, only do that if the update didn't fix it as version updates replace the current install, so might fix.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom