How To Fix Ndu.sys Blue Screen Error On Windows

Ndu.sys is the Windows Network Information Utilization Monitoring Driver. For those who test the What Failed part for numerous bugchecks like SYSTEM THREAD EXCEPTION NOT HANDLED and IRQL NOT LESS EQUAL, you’ll usually discover ndu.sys listed there.

Nonetheless, opposite to what customers usually imagine, this doesn’t imply that ndu.sys brought about the BSOD. As a substitute, this driver failed due to one thing else, and that’s what you’ll want to determine to repair the ndu.sys BSOD at its root.

Methods to Repair Ndu.sys BSOD Error

As said, there are numerous BSODs associated to ndu.sys, with some widespread ones being:

0x0000000A: IRQL NOT LESS EQUAL (Ndu.sys)
0x0000001E: KMODE EXCEPTION NOT HANDLED (Ndu.sys)
0x0000003B: SYSTEM SERVICE EXCEPTION (Ndu.sys)
0x00000050: PAGE FAULT IN A NONPAGED AREA (Ndu.sys)
0×0000007A: KERNEL DATA INPAGE ERROR (Ndu.sys)
0x0000007E: SYSTEM THREAD EXCEPTION NOT HANDLED (Ndu.sys)

These BSODs will be attributable to quite a few causes, however when related to ndu.sys, sure fixes will likely be very efficient. We’ve listed these first, and if these fixes don’t assist, you’ll be able to analyze the dump file to determine the precise trigger and apply any of the final options listed additional under.

Take away Antivirus

The most typical cause for ndu.sys-related BSODs has been incompatibility with antiviruses. Malwarebytes, particularly, is infamous for this. As such, briefly eradicating the antivirus is likely to be your best wager at fixing this BSOD. 

You should use Windows Defender for cover within the meantime. With that mentioned, right here’s how one can take away the antivirus:

1. Press Win + R, kind appwiz.cpl, and press Enter.
2. Choose the antivirus from the listing and press Uninstall.
3. Comply with the on-screen directions to take away the antivirus and restart afterward.

Update Network Driver

Outdated or corrupt network drivers are one other widespread cause for ndu.sys-related BSODs. It is best to first attempt updating the network drivers. Right here’s how you are able to do so:

1. Press Win + R, kind devmgmt.msc, and press Enter.
2. Broaden the Network Adapters part.
3. Proper-click the Network Adapter and choose Update Driver.
   
4. First, choose Search routinely for up to date drivers.
5. For those who’re unable to search out newer drivers that method, search for the drivers on the system producer or network adapter producer’s web site.
6. Obtain whichever one is newer.
7. Launch the Gadget Supervisor and attempt to update the network driver as soon as once more.
8. This time, choose Browse my pc for drivers.
   
9. Click on on Browse and find the listing the place the driving force information had been downloaded in Step 6.
   
10. Press Okay > Subsequent > Shut.
11. Restart your pc afterward.

Substitute ndu.sys

It’s additionally potential that the ndu.sys file itself is corrupt, and changing it with a correct one may resolve the BSOD points. For those who lately upgraded Windows, you’ll have the Windows.outdated folder in your system. You should use the ndu.sys file from that listing to switch the present one. Right here’s how you are able to do this:

1. First, create a restore level as a security measure.
2. On an admin account, press Win + R, kind cmd, and press CTRL + Shift + Enter.
3. Execute the next instructions to take possession of the present file and rename it:
   takeown /f %WinDirpercentSystem32driversndu.sys
icacls %WinDirpercentSystem32driversndu.sys /Grant Directors:f
ren "%WinDirpercentSystem32driversndu.sys" "ndu.outdated"
4. Now, execute the next instructions to switch the file:
   copy C:windows.oldsystem32driversndu.sys  C:windowssystem32drivers

If the Windows.outdated methodology isn’t relevant to you, you’ll be able to as a substitute get the ndu.sys file from an set up media and substitute it in the identical method. Listed here are the steps for this:

1. Insert the set up media and reboot your pc.
2. Press the Boot Choices key proven on the display screen (often F12) and choose the media besides from it.
3. Within the set up wizard, click on on Restore your pc.
   
4. Choose Troubleshoot > Superior Choices > Command Immediate.
5. Enter the next instructions and notice the system drive letter:
   Diskpart
Checklist vol
   
6. Enter exit.
7. Sort the next command:
   copy X:windowssystem32driversndu.sys  C:windowssystem32drivers
   
8. Substitute C: with the system drive letter from Step 5 if completely different, and press Enter to switch the ndu.sys file.
9. On older programs, the earlier command could not work. In such instances, do that one as a substitute:
   copy X:sourceswindowssystem32driversndu.sys  C:windowssystem32drivers
10. Restart your system and take away the set up media besides usually.

Analyze Dump File

The earlier fixes will resolve the BSOD for many customers, but when they persist, you must analyze the dump information generated by the bugcheck to get a greater thought of what precisely is inflicting it. Afterward, you’ll be able to apply the suitable answer from those listed additional under. Right here’s how one can analyze the dump information:

1. Set up the WinDbg Preview App from the Microsoft Retailer.
2. Launch the app and press CTRL + D.
3. Navigate to %windir% or %windir%/minidump/ and open the dump file.
   
4. Choose View > Command and enter !analyze -v on the kd immediate.
   
5. After finishing the evaluation, test the MODULE_NAME and In all probability attributable to sections for hints on what brought about the crash.
6. If there are a number of dump information, analyze the remainder in the identical method to get more data.

If vital, you may additionally use further strategies to collect data, like checking the Occasion Viewer logs and utilizing Driver Verifier.

Restore System Corruption

We changed the ndu.sys file earlier, however there may be different corrupt system information which can be inflicting this driver to fail. As such, we advocate utilizing the native DISM and SFC utilities to restore system corruption. Right here’s how you are able to do this:

1. Press Win + R, kind cmd, and press CTRL + Shift + Enter.
2. Execute the next instructions:
   dism /on-line /cleanup-image /restorehealth
sfc /scannow
   

Use Diagnostic Instruments

Reminiscence and disk issues are a typical cause for BSODs. As such, utilizing in-built instruments to diagnose any potential points with them is a good suggestion. First, we advocate utilizing CHKDSK with the steps proven under:

1. Press Win + R, kind cmd, and press CTRL + Shift + Enter.
2. Sort chkdsk c: /f /r, substitute c: together with your system drive letter if completely different, and press Enter.
   
3. Settle for the immediate to run the disk scan upon restarting, and restart your PC afterward.
4. If no disk points are discovered, use the mdsched run command and use the Windows Reminiscence Diagnostic instrument to test the reminiscence as a substitute.

Clear Boot

We’ve already talked about eradicating antiviruses, however different third-party applications may be interfering with the ndu.sys driver or different system parts and inflicting this BSOD. As such, performing a clear boot could possibly be useful. Right here’s how you are able to do this:

1. Press Win + R, kind msconfig, and press Enter.
2. Within the Companies tab, allow the Hide all Microsoft companies possibility.
   
3. Click on on Disable all and press OK.
4. Within the Startup tab, click on on Open Activity Supervisor.
5. Disable all of the functions and restart your pc.
   
6. For those who don’t get the BSOD like this, one of many applications or companies would be the offender. Allow them one after the other to determine which one.
7. For those who do get the BSOD, the issue is probably going one thing else. Comply with the identical steps to revert the clear boot configurations.

Update Windows

Windows Updates usually embrace patches to minor points with system parts, together with drivers like ndu.sys. As such, we advocate updating your system with the steps listed under:

1. Press Win + R, kind management update, and press Enter.
2. Click on on Examine for Updates, then obtain and set up any pending ones.
3. Restart your PC afterward.

Use System Restore

You probably have a system restore level from a time earlier than the BSOD began, it’s very seemingly that restoring your system to that time may do away with the BSODs as properly. Right here’s how you should use system restore in such instances:

1. Press Win + R, kind rstrui, and press Enter.
2. Press Subsequent and choose the restore level to make use of.
   
3. Settle for the affirmation prompts and press End.
4. After 30 – 60 minutes, the system restore ought to end, and also you’ll obtain a completion message.