KMODE_EXCEPTION_NOT_HANDLED (1e) BSOD persisting Despite Troubleshoots

franco salvadori 20 Reputation points
2026-06-07T11:11:21.9766667+00:00

Good afternoon,

I have been having quite a few issues with my system (a MSI GF63 laptop running Windows 11 (build 26100.8457)) BSODing at random moments whenever I do anything intensive with my PC (launching a game, etc). I have checked most of my drivers, updated my BIOS/Chipset Drivers/Video Drivers, ran sfc /scannow and other cmd promts and plenty more.

Symptoms:

The issue occurs both during normal desktop usage and while gaming. The system frequently becomes partially unresponsive:

  • The mouse cursor continues to move normally.
  • The keyboard becomes completely unresponsive.
  • Ctrl+Alt+Del does not work.
  • The taskbar may disappear or fail to load.
  • Explorer.exe, SearchHost.exe and other Windows components stop responding.
  • Applications often open as blank white windows and then freeze.
  • Sometimes the screen turns black temporarily before partially recovering.
  • Audio may continue to play while the system is frozen.
  • In several cases the issue eventually leads to a BSOD.

BSOD Information

Recent BSOD:

  • KMODE_EXCEPTION_NOT_HANDLED (0x1E)

Minidump analysis shows:

  • Exception code: 0xC0000006 (InPageError)
  • Failure Bucket: 0x1E_C0000006_nt!HvpGetCellPaged
  • Process Name: Registry

The crash appears to occur while Windows is accessing registry data.

Reliability Monitor Findings

Multiple applications and services crash around the same time when the issue occurs:

  • SearchHost.exe
  • CTF Loader (ctfmon.exe)
  • Host Process for Windows Tasks (taskhostw.exe)
  • NVIDIA Container
  • Diagnostic Policy Service
  • A-Volute NS

Many of these crashes report:

  • InPageError
  • Exception code 0xC0000006

Storage Investigation

I investigated possible SSD issues.

Tests performed:

  • CrystalDiskInfo → SSD health reported as GOOD.
  • CHKDSK C: /f /r → completed successfully.
  • No bad sectors found.
  • CHKDSK corrected a filesystem bitmap inconsistency.
  • After repair, the issue continued to occur.

Relevant Event Viewer entries observed previously:

  • Disk Event ID 51
  • NVMe reset events
  • RaidPort reset events

However, SSD SMART data currently reports no hardware failure.

Windows Integrity Checks

Executed successfully:

DISM /Online /Cleanup-Image /RestoreHealth

Result:

  • Restore operation completed successfully.

SFC /SCANNOW

Result:

  • Windows Resource Protection did not find any integrity violations.

Memory Investigation

Windows Memory Diagnostic was executed.

Result:

  • No memory errors detected.

RAM modules have been installed and functioning correctly for approximately two years prior to the issue.

Third-Party Software Potentially Involved

The system contains:

  • MSI Center
  • MSI NB Foundation Service
  • A-Volute / Nahimic components
  • Norton Security
  • NVIDIA drivers

The command FLTMC shows active Norton filesystem filter drivers:

  • nllSP
  • nllMonFlt
  • nllSnx

Reliability Monitor also shows repeated crashes involving:

  • A-Volute NS
  • NVIDIA Container

The system remains unstable despite CHKDSK, DISM, SFC, SSD health verification, and memory diagnostics.

I have attached my most recent minidump file, could anyone please help me find a solution to this issue? Thanks!

https://drive.google.com/file/d/1kzKb1pE4Wz2fZFKYe0YAg53ILJDtkyw0/view?usp=sharing

Here is the result of winDbg: https://drive.google.com/file/d/1BVDqnELsiNd2BGTcmblugELD-JZ9PGjm/view?usp=sharing

Windows for home | Windows 11 | Performance and system failures
0 comments
Answer accepted by question author
DaveM121 935.7K Reputation points Independent Advisor
2026-06-07T11:50:59.9766667+00:00

That one minidump file was inconclusive and just indicated generic errors, there was no indication of the underlying cause of that crash.

If this is an on-going problem, please upload all minidump files you may have for analysis.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-06-07T11:11:49.0966667+00:00

    The KMODE_EXCEPTION_NOT_HANDLED (0x1E) bug check indicates a kernel‑mode exception that was not handled. In the scenario described, the exception code 0xC0000006 (InPageError) and the failure bucket pointing to nt!HvpGetCellPaged show that the fault occurs when Windows is paging in registry data.

    From the documentation:

    • Bug check 0x1E occurs when a kernel‑mode program generates an exception that the error handler does not catch.
    • Parameter 1 is the exception code, parameter 2 is the address where the exception occurred, and parameters 3 and 4 are exception information parameters.
    • Common exception codes include 0xC0000005 (access violation), but in this case 0xC0000006 indicates an in‑page I/O error while accessing paged data.

    Given that:

    • The exception is raised while accessing registry data (HvpGetCellPaged).
    • There are repeated InPageError events and Disk / NVMe / RaidPort reset events.
    • Multiple system processes (SearchHost, ctfmon, taskhostw, NVIDIA Container, A‑Volute NS, etc.) fail with 0xC0000006 around the same time.
    • SFC and DISM complete successfully and report no integrity violations.
    • Memory diagnostics and SMART/CHKDSK do not show clear hardware failure.

    The pattern is consistent with intermittent I/O failures at the storage or driver level that surface as in‑page errors when the kernel attempts to read paged registry or system data. For bug check 0x1E, the official guidance is:

    1. Identify the exception code and the address where the exception occurred (parameters 1 and 2) to locate the driver or function involved.
    2. If a driver is identified in the bug check message, disable or remove that driver, or obtain an updated version.
    3. Consider hardware causes such as BIOS incompatibilities, memory conflicts, or IRQ conflicts.
    4. Use Event Viewer’s System log to correlate additional errors that may identify the device or driver causing the bug check.
    5. If the specific cause is unknown, obtain a stack trace in the debugger and analyze the exception and context records to see the call stack at the point of the unhandled exception.

    For 0x1E specifically, the documentation also notes:

    • A faulty device driver or system service can cause this error.
    • Hardware issues (including BIOS incompatibilities) can also generate this error.
    • If the error occurs during startup, Safe Mode can be used to disable or remove problematic drivers.

    In this case, next steps aligned with the documentation are:

    1. Use the bug check parameters to confirm the exception code and the faulting address, and map that address to the module (driver) involved.
    2. If the stack or parameters implicate a third‑party driver (for example, storage, filter, or security software), disable or remove that driver and test stability.
    3. Continue to monitor the System log for Disk, NVMe, or storage‑related errors that coincide with the 0xC0000006 InPageError events.
    4. If the cause remains unknown, use the debugger procedure described for 0x1E to obtain a stack trace based on the exception and context records and identify the calling stack where the unhandled exception occurred.

    These steps follow the official guidance for diagnosing and resolving KMODE_EXCEPTION_NOT_HANDLED (0x1E) with storage‑related exception codes.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.