Solved slow boot

sprite · Mar 15, 2014

Hi!
My PC takes its sweet time to boot given the specs it has. (around 1.75 mins) Especially the "black" part seems to take so long. I've fastboot enabled and I use UEFI.

Any ideas regarding what might cause this behavior, and how to make the PC boot faster ?

ps: I've read some topics about this issue (disabling fastboot etc. ) and none of them worked.

MilesAhead · Mar 15, 2014

The quickest thing to try is boot logging. Start msconfig(typing msconfig in the Run box works) then click the Boot Tab. Click the Boot Logging check box. Restart. The boot log file should be named ntbtlog.txt and it should be in the root of the system partition(usually C:\ntbtlog.txt.)

Often slow boots are caused by attempts to load drivers that no longer exist or cannot be found. The system waits until the time out limit for the file to load. One thing that caused my system to have a 2 minute warm boot cycle was Norton AV that was removed. But the driver load commands were still in the registry.

Don't forget to run msconfig and turn boot logging off once you have the log file.

sprite · Mar 16, 2014

Thanks for your reply.
I've got some interesting stuff going on with my booting.

There were some issues with some paragon drivers

Code:

BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\uim_vimx64.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\Uim_IMx64.sys

I simply unticked them in Autoruns (I've uninstalled all paragon software a long time ago) and so these problems are gone.
However there are some issues I don't know anything about:

Code:

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\cdrom.sys

BOOTLOG_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\BasicRender.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\uimx64.sys

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys

BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\NDProxy.SYS
BOOTLOG_LOADED \SystemRoot\System32\Drivers\NDProxy.SYS
BOOTLOG_LOADED \SystemRoot\System32\drivers\usbhub.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\NDProxy.SYS
BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\NDProxy.SYS
BOOTLOG_NOT_LOADED \SystemRoot\System32\Drivers\NDProxy.SYS

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys

BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\gzflt.sys
BOOTLOG_NOT_LOADED \SystemRoot\system32\DRIVERS\trufos.sys

BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srv.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\srv.sys

In the second line it says the dxgkrnl.sys (directx kernel file ?) has been loaded, yet a line later it states that it can't be loaded. Then the dxgkrnl.sys issue recurs through the log file.
The same with NDProxy.sys: the log says it's not loaded, then it's, then it's not four more times. This also happpens with srv.sys at the end of the log.

There are some cuties as well that I have no idea about (cdrom.sys, uimx64.sys, gzflt.sys , trufos.sys)

MilesAhead · Mar 16, 2014

I would back up your registry with a Restore Point and ERUNT freeware. Then run CCleaner Registry clean and have it clean all found issues. When it offers to make a backup .reg file accept. I only had one version of CCleaner that had a problem with registry cleaning. But I regretted not making the backup.

See if that removes the unnecessary driver loads.

sprite · Mar 16, 2014

I use CCleaner frequently , it doesn't help with these problems

MilesAhead · Mar 16, 2014

sprite said:
I use CCleaner frequently , it doesn't help with these problems

Did you use the registry tool or just the cleaner function?

MilesAhead · Mar 16, 2014

There are some cuties as well that I have no idea about (cdrom.sys, uimx64.sys, gzflt.sys , trufos.sys)

If CCleaner won't automate dead driver removal then there's manual mode. Search driver name, find out what it is, and if you need to run it. If not, search registry for the load location and delete it. Back up first as always.

sprite · Mar 16, 2014

I appreciate your help, but the drivers that I have problems with are all microsoft. (dxgkrnl is the directx kernel, NDPROXY is a system-provided driver that interfaces NDISWAN and CoNDIS WAN drivers, srv.sys is a Windows Server driver) These are all built-in.

MilesAhead · Mar 16, 2014

sprite said:
I appreciate your help, but the drivers that I have problems with are all microsoft. (dxgkrnl is the directx kernel, NDPROXY is a system-provided driver that interfaces NDISWAN and CoNDIS WAN drivers, srv.sys is a Windows Server driver) These are all built-in.

Which seems to contradict

There are some cuties as well that I have no idea about (cdrom.sys, uimx64.sys, gzflt.sys , trufos.sys)

It seems they are being loaded more than once. Again, I'd search the registry for redundant loads. I don't know any way to avoid the heavy lifting or I'd suggest it.

sprite · Mar 16, 2014

Should I just look for the file (eg dxgkrnl) and just delete the second, the third etc. entries it appears ?

BTW the I have no idea about part referred to the fact that I have no idea what might cause this kind of behavior of theirs.

MilesAhead · Mar 16, 2014

Maybe there's a better way. AutoRuns

shows auto start programs, services etc.. it has a Drivers Tab that should make it a bit easier.

sprite · Mar 16, 2014

But can I disable windows built-in drivers without messing up the whole os ?

MilesAhead · Mar 16, 2014

sprite said:
But can I disable windows built-in drivers without messing up the whole os ?

The idea is not to disable the drivers. The idea is to delete redundant loads. The system gets an error because you are trying to load an already loaded driver. I would search the registry for load locations that do not match those listed in AutoRuns.

Back up your registry as searching through RegEdit can be tedious. Or you can gamble and try some other registry cleaner programs. I would read a lot of user reviews before trying any other than the CCleaner one. Again, backup is what saves the bacon.

I haven't tried regisry optimizers since it is risky. But in your case it may not be much rikier than slogging through regEdit by hand provided you have backups. Just be careful. You don't want to get it to the point it won't boot. I'd make the Macrium Rescue discs and make sure they boot before proceding. They might pull you out of a jam.

sprite · Mar 16, 2014

Thanks

Solved slow boot

New Member

My Computer

Eclectician

My Computer

New Member

My Computer

Eclectician

My Computer

New Member

My Computer

Eclectician

My Computer

Eclectician

My Computer

New Member

My Computer

Eclectician

My Computer

New Member

My Computer

Eclectician

My Computer

New Member

My Computer

Eclectician

My Computer

New Member

My Computer