How to Fix Blue Screen Error RNDISMP6.SYS on Windows

The RNDISMP6.SYS is a system file and you may locate this file inside the folder – C:\Windows\System32\drivers on Windows 11/10. Several users reported encountering a Blue Screen Error displaying RNDISMP6.SYS under what failed in the error description. 

This is quite evident from the error description that the RNDISMP6.SYS is a very important system file and your operating system can’t function properly in its absence. So, our prime task is to prevent the reasons causing this system file to fail. Let’s explore the reasons causing this blue screen error and the relevant fixes that might solve this problem. 

Fix Blue Screen Error RNDISMP6.SYS

What causes this BSOD Error RNDISMP6.SYS?

If you look closely into the error message, it reads “Stop Code: DRIVER_IRQL_NOT_LESS_OR_EQUAL” along with “what failed: RNDISMP6.SYS”. There must have occurred some issues causing this system file to fail out of nowhere. 

RNDISMP6.SYS failed BSOD Error

One may encounter this error while starting your Windows OS or while working on some application(s). This suggests that some important drivers must have failed to start or have crashed all of a sudden. In short, this is a driver-related issue and you should focus on correcting all your device drivers. If you have recently updated some drivers on your PC, this error must be the result of the recent installation(s). 

Apart from this, the RNDISMP6.SYS failed BSOD Error might also occur due to a corrupted Windows registry, missing or damaged system files, or corruption within the System Image. Last but not the least, this error may also appear when your hard disk has been corrupted somehow. 

Ways to Solve BSOD Error RNDISMP6.SYS

To solve this Blue Screen Error RNDISMP6.SYS, boot into Safe Mode with Networking, and then attempt the below fixes. Booting into the Safe mode is required as you can’t apply any fix without getting past this blue screen. The essential solutions that might resolve this error code are as follows –

1] Uninstall Faulty Device Drivers

If this RNDISMP6.SYS error had started occurring after installing some network drivers, make sure to roll back those drivers. Here’s how to perform this task –

Note: DriverFix is a premium tool that is developed to automatically find and resolve such driver-related errors on Windows PC. If you don’t want to apply these advanced fixes, we recommend purchasing this tool. 

Case:1 When you are able to Boot into the Safe Mode

If you are able to boot into your device in Safe Mode, use these steps instead –

  • Open Device Manager, and locate the recently installed device drivers.
  • Right-click on the problematic driver, and select Properties.
  • Go to the Driver tab, and click Roll back driver.
  • Click OK to confirm the rollbacking of your faulty device driver. 

After you remove the recently installed drivers, restart your PC and check if the BSOD error resolves this way. 

Case:2 If you can’t boot into the Safe Mode

You may perform this task by using a Windows Installation media and booting into the Recovery Environment. Insert the bootable media into one of your system’s ports, and restart your device.

  • On the WinRe screen, click Repair your computer
  • Go to Troubleshoot, and select Advanced options.
  • Select Command Prompt and when this opens up, run the below code on it. 

Dism /image:C:\ /Get-Drivers

  • You will see a list of drivers installed on your computer. 
  • Locate the network driver that you have installed recently and note down its Published name. You may identify the problematic network adapter by looking into its Original File Name and Provider Name.

Note: Third-party drivers usually have names like oem0.inf, oem1.inf, etc. The digit present at the end of the Published name basically denotes the installation order of a driver. 

  • If you are sure which driver to uninstall, run the below code on the elevated console – 

DISM /Image:C:\ /Remove-Driver /Driver:oem1.inf

Make sure to change the digit if the same differs in your case. 

  • When this command runs successfully, you will see the following message. 

Found 1 driver package (s) to remove.
Removing 1 of 1 – oem1.inf: The driver package was successfully removed.
The operation completed successfully.

  • Restart your Windows and check if Windows starts correctly without the faulty driver.

2] Repair the corrupt Windows Registry

The RNDISMP6.SYS failed BSOD Error might also occur on account of some corruption inside the windows registry. Take a look and perform as guided below to repair the corrupted registry on your Windows PC –

  • Assuming you are inside the Safe Mode, press Win + X, and choose Terminal (Admin).
  • When the terminal launches, run the below command on it –

sc.exe config netsetupsvc start=disabled

  • The above code will disable the Network Setup Service on your Windows PC. 
  • Copy/paste the below script on the terminal and press Enter

$ErrorActionPreference = 'SilentlyContinue'
$path = Get-ChildItem -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}' | Get-ItemProperty | Where-Object { $_.DriverDesc -like "*NDIS*" } | Select-Object -ExpandProperty PSPath
New-ItemProperty -Name *IfType -Value 6 -LiteralPath $path -Force
New-ItemProperty -Name *MediaType -Value 0 -LiteralPath $path -Force
New-ItemProperty -Name *PhysicalMediaType -Value 14 -LiteralPath $path -Force

Repair the corrupt Windows Registry

  • Wait for this script to run successfully. Once you see the blinking cursor, re-enable the Network Setup Service. You may use the below command to perform this task –

sc.exe config netsetupsvc start=demand

  • Restart your PC next and when it does reload, check if the RNDISMP6.SYS failing error resolves. 

3] Run SFC/DISM Scans

SFC and DISM scans are two useful command tools that can repair missing or damaged system files, folders, and the System Image. Follow the below instructions to run both of these tools on your Windows 11/10 PC –

  • Press Win + X, and choose Terminal (Admin). 
  • When the terminal starts, execute the below commands separately on it.
  • Only when the SFC scan completes, run the DISM command on your Windows PC. 

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

SFC and DISM Tools on Windows 11 Terminal

  • Both these tools will take 15-20 minutes to find and repair corruption within your system files, folders, and the System Image. 
  • While you are at the CMD screen, you may de-register all DLL files by running this code –

for %i in (%windir%\\system32\\*.dll) do regsvr32.exe /s %i

  • After this command runs successfully as well, restart your PC. 
  • Try booting into your device normally and check if the blue screen resolves this way. 

Note: If you aren’t able to boot into the Safe boot, go to the Automatic Repair screen, and launch CMD from here. You will access Command Prompt by navigating to the below path.

Troubleshoot > Advanced Options > Command Prompt

4] Check your hard disk using CHKDSK

The Blue Screen error might also occur due to the presence of bad or outdated sectors on your hard drive. Check for the same using CHKDSK. If you are able to boot into the Safe Mode on your Windows, launch CMD as administrator and run the below command on it –

chkdsk C: /f /r

CHKDSK Windows 11

However, if the Safe boot is also not opening, power On/Off your device 2-3 times using the Power button. Your device will boot into the Automatic Repair screen next. Go to Troubleshoot > Advanced Options, and select Command Prompt.

Command Prompt

When the CMD launches, execute the CHKDSK command on it. Wait for this code to run successfully and once this is over, you will get a report stating whether your hard disk is alright for use or not. In case you find any issues with your HDD, replace it with a new one. 

5] Use the Restore Point

If none of the above fixes work to resolve this Blue Screen Error RNDISMP6.SYS, revert your PC back to an earlier stable point. For this, you require a restore point that has been taken sometime back when your device was functioning pretty well. In case you haven’t enabled the System Protection on your PC, you may skip this solution, and rather perform a clean installation of Windows 11. 

Assuming you do have a system backup on your computer, follow these steps to restore your operating system to its previous working state –

  • Power On and Off your device multiple times using the Power button. 
  • Doing so will open the Automatic Repair Screen. 
  • Go to Troubleshoot > Advanced Options, and click System Restore.

Use System Restore on Blue Screen

  • The system will prompt you to select a restore point. Well, do so and follow the on-screen instructions. 
  • Once you start this process, don’t cancel this ongoing task as this will corrupt your entire Windows OS. 

This System Restoration is a time taking process, so wait until this completes. Hopefully, the system will revert back to an earlier build where this BSOD Error RNDISMP6.SYS was not appearing. 

I hope this guide indeed helps you to solve the Blue Screen Error RNDISMP6.SYS on your Windows 11/10 PC. Let’s know in the comment section if you face any difficulty following the aforementioned solutions. 

How do I fix the Ndis.sys Blue Screen error in Windows?

If you are encountering a blue screen of death error displaying Ndis.sys under What failed, you may apply the same fixes as outlined in this post. As we all know, a BSOD error mostly occurs due to some driver issues, it is important to find and update the outdated system drivers on Windows. 

In case the error appears even after updating all device drivers, we suggest applying the below fixes – 

  • Run System File Checker to find and repair missing or damaged system files/folders. 
  • Run DISM to resolve file corruption within the System Image. 
  • Reset Update Components so that all update services come back to their default settings. 
  • Inspect for bad sectors on your HDD using CHKDSK.

Tip: If you are facing update, activation, or driver issues on your Windows PC, try RESTORO PC Repair Tool. This software will scan your device for potential issues and resolve them automatically.

Leave a Reply