How to Fix ndis.sys Blue Screen Errors in Windows 10/11
The ndis.sys file is a critical system driver in Windows responsible for managing network interface communication between your hardware and the operating system. When this file encounters issues, it can trigger a Blue Screen of Death (BSOD), often with error codes like CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, or IRQL_NOT_LESS_OR_EQUAL. This guide will help you diagnose and resolve these errors effectively.
Why Does ndis.sys Cause BSODs?
The ndis.sys driver can fail due to:
- Corrupted or outdated network drivers: Outdated, incompatible, or corrupted drivers (e.g., Wi-Fi, Ethernet) are the most common culprits.
- Hardware conflicts: Faulty network adapters, overclocked components, or faulty RAM can trigger instability.
- Malware or system corruption: Viruses or corrupted system files (e.g., from improper shutdowns) may affect the driver.
- Windows updates: A recent update might introduce bugs affecting network functionality.
- Driver conflicts: Conflicts between third-party drivers (e.g., VPN, antivirus) and Windows components.
Step-by-Step Fixes for ndis.sys BSODs
1. Update or Reinstall Network Drivers
Outdated or corrupted drivers are a leading cause of ndis.sys-related crashes.
- Uninstall current drivers:
- Press Win + X, then select Device Manager.
- Expand Network adapters, right-click your network card, and choose Uninstall device.
- Check the box for Delete the driver software for this device and confirm.
- Download the latest drivers:
- Visit your laptop/PC manufacturers support page (e.g., Dell, HP) or the chipset manufacturers site (Intel, Realtek).
- Manually install the driver or use Windows Update to search for updates.
2. Run System File Checker (SFC) and DISM
Corrupted system files can trigger BSODs. Use these built-in tools to repair them:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow- Open Command Prompt as Administrator (search for “cmd,” right-click, and select Run as administrator).
- Paste the first command above and press Enter. Wait for completion.
- Run the second command (
sfc /scannow) and restart your PC after it finishes.
3. Check for Disk Errors with CHKDSK
If file system corruption is suspected, run:chkdsk C: /f /r
- Open Command Prompt (Admin).
- Paste the command above and press Enter. If prompted to schedule a scan on next reboot, confirm.
- Restart your PC to complete the scan.
4. Roll Back or Disable Problematic Drivers
If the BSOD started after a driver update:
- Open Device Manager, expand Network adapters, right-click your card, and select Properties.
- Go to the Driver tab, click Roll Back Driver if available.
- If no rollback option exists, note the driver version and reinstall a stable version from the manufacturers site.
5. Test for Hardware Issues
Faulty RAM or overheating can cause intermittent crashes:
- Test RAM: Use Windows Memory Diagnostic:
- Search for Windows Memory Diagnostics, run the tool, and follow prompts.
- Check overheating: Monitor CPU/GPU temps using tools like MSI Afterburner. Ensure cooling fans are functional.
6. Disable or Update Antivirus Temporarily
Some security software (e.g., McAfee, Norton) may conflict with ndis.sys:
- Uninstall third-party antivirus via Settings > Apps > Installed apps.
- Use Windows Defender temporarily to test for BSOD recurrence.
7. Perform a Clean Boot
A clean boot starts Windows with minimal drivers/services, isolating the issue:
- Press Win + R, type
msconfig, and hit Enter. - Go to the Services tab, check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab, click Open Task Manager, disable all startup items, and restart.
- Test for BSODs. If none occur, re-enable services/apps one by one to identify the culprit.
8. Restore from a System Restore Point
If the issue started recently, restore Windows to a stable state:
- Search for Create a restore point, go to System Protection > System Restore.
- Choose a restore point from before the BSODs began and follow prompts.
9. Check for Windows Updates
Microsoft often patches driver issues in updates:
- Go to Settings > Update & Security > Windows Update, then click Check for updates.
- Install all optional and important updates, including driver firmware updates.
10. Reinstall or Reset Windows (Last Resort)
If all else fails, reset your PC while preserving files:
- Go to Settings > Update & Security > Recovery, then Reset this PC.
- Choose Keep my files and follow the prompts.
FAQ: Common Questions About ndis.sys BSODs
Q: Can I safely ignore a one-time ndis.sys BSOD?
A: No. A single occurrence may indicate a temporary glitch, but repeated crashes suggest deeper issues (e.g., hardware failure). Follow the steps above to resolve it.
Q: Will updating BIOS fix this?
A: Rarely, but if your motherboards firmware is outdated, check for a BIOS update on the manufacturers website. Proceed with cautionfollow their instructions carefully.
Q: Why does my Wi-Fi/Ethernet work fine sometimes?
A: Intermittent connectivity suggests hardware-level instability (e.g., loose cables) or driver conflicts. Test with a different cable/adapter to rule out physical issues.
Q: Can third-party tools like Driver Booster harm my system?
A: Some tools install unnecessary drivers, worsening conflicts. Use only official manufacturer drivers and avoid “driver update” software unless from trusted sources.
Q: How do I check the exact BSOD error code?
A: Note the error details on the blue screen (e.g., 0x000000D1). Search online for the code + “ndis.sys” to find targeted fixes.
Final Notes
If BSODs persist after trying these steps, consider hardware diagnostics (e.g., testing RAM with a known-good stick) or consulting a technician. ndis.sys-related crashes are often resolvable without data lossstart with driver updates and system file repairs before escalating to advanced solutions.
Last Updated: December 13, 2025
Tested on: Windows 10 (22H2) & Windows 11 (23H2)