4. Update your Realtek audio driver
So, in this situation, it was discovered that the Realtek HiDefinition Audio driver, labeled as Creative Audio Driver, was out of date.
If you have been experiencing a similar BSOD problem in Windows 10, you need to download the latest Realtek drivers. Save yourself some time and do it automatically with a third-party program.
Some of the most common Windows errors and bugs are a result of old or incompatible drivers. The lack of an up-to-date system can lead to lag, system errors or even BSoDs.To avoid these types of problems, you can use an automatic tool that will find, download, and install the right driver version on your Windows PC in just a couple of clicks, and we strongly recommend DriverFix.Follow these easy steps to safely update your drivers:
- Download and install DriverFix.
- Launch the app.
- Wait for the software to detect all your faulty drivers.
- You will now be presented with a list of all the drivers that have issues, and you just need to select the ones you’d liked fixed.
- Wait for DriverFix to download and install the newest drivers.
- Restart your PC for the changes to take effect.
Keep your Windows safe from any type of errors caused by corrupted drivers, by installing and using DriverFix today!
Disclaimer: this program needs to be upgraded from the free version in order to perform some specific actions.
5. Turn off BlueStacks/ another Android emulator
- Open Notepad.
- Enter the following lines:
C:Program Files (x86)BlueStacksHD-Quit.exe
net stop BstHdUpdaterSvc
net stop BstHdLogRotatorSvc
net stop BstHdAndroidSvc
- Click on File and then on Save as.
- Set Save as type to All Files. Enter script.bat as the file name and click on Save.
- Locate the script.bat file and double click it to run it.
Note: Some Windows 10 users reported that the ntoskrnl.exe BSOD errors occur mainly when they enabled BlueStacks and other Android emulators.
So, if you installed emulators on your computer, disable or completely uninstall them.
6. Clean your registry
- Go to Start, then type CMD.
- Open Command Prompt (Admin).
- Type in the following command:
- Wait for the scanning process to complete.
- Then, restart your computer.
- All corrupted files will be replaced on reboot.
You can also use Microsoft’s System File Checker to check for system file corruption. The utility verifies the integrity of all protected system files and repairs files with problems when possible.
Note: Corrupted or missing registry keys may also cause BSOD errors. Don’t forget to first backup your registry in case anything goes wrong.
The simplest way to repair your registry is to use a dedicated tool for Windows.
7. Check your disk for errors
- Star Command Prompt (Admin).
- Type the following command and press Enter:
chkdsk C: /f
- Replace the C with the letter of your HDD.
- To command detects and repairs logical issues.
- To repair physical issues, type the following command:
chkdsk D: /r
- Let CMD run its course.
On Windows 10, you can run a disk check using Command Prompt. As a quick reminder, if you do not use the /f parameter, chkdsk displays a message that the file needs to be fixed, but it does not fix any errors.
On other Windows versions, go to hard drives and right-click the drive that you want to check.
8. Fix bad memory issues
- Go to Start and type Memory.
- Double-click on Windows Memory Diagnostic.
- Select the first option to restart your computer and check memory.
Note: Another common cause of ntoskrnl.exe BSOD errors is related to bad memory. Use Windows 10‘s built-in memory diagnostic tool to identify potential memory issues affecting your system.
9. Remove faulty sticks of RAM
Some Windows 10 users reported that the system_thread_exception_not_handled ntoskrnl.exe errors that they encountered were caused by a faulty stick of RAM.
So, if you recently changed the RAM configuration of your computer, check your RAM sticks to make sure that they’re properly inserted and are working as they should be.
We hope the solutions listed in this article helped you fix Windows 10 BSOD errors caused by ntoskrnl.exe. If you come across other solutions to fix this issue, let us know in the comments below.
Also, leave there any other suggestions or questions you may have and we’ll be sure to check them out.