Unfortunately it doesn't look like the delay got captured in the trace. You see that you get to post-boot phase after ~15 seconds.
So that means that either you didn't hit the issue on this boot or the delay is so early in the boot process that it's not getting logged.
I had the issue for sure. So if it isn't logged do you think it is down to bios level? It was the same in the performance report I posted earlier. You can see the issue in the video I posted. It's so strange it logs only 15 seconds when it takes a lot more..
The tracing starts in the pre-session phase, which is when the kernel is getting loaded. So it's down to the BIOS or early Windows boot phases.
Do you see this issue in safe mode?
Yes it is present in safe mode too
Can you redo the video showing just the screen. Moving the camera gives us zero idea what is going on. Check your startup items in Task Manager and see what else is loading. 15 seconds is not a lot, unless you also have it rebuilding the Page, Hibernate, have Delay Boot to 0 or grayed out in msconfig. Do not disable Write Caching, etc., that some people state improves things, but disabling certain cache with a SSD will actually slow it down.
You used to be able to view the drivers being loaded during boot on the screen but it looks like that no longer works, at least on my system. Can you give it a try just in case? In MSCONFIG:
If you don't see anything on the screen then you can look at the boot log file in \Windows\ntbtlog.txt and see if there's any error messages. The log is concatenated on every boot so another thing you can try is:
1. Enable MSCONFIG settings as above.
2. Delete any existing \Windows\ntbtlog.txt file.
3. Reboot system. Keep track of the time when BIOS starts booting and when you see the spinning wheel.
4. While system is stuck during boot, press the reset button or forcibly power off the system.
5. Boot up the system normally and check the log to see what was the last driver loaded before you pressed the reset button on the previous boot.
You can post the log file somewhere. This will tell us if Windows is stuck loading a driver.
Disable the scpService (Ds3Service / Scarlet.Crush Productions) and test.
Ok so here is what I did.
I disabled that service but the issue persists(it is just a driver so my ps3 controller gets recognized as a genuine xbox360 controller so I can play all games on steam with it :)
I set it up like that and unfortunately you can't see the drivers on screen. But I took a look at the log. At first this was always the last couple of lines (I tried 3 times) :
BOOTLOG_LOADED \SystemRoot\System32\drivers\asyncmac.sysBOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sysBOOTLOG_LOADED \SystemRoot\System32\drivers\tunnel.sysBOOTLOG_LOADED \SystemRoot\system32\drivers\wcnfs.sysBOOTLOG_LOADED \??\C:\Program Files (x86)\Samsung\Samsung Magician\magdrvamd64.sysBOOTLOG_LOADED \??\C:\Program Files (x86)\Samsung\Samsung Magician\magdrvamd64.sys
So naturally I uninstalled samsung magician and it changed but I don't know what to think of it. So now it comes to this:
BOOTLOG_LOADED \SystemRoot\System32\drivers\ndiswan.sysBOOTLOG_LOADED \SystemRoot\System32\drivers\tunnel.sysBOOTLOG_LOADED \SystemRoot\System32\drivers\condrv.sysBOOTLOG_LOADED \SystemRoot\system32\drivers\wcnfs.sysBOOTLOG_LOADED \SystemRoot\System32\drivers\asyncmac.sysBOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
Full log with magician and without
At what times did you press the reset button?
Quote
