Share via

KMODE_EXCEPTION_NOT_HANDLED and NETIO.SYS. What are these?

Paolo Eduardo 0 Reputation points
2026-04-03T17:02:26.6966667+00:00

My laptop crashes and the return it says on Windbg is KMODE_EXCEPTION_NOT_HANDLED.I have posted here before about BSODs and this is a new one. before, DPC_WATCHDOG_VIOLATION and CLOCK_WATCHDOG_TIMEOUTS were the return errors but it somehow fixed itself or rather it stopped because I got it cleaned. one dude tried to help me but it still didn't fix my computer. I recently cleaned the hardware as stated earlier because I thought it might be the culprit but the crashes seldom happen. I also have done numerous fixes like updating BIOS, updating the drivers through Windows update and manually, reseating RAM, reseating SSD but to no avail. Can anyone help me? it would be much appreciated. here are the dump files for a clearer view.

Windows for home | Windows 11 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ivan B 106.5K Reputation points Independent Advisor
    2026-04-03T18:12:25.4766667+00:00

    Hi ,

    What is the laptop model? If possible, access Msinfo32.exe in the search bar, take a screenshot and post it here?

    If possible, upload the minidumps to OneDrive or Google Drive and share the link here.

    There's a very high probability that it's a hardware issue.

    Thanks

  2. Q&A Assist
    2026-04-03T17:02:44.3266667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    KMODE_EXCEPTION_NOT_HANDLED is a Windows bug check (blue screen) with value 0x0000001E. It means a kernel‑mode component (driver or system code) raised an exception that was not handled by the kernel’s error handler.

    The parameters of this bug check are:

    1. Exception code that was not handled (for example STATUS_ACCESS_VIOLATION 0xC0000005, STATUS_BREAKPOINT 0x80000003, etc.).
    2. Address where the exception occurred (usually inside a driver or ntoskrnl). 3–4. Additional exception information from the exception record.

    NETIO.SYS is a core Windows networking driver (part of the network I/O subsystem). If NETIO.SYS appears in the crash stack or as the faulting module together with KMODE_EXCEPTION_NOT_HANDLED, it usually means a kernel‑mode networking component misbehaved. Common causes include:

    • Faulty or outdated network adapter drivers.
    • Third‑party firewall, VPN, or security software that installs filter drivers on the network stack.
    • Other kernel drivers that interact with networking.

    General guidance for KMODE_EXCEPTION_NOT_HANDLED:

    • If a specific driver name is shown in the bug check message or in WinDbg, disable, remove, or update that driver.
    • Check Event Viewer → System log for related driver or hardware errors around the crash time.
    • Verify hardware and BIOS compatibility with the installed Windows version and update BIOS/firmware if needed.
    • Run hardware diagnostics, especially memory tests, as faulty RAM or other hardware can also cause unhandled kernel exceptions.

    For deeper debugging in WinDbg, the exception code (parameter 1) and exception address (parameter 2) help identify the failing driver or function. If normal stack tracing is difficult, the documented procedure uses commands like kb, .exr, and .cxr to reconstruct the call stack and see where the unhandled exception occurred.

    If the crashes are tied to networking activity (browsing, downloads, VPN use) and NETIO.SYS is consistently present in the stack, focus on:

    • Updating or temporarily uninstalling third‑party firewall/VPN/antivirus.
    • Updating the network adapter driver from the laptop or NIC vendor.
    • Testing stability with only the built‑in Windows Defender Firewall and no third‑party network filters.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.