The procedure entry point could not be located

Page Fault in Non-Paged Area is a blue screen error usually happening with faulty drivers but it can come from different issues like faulty RAM. In this short article, we will cover usual ways on how to approach and solve this error.

Solving Page fault in Non-Paged Area

Rollback using system restore

Simple and easy solution, roll back to the previous system restore point where Windows was stable and working.

Fix Page Fault in Non-Paged Area using device manager

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on device manager
3. Find a device with a question mark and right-click on it
4. Click on the rollback driver button

Fix via command prompt

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on command prompt (admin)
3. Inside command prompt type in SFC / scannow and press ENTER
4. Wait for the process to be finished and then reboot the PC

Fix via DISM tool

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on command prompt (admin)
3. Inside command prompt type in DISM /Online /Cleanup-image /Restorehealth and press ENTER
4. Wait for the process to be finished and then reboot the PC

Page fault in Non-Paged Area via a dedicated tool

Sometimes manual and provided solutions just simply cannot cut it because the issue is triggered also with something else and not just a single issue. Use DRIVERFIX to fix this specific issue with a single click.

Each time you connect to a Wi-Fi network your PC saves that network password. If for any reason you need to see this password or passwords there are ways you can do it and we are here to show you how. Hello and welcome to error tools where we aim to help you with all of your Windows problems and issues, where we offer our insight on various topics and sometimes go offroad and write something crazy. This time we will offer you a way on how to easily and quickly see how can you find out your memorized Wi-Fi password.

Find your W-Fi password

1. Make sure that you are connected to the Wi-Fi network you wish to find out the password of
2. Open Windows Settings app by pressing ⊞ WINDOWS + I
3. On the left side choose Network & Internet and click on it
4. Click on Advanced Network Settings
5. Inside Advanced Network Settings go to Related Settings
6. Select More Network Adapted Options
7. Right-click on your adapter and select Status
8. Click on Wireless Properties
9. Click on the Security tab
10. Click on enable on Show Character box beneath Network Security key to reveal Wi-Fi password

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer and see if the problem is fixed or not.

Option 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s causing the problem.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

There are times when the Windows Search doesn’t work and you wouldn’t have a clue as to why it happened since it does not give any error codes. In such cases, you have to check the error logs in the Event Viewer to find out more about the problem. From there, look for an error with the Event ID 3104 in the Windows error logs and if you see an error message that says, “Enumerating user sessions to generate filter pools failed”, read on as this post will guide you in fixing the problem. Apart from the error message, you might also see more information in the details section of the log that says, “(HRESULT: 0x80040210) (0x80040210)”. This kind of error is most likely caused by something that prohibits the search function from initializing. A lot of users assumed that it could be due to Cortana but it’s actually not. While some users also reported that they encounter the issue after they restarted their computers. This error was also reported with the same event ID 3104 on the Windows Server. According to security researchers, this error could be caused by problems in the Registry entry of Windows search. It could also be due to an issue with the SYSTEM account where it hasn’t been added to the DCOM Security. It is also possible that the Windows Search function has not been initialized. To fix this error, you can try to rebuild the Search Index manually or run the Search and Indexing troubleshooter. You can also check the startup type of the Windows Search service or try some registry tweak.

Option 1 – Try to rebuild the Search Index manually

The first thing you can do to fix the problem is to manually rebuild the Search Index. You can do that by going to Control Panel > Indexing Options and from there, click on Advanced. After that, go to the Index Settings tab and then click on Rebuild > OK. Once you’re done, check if it fixed the problem.

Option 2 – Try running the Search and Indexing troubleshooter

You could also run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings are in place and automatically corrects any issues with the Windows 10 search function. To run this troubleshooter, just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter. Once the troubleshooter is done, restart your computer and see if it fixed the error.

Option 3 – Try checking the startup type of the Windows Search Service

In this option, you have to check the startup type of the Windows Search service since the service won’t start. To do so, refer to these steps:

• Tap the Win + R keys to open the Run utility and type “services.msc” in the field and then tap Enter to open the Services Manager.
• Next, from the list of services, look for the Windows Search Service or WSearch. Once you find it, right-click on it and select Properties.
• After that, change the Startup type to Automatic and click on the Start button if the service is in the Stop state.
• Now click on the Apply and OK buttons to save the changes made and then restart your computer.

Option 4 – Try changing the Registry entry for Windows Search

Before you apply some registry tweak, you need to create a System Restore point first. Once you have that covered, follow these steps:

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and tap Enter to open the Registry Editor.
• If a User Account Control prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows Search
• From there, click on Windows Search and look for the key named “SetupCompletedSuccessfully” and change its value to “0”. Just right-click on it and select Modify.
• Then input “0” as its value data and click on OK to save the changes made.
• Exit the Registry Editor and restart your computer.
• Now check if the Enumerating user sessions to generate filter pools failed is fixed or not.

The number of Hertz is the number of how many images your screen draws in one second. So monitor with a refresh rate of 60Hz will draw 60 images each second on your screen. To most users, this will look fine and enough but actually, if you would place them in front of a 120Hz screen difference will be visible right away.

Benefits of higher refresh rates

In most simple words just looking at a screen that has a higher refresh rate will produce a more natural feel of things, although some people would argue that flickering can not be seen on 60Hz monitors and that should be enough, I would argue that they never watched the movie, played the game or used high refresh rate screen when they can state something like that.

Yes, 60Hz might be enough to look at the web page or read some documents but long exposure to 60Hz can have a tiring effect on the eyes in the long run. 120Hz and above just feel more relaxed and it is far less demanding on the eyes. Watching movies also is much better on a higher refresh screen, with way much less motion blur in fast scenes giving the overall experience a greater natural feel.

Gaming is perhaps an area where a refresh rate of 120Hz and above will show its best. Having a higher refresh rate will be easier on your eyes and can even give you a competitive edge. When for example you have twice more images per second on your screen than your opponent his movement will be more fluid and predictable because of that and overall precision will be much higher when moving the cursor in the game since more frames per second means more precision and smoother movement.

The dark side of high refresh rates

After all the positive things that were said about the advantages of high refresh rates, it is just fair to look at some negatives or in this case only negative one and that is Computer power. As said in the previous section having a 120Hz refresh rate means having 120 frames displayed on the screen per single second. Having even higher monitors like 360Hz means even more frames per second and in order to actually see all of that frames you will need to have enough computer power to back it up. Having for example screen with a refresh rate of 240Hz means nothing if your GPU and rest of the computer are able only to push 150 frames per second, in this case, you will still have 150 frames in one second despite the monitor being able to go to 240.

Conclusion

Generally and with all of my heart I would recommend moving away from 60Hz monitors, yes they are cheaper and more affordable but at the end of the day if you are someone like me who spends most of his daily time in front of the computer you would be grateful to have higher refresh rate screen and save your eyes, and after all, why not enjoy some smoother and better movie and game experience as well as saving your eyesight.

0x0000007c error inside Windows 11 is a printer error that is manifested when Windows users are trying to connect to a shared network remote printer. Error is displayed by the message:

Windows cannot connect to the printer. Operation failed with error 0x0000007c.

If you are experiencing this type of annoyance, fear now we are providing you with several solutions to this problem.

Update Windows 11

1. Open the Start menu, click on the settings app
2. Select Windows update tab
3. Click on Check for updates
4. Click on Advanced options
5. Inside select Optional updates
6. If there are optional updates click on Download & Install

Run the printer troubleshooter

1. Press ⊞ WINDOWS + I to open settings
2. Click on Troubleshoot navigation on the system tab
3. Select Other trouble-shooters
4. Click on the Run for printer troubleshooter
5. If the error is found click on Apply this fix

Restart the Print Spooler Service

1. Right-click on the Start button
2. Click on RUN
3. Type in services.msc and press OK
4. Right-click on Printer Spooler service and select Restart

Clear the Print Spooler

1. Open services like in the previous step
2. Right-click Print Spooler and select STOP
3. Open File explorer
4. Navigate to: C:\Windows\System32\spool\drivers\x64\3 (64-bit Platform) C:\Windows\System32\spool\drivers\W32X86\3 (32-bit Platform)
5. Delete everything inside folders
6. Go back to services, right-click on Print Spooler and select RESTART

Reinstall Driver for printer

1. Right-click on Start and select device manager
2. Double click on the Print queues category
3. Right-click on the printer and select Uninstall device
4. Click on Uninstall on prompt
5. Right-click on the Print queues category and select Scan for hardware Changes

In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

• Go to Settings.
• From there, go to System > Storage > Free Up Space and then click on it to launch it.
• Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
• Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

• Tap the Win + E keys to open File Explorer.
• Next, enable the Hidden Files view from the menu.
• Then go to C:/ProgramData/MicrosoftWindowsWER.
• From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
• Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.

Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:

• Right-click on the folder and then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.

Upgrading your Windows computer may not always go as expected as you could end up getting some error messages along the way. One of the error messages you can encounter is the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. This error indicates that is some security issue within the Windows operating system. It could be that the system files have an issue and they have been modified incorrectly. Although this does not necessarily mean that malware is behind the modification, one of the applications you installed recently might have something to do with the problem. The application might have modified or corrupted some of the core system files. When you encounter this error, you will see a blue screen along with the following error message:

“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (0% complete) If you’d like to know more, you can search online later for this error: 0xc000021a”

This error pops up when a user-mode subsystem like the WinLogon or the Client Server Run-Time Subsystem or CSRSS has been compromised fatally and security can no longer be guaranteed in the system. Thus, the operating system switches to kernel mode, and Windows won’t be able to run without the WinLogon or the Client Server Run-Time Subsystem. This is why it’s one of the few cases where the failure of a user-mode service can shut down the system. To resolve the issue, here are some fixes that might help.

Option 1 – Uninstall programs you installed lately

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 2 – Perform System Restore

Performing System Restore can also help you fix the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 3 – Run the System File Checker or SFC scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Rebuild the BCD and fix MBR

Rebuilding the BCD can help you in fixing the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
• exe /FixMbr
• exe /FixBoot
  • exe /RebuildBcd

The commands you entered should rebuild the BCD and repair MBR.

Option 5 – Run the CHKDSK utility

You can also run the Chkdsk utility to resolve the problem. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them.
• chkntfs /t
• chkntfs /t:10

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

A lot of users rely on keyboard shortcuts to carry out tasks on their PCs. One of the most common keyboard shortcuts used is the Ctrl + Shift + Esc which opens the Task Manager. As you can see, the Shift key is not just used to capitalize a text as it can also be used for other functions and plays an essential role in operating a computer. However, if you suddenly find it not working, read on as this post will help you fix the problem. If your Shift key is not working, there are several potential fixes you can check out to fix it. These are the different ways to get rid of the Shift key not working issue on Windows 10:

1. Physically clean the key and keyboard
2. Disable Sticky Keys.
3. Update, Reinstall, or Rollback Keyboard driver.
4. Test the keyboard on another system.
5. Check your connections
6. Run the Hardware troubleshooter
7. Troubleshoot in Clean Boot State.

Option 1 – Clean the keyboard keys physically

Your keyboard might not be working properly due to some dirt or other corrosion. Thus, you need to clean your keyboard, especially the Shift key. First, you need to shut down your computer and then unplug the keyboard if you are using a desktop computer and then prepare it for cleaning. After that, use a small cotton ear cleaning tool to get between the creases and clean them. You can dip it slightly in alcohol to make it more efficient in cleaning dust and dirt. And if you can, you have the option to pull apart the keyboard completely and then wipe away all the corrosion from the inside. Once you’re done, put the keyboard back together and then plug it back into your PC. Now turn your PC on and check if the Shift key is now working.

Option 2 – Try to disable the Sticky keys

Another thing you can try is to disable the Stick keys. How? Refer to these steps:

• Tap the Win + I keys to open the Settings app.
• After that, navigate to the Ease of Access section, and here, select Keyboard.
• Next, make sure that the option for Press one key at a time under the Sticky Keys is toggled off.

Option 3 – Reinstall, update or rollback your keyboard driver

Once you’ve determined that the problem is in the software part of the keyboard, it is now time to try to reinstall, update or roll back your keyboard drivers. To reinstall the driver for your keyboard, refer to these steps:

• From the WinX Menu, open the Device Manager.
• In the Device Manager, you should find your laptop’s keyboard under the “Keyboards” option. Right-click on it and select the “Uninstall” option.

Note: If you’re not quite certain about your laptop’s keyboard, you can uninstall all the keyboards if there’s more than one.

• After that, restart your PC and see if the keyboard driver is installing automatically. If not, open the Device Manager again and right-click on Keyboards, and select the option “Scan for hardware changes” to install it.

Once the keyboard driver is installed again, check if your keyboard is now working properly or not.

Option 4 – Try connecting the keyboard to a different USB port or another computer

The problem might have something to do with the USB port that’s currently in use by your keyboard. It could be that it’s not working so it makes sense to unplug it and attach it to another USB port. You can also clean the USB port on both ends to ensure that they are not affected by corrosion. In addition, you can also try connecting the keyboard to a different computer and see if the Shift key works there or not.

Option 5 – Try to check your connections

You can also try checking if the connection mode you are using for your keyboard is functioning properly. For instance, if you are using a Surface 2-in-device, you can clean the connection pins and see if it resolves the problem.

Option 6 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 7 – Put your PC in a Clean Boot State

You might also want to put your computer in a Clean Boot State to fix the problem with the Shift key. It could be that there is a third-party program that’s preventing the Shift key from functioning. To isolate this possibility, you need to put your computer in a Clean Boot State.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to connect the external devices and check if the error is now gone.