Slow start-up BEFORE login screen

It used to (few days ago) take less than 10 seconds to get to the login screen once the BIOS was finished, now it's taking more like 25 seconds. Since this is pre-login, I assume it has nothing to do with startup programs (note that startup is lightning fast once I login) and is more likely a driver issue?

From what I've read on forums, the suggestion is usually to consult the Event Viewer and/or configure Windows to give "verbose" messages during startup so you can monitor the start-up process?

Does that about sum it up?

Thank you!

It could be a network issue. If your PC is configured to get its IP address and other settings from a DHCP server, such as a modem or router, and it is switched off, then it can lengthen the time to boot up if its searching for a router and then times out. If you leave the modem/router on then it should pick it up fast and make boot times faster.

Another thing to check for, is for the number of startup items that are loaded. Use MSConfig.exe to see what is loaded after Windows is started. Reducing these can improve startup and login times.

OK, I'll try to get those system details updated. I believe the culprit ended up being NIS 2012. I did a system recently and that seemed to freak Norton out a little. When I uninstalled and reinstalled, I ended up with NIS 2012. When I tried to disable Safe Search, NIS 2012 sort of froze leading to the startup delays I believe. I uninstalled and reinstalled a few times, each time leading to the same problem, and finally Norton must have figured out something was wrong and ended up installing NIS 2011 as before. I'm back to the normal 15s (from my memory) of seeing the "Windows is starting up message". However I might as well to take this opportunity to post three errors that I am seeing in the Event log if I may:

1: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

2: \SystemRoot\SysWow64\Drivers\crlscsi.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

3: The following boot-start or system-start driver(s) failed to load: crlscsi

I've seen several people post the first log event and it seems a tough one to solve. The other two have to do with an old Corel driver from an old Corel program that I migrated over from previous computer. What is the best way to disable a driver from loading at boot-up/start-up? Do I simply look for all references to the driver in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\crlscsi
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\crlscsi

and delete them? Any ideas as to the cause of the first error?

Thank you!

Specs updated.

Do you know how to address these three errors from the Even Viewer error log?

1: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

2: \SystemRoot\SysWow64\Drivers\crlscsi.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

3: The following boot-start or system-start driver(s) failed to load: crlscsi

I've seen several people post the first log event and it seems to be a tough one to solve.

The second and third log event have to do with an old Corel driver from an old Corel program that I migrated over from previous computer. What is the best way to disable a driver from loading at boot-up/start-up? Do I simply look for all references to the driver in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\crlscsi
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\crlscsi

and delete them?

Norton seems to be ok now and is unrelated to the three event view errors, so for the moment I think I'll stick with it (as I have paid for it), although I appreciate your recommendation.

What is the best way to disable a driver from loading at boot-up/start-up? Do I simply look for all references to the driver in the registry and delete them?

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\crlscsi
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\crlscsi

Thank you!