This error suggests poorly written software (or malware).
What happened to your system shortly before this problem started?
What antimalware software are you using, and is your subscription current?
There are two general methods for diagnosing errors that appear when Windows starts.
- Download and run Autoruns: https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
When the scan completes (Ready will appear at the lower left of the Autoruns window), select the "Logon" tab.
Carefully review each item. If you don't recognize something, right-click it and select "Search Online." If the online search doesn't help you understand what the item is, or if you believe an item is suspicious, make a note of the item's name and its "Image Path" so you can report that information in your Reply here.
Please read through the entire Logon tab and collect the information from all unknown or suspicious items before reporting them in your Reply here rather than having multiple replies. One easy way to do this is to open a Notepad window, then right-click on a suspicious item in Autoruns, select Copy, and then Paste into the Notepad window. When you're done, just Select All (CTRL+A) in the Notepad window, Copy (CTRL+C), and Paste (CTRL+V) into your Reply.
If you discover an item that you're sure doesn't belong, just clear the checkbox and the left end of the line. This will prevent the item from starting when Windows starts, but will allow you to reinstate the item's startup status (if you were wrong about it) simply by re-running Autoruns and checking the box.
- Using Autoruns is an attempt to analyze startup items and determine which one is causing the error. You can also approach this using a more brute force method: using the "Clean Boot" method as follows. This is generally effective but very tedious (as you will see below).
- Click Start, type msconfig in the Search box, and press Enter
- When the System Configuration utility (msconfig.exe) opens, select the "Startup" tab and click "Disable All."
- Select the "Services" tab, click to check the box next to "Hide all Microsoft services," and then click "Disable All."
- Click OK and "Reboot now."
Hopefully, the error will not appear when Windows restarts. Assuming that to be the case, re-run msconfig, select the "Services" tab, and click "Enable All." Once again, click OK and "Reboot now." (If the error DOES appear at this point, your problem is more difficult than the usual situation, and "Clean Boot" will not help. Run msconfig, select "Normal startup" on the "General" tab, reboot, and come back here and describe what happened.)
If the error does NOT appear this time, you know that the problem is not caused by a system service but rather by one of the startup items, In this case, you can leave the system services all enabled.
On the other hand if the error DOES appear this time, the problem is caused by one of the services and you now have to determine which one. To do this, run msconfig, go to the "Services" tab, and re-enable half of the services. I suggest ordering the list alphabetically (this should already be the case, but if not, click on "Service" in the header row of the table) to help with this.
When you restart this time, if the error appears, you know that it is caused by one of the services you had re-enabled; if it does not appear, you know that it is caused by one of the services that you left disabled.
Narrow things down by half and rebooting until you isolate the problem service.
If the problem was not caused by a system service (and thus you had re-enabled all of them), follow the same process with the startup items. That is, disable half, reboot, and check for the error. Repeat until the problem startup item is identified.