Windows 10: [BUG CHECK] KMODE_EXCEPTION_NOT_HANDLED 1e

Getting some BSODs, trying to pin point what my problem is.





Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021020-6187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP 12 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff802`7a89e000 PsLoadedModuleList = 0xfffff802`7acb7710
Debug session time: Mon Feb 10 15:23:06.975 2020 UTC - 5:00
System Uptime: 0 days 0:33:22.692
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED 1e
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8027a998604, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7B84

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 2.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3.10

BIOS_DATE: 01/30/2019

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: A320M PRO-M2 V2 MS-7B84

BASEBOARD_VERSION: 2.0

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027a998604

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff8027ad63540
fffff8027adde390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

EXCEPTION_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!KiTryUnwaitThread+1a4
fffff802`7a998604 f0480fbaae1059000000 lock bts qword ptr [rsi+5910h],0

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: c

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXPNP: 1 !blackboxpnp


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Corsair.Service.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-VP6C47J

ANALYSIS_SESSION_TIME: 02-10-2020 15:39:43.0933

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

DPC_STACK_BASE: FFFFF20364684FB0

EXCEPTION_RECORD: ffff9286ac8b7080 -- .exr 0xffff9286ac8b7080
ExceptionAddress: ffff9286ac8b7088
ExceptionCode: 00200006
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff8027a804a70 -- .trap 0xfffff8027a804a70
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=cccccccccccccccc rsp=cccccccccccccccc rbp=e083104233e8d36c
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=3 nv up di ng nz ac pe nc
70ba:cccccccc`cccccccc ?? ???
Resetting default scope

BAD_STACK_POINTER: cccccccccccccccc

LAST_CONTROL_TRANSFER: from fffff8027ab29d2e to fffff8027aa54980

STACK_TEXT:
fffff203`646839c8 fffff802`7ab29d2e : 00000000`0000001e ffffffff`c0000005 fffff802`7a998604 00000000`00000000 : nt!KeBugCheckEx
fffff203`646839d0 fffff802`7aa5d492 : fffff802`7ad7f000 fffff802`7a89e000 0005b98c`00a6e000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff203`64683a10 fffff802`7a9c3b00 : fffff203`64684060 00000000`00000000 fffff203`64683f80 00000000`00000000 : nt!RtlpExecuteHandlerForException+0x12
fffff203`64683a40 fffff802`7a8de334 : fffff203`64684978 fffff203`646846c0 fffff203`64684978 ffffa481`37c80180 : nt!RtlDispatchException+0x430
fffff203`64684190 fffff802`7aa662c2 : ffff9286`ac8b7080 00000000`00000a7f fffff802`7a804a70 fffff802`7a8017ae : nt!KiDispatchException+0x144
fffff203`64684840 fffff802`7aa6214b : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 fffff802`846e48ef : nt!KiExceptionDispatch+0xc2
fffff203`64684a20 fffff802`7a998604 : ffff9286`ae7d01a0 fffff802`79a6d800 ffffa481`37c80180 fffff780`00000320 : nt!KiGeneralProtectionFault+0x30b
fffff203`64684bb0 fffff802`7a98adac : ffff9286`b549a1c0 fffff203`00000000 ffff9286`b5c79200 00000000`00000009 : nt!KiTryUnwaitThread+0x1a4
fffff203`64684c10 fffff802`7a98a945 : ffff9286`b5c79200 00000000`00000000 fffff203`64684e68 fffff802`7a95a009 : nt!KiTimerWaitTest+0x1cc
fffff203`64684cb0 fffff802`7a98b937 : 00000000`0000000a 00000000`00989680 ffff9286`b5c792c0 00000000`00000019 : nt!KiProcessExpiredTimerList+0xb5
fffff203`64684da0 fffff802`7aa5b805 : 8b486500`00086086 ffffa481`37c80180 fffff203`66e03b80 ffff9286`ac8c1f00 : nt!KiRetireDpcList+0x4a7
fffff203`64684fb0 fffff802`7aa5b5f0 : fffff802`7a819cc0 fffff802`7a802af5 ffff9286`b5c792c0 ffffffff`f4143e00 : nt!KxRetireDpcList+0x5
fffff203`66e03ac0 fffff802`7aa5aeb5 : 00000000`018cfbec fffff802`7aa56951 00000000`017bda14 fffff203`66e03b80 : nt!KiDispatchInterruptContinue
fffff203`66e03af0 fffff802`7aa56951 : 00000000`017bda14 fffff203`66e03b80 ffff9286`ac8c1f00 ffff9286`b5f837e0 : nt!KiDpcInterruptBypass+0x25
fffff203`66e03b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1


THREAD_SHA1_HASH_MOD_FUNC: 455d7d4b3a0226cb6ac3dd93a74fc25dd8cc07be

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f7b11fac729f371494157458cfb3e03d39f69fdc

THREAD_SHA1_HASH_MOD: 38bc5fec3f0409c265cf5c87da6f8f8859d0711c

FOLLOWUP_IP:
nt!KiTryUnwaitThread+1a4
fffff802`7a998604 f0480fbaae1059000000 lock bts qword ptr [rsi+5910h],0

FAULT_INSTR_CODE: ba0f48f0

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nt!KiTryUnwaitThread+1a4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 11b35b7e

IMAGE_VERSION: 10.0.17763.973

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1a4

FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_nt!KiTryUnwaitThread

BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_nt!KiTryUnwaitThread

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_STACKPTR_ERROR_nt!KiTryUnwaitThread

TARGET_TIME: 2020-02-10T20:23:06.000Z

OSBUILD: 17763

OSSERVICEPACK: 973

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1979-05-30 22:50:38

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: a127

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_stackptr_error_nt!kitryunwaitthread

FAILURE_ID_HASH: {572d8862-52b1-d972-69fd-468443a7c315}

Followup: MachineOwner
---------

:)

 

Windows 10 KMODE_EXCEPTION_NOT_HANDLED blue screen, happens daily.

Hi,

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

I suggest you to refer the link suggested by
Andre Da Costa which is marked as answered and follow the steps suggested. Do let us know if you still get Blue screen error. Thank you.

 

KMODE_EXCEPTION_NOT_HANDLED BSOD while loading games.

Hi Sterling,

I appreciate the troubleshooting steps you have tried to resolve the issue. I suggest you to update mouse drivers and check.

In addition to this I would suggest you to refer to the troubleshooting steps suggested by
Babu V in the link below and check if it helps:

How to troubleshoot blue screen errors in Windows 10


For more information regarding this error code, you can refer to the link below:

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Do let us know the status of the issue. Thank you.

 

Kmode_exception_not_handled BSOD in Windows 10

Hi Lucas,



Thank you for posting your query in Microsoft Community. I regret the inconvenience caused to you. Let me help you.

• 
  When did the BSOD screen appeared?
  
• 
  Have you made any changes in settings or installed any third party software prior to the issue?
  

I would suggest you to refer to the troubleshooting steps suggested by
Babu V in the link below and check if it helps:

How to troubleshoot blue screen
errors in Windows 10

For more information regarding this error code, you can refer to the link below:

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Check if it helps.



If you need any further assistance, please feel free to contact us again. We will be happy to assist you further.