Oculus Quest 2
![occulus quest 2 VR](https://errortools.com/wp-content/uploads/2021/07/occulus-quest-2-VR.jpg)
Valve Index VR
![valve index vr](https://errortools.com/wp-content/uploads/2021/07/valve-index-vr.jpg)
Sony PlayStation VR
![playstation vr](https://errortools.com/wp-content/uploads/2021/07/playstation-vr.jpg)
HP Reverb G2 VR
![HP Reverb G2](https://errortools.com/wp-content/uploads/2021/07/HP-Reverb-G2.jpg)
HTC Vive Cosmos
![HTC Vive Cosmos](https://errortools.com/wp-content/uploads/2021/07/HTC-Vive-Cosmos.jpg)
Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.
The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:
You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.
If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.
After troubleshooting, below you’ll find a few solutions to rectify the issue.
Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.
If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link.
If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.
You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.
If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first.
First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation.
If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up.
Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.
If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).
Other troubleshooting steps include:
If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.
del *.*
PC Optimizer Pro is a PC optimizer utility developed by Xportsoft Technologies. It is classified as a potentially unwanted program, due to its aggressive scan and registration reminders, and that it is often distributed bundled with other programs in a manner that leads many users to not know how it got on their computer. While not inherently malicious, PC Optimizer Pro adds numerous registry keys, startup entries and while running consumes a relatively high amount of system resources, especially during its scans. The software installs from a .exe file that is around 5.20 MB or 5.453.240 Bytes (depending on the version). As of the publication of these videos, the current version of PC Optimizer Pro was detected as malicious or potentially unwanted by at least 21 AntiViruses.
Stop 0X00000050 (parameter1, 0, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA”
“Something went wrong, We weren’t able to set up your PIN. Sometimes it helps to try again or you can skip for now and do this later.”On the other hand, here’s the error message you get for the Microsoft Store-related error:
“Try that again, Something happened on our end and we couldn’t sign you in.”Here are some potential fixes you can try to fix the Error Code 0x80090016 in the Microsoft Store:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml
“This policy setting allows you to control whether a domain user can sign in using a convenience PIN. If you enable this policy setting, a domain user can set up and sign in with a convenience PIN. If you disable or don’t configure this policy setting, a domain user can’t set up and use a convenience PIN. Note: The user’s domain password will be cached in the system vault when using this feature. To configure Windows Hello for Business, use the Administrative Template policies under Windows Hello for Business.”
chkdsk C: /f /x /rNote: “C” is the drive root drive so it could be changed if you’re using a different one.
“Something went wrong, try rebooting your PC and then launch GeForce Experience, ERROR CODE: 0x0001.”Errors like this one diminish the overall experience of users due to the fact that when this error occurs, the NVIDIA GeForce experience wouldn’t even start which renders its features useless. There are several potential fixes you can check out to resolve this error but before you check them out, you can try to restart your computer first and then open the NVIDIA GeForce Experience once again, if you still encounter the error, then you need to check the NVIDIA Display Driver Services or update your NVIDIA display drivers or switch to the BETA release. You could also try to install and reinstall the NVIDIA display drivers or perform System Restore and see if it helps. For detailed instructions, follow the given options below.
“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.