Please share several memory minidumps to OneDrive for analysis.
How to fix Stop code: KMODE EXCEPTION NOT HANDLED
I work remotely and desperately need to be able to get work done today. The above came up three different times upon restarting my computer. I tried to go into safe mode as a work around. However, when I attempted to get into the Word document I had started yesterday and need to continue in it said something to the effect of Microsoft doesn't recognize your license for this. I have never had this issue before and need it resolved ASAP. Please advise accordingly.
Windows for home | Windows 10 | Performance and system failures
3 answers
Sort by: Most helpful
-
Igor Leyko 110.8K Reputation points Independent Advisor
2026-05-16T17:19:53.4466667+00:00 -
Igor Leyko 110.8K Reputation points Independent Advisor
2026-05-16T16:57:57.5366667+00:00 {duplicate]
-
Q&A Assist2026-05-16T15:28:53.92+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreKMODE_EXCEPTION_NOT_HANDLED (stop code 0x0000001E) indicates that a kernel‑mode program generated an exception that wasn’t handled. This is typically caused by a faulty or incompatible driver, system service, or (less commonly) hardware/BIOS issues.
To get the PC stable enough to work and then address the root cause, follow these steps:
- Stabilize the system (Safe Mode and basic checks)
- Boot into Advanced startup
- If Windows still boots intermittently: Go to Settings > Update & Security > Recovery and under Advanced startup select Restart now.
- If Windows does not boot reliably: Power on the PC and interrupt startup (hold power to force off) 2–3 times until Preparing Automatic Repair or Advanced options appears, then go to Advanced options.
- Enter Safe Mode
- In Choose an option, select Troubleshoot > Advanced options > Startup Settings > Restart.
- After restart, press 4 (Enable Safe Mode) or 5 (Safe Mode with Networking).
If the blue screen does not appear in Safe Mode, that strongly points to a driver or service rather than core hardware.
- Address the KMODE_EXCEPTION_NOT_HANDLED stop error
According to the stop‑error guidance:
- This error is often caused by a faulty device driver or system service.
- If a driver is named on the blue screen, that driver should be disabled or removed.
- Remove or disable recently added drivers/services
- In Safe Mode, open Device Manager.
- Uninstall or disable any drivers that were recently installed or updated (for example, display, network, USB, storage, or any vendor‑specific drivers that appeared around the time the crashes started).
- Also uninstall any recently installed hardware‑management or tuning utilities that install kernel services.
- Use Safe Mode to disable a specific driver (if one is named) If the blue screen shows a specific driver file name and the system drive is NTFS, use Safe Mode to disable it:
- Boot to Safe Mode as above.
- In Device Manager, locate the device that uses that driver and Disable or Uninstall device.
- Check for hardware/BIOS issues
- If new hardware was added recently, temporarily remove or disconnect it and test.
- Run the hardware diagnostics provided by the PC or motherboard manufacturer, especially memory tests.
- If the error began after a BIOS/firmware change, check the vendor’s site for an updated or rolled‑back BIOS that is compatible with the installed Windows version.
- If the cause is a USB 3.0 driver on Windows 8.1/Server 2012 R2
If this is Windows 8.1/Windows Server 2012 R2 and the crashes occur when using USB 3.0 devices with drivers that use static streams (and the stop code text matches the documented USB 3.0 scenario), install the update rollup that fixes a known issue where a driver incorrectly closes static streams when destroying the endpoint object. The documented resolution is to install update rollup 2887595 for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2.
- Get Word/Office working once Windows is stable
Once the system is booting reliably (normal mode or Safe Mode with Networking), address the Word licensing/launch issue so work can continue.
- Try an Online Repair of Microsoft 365/Office
- Open Settings > Apps.
- Find Microsoft Office or Microsoft 365 Apps in the list.
- Select it and choose Modify.
- Choose Online Repair and let it complete. This repairs the Office installation and often resolves issues where apps crash or report licensing/activation errors.
- If Online Repair does not work
- Completely uninstall Office from Settings > Apps.
- Restart the PC (full restart, not shutdown).
- Reinstall Office from the Microsoft account or organization portal used for the subscription.
- If the error is specifically “Word has run into an error that is preventing it from working correctly”
- Use the Online Repair method above first.
- If that fails, uninstall, restart, and reinstall Office as described.
- If Office reports that the license is not recognized
- After repair/reinstall, sign out of Office apps, then sign back in with the correct work or school account that holds the subscription.
- If multiple identities (personal + work/school) are used, sign out of all Office apps and Windows account connections, then sign back in with the work account first to ensure activation uses the correct license.
- If blue screens continue
If KMODE_EXCEPTION_NOT_HANDLED continues after driver removal and hardware checks:
- Collect the stop code details (including any driver name and parameters) and use the debugging guidance to identify the exception code and the address where it occurred.
- For deeper analysis, a developer or support engineer can use a kernel debugger and the bug‑check parameters to obtain a stack trace and pinpoint the failing driver or function.
References:
- Bug check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
- Advanced troubleshooting for stop code errors
- "KMODE_EXCEPTION_NOT_HANDLED" Stop error when a driver tries to close static streams for USB 3.0 devices in Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2
- I get a "stopped working" error when I start Office applications on my PC
- we are sorry, but word has run into an error that is preventing it from working correctly. Word will need to be closed as a result. Would you like us to repair now? - Microsoft Q&A
- How can I get office 365 to work? - Microsoft Q&A