Windows 10: KMODE_EXCEPTION_NOT_HANDLED (1e)

I often get BSOD ramdomly during boost and while using. I can't find a way to fix it.

*******************************************************************************

* *

* 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: fffff80118f0e354, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception



Debugging Details:

------------------





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 401



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.



SYSTEM_PRODUCT_NAME: H370HD3



SYSTEM_SKU: Default string



SYSTEM_VERSION: Default string



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: F1



BIOS_DATE: 02/23/2018



BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.



BASEBOARD_PRODUCT: H370 HD3-CF



BASEBOARD_VERSION: Default string



DUMP_TYPE: 1



BUGCHECK_P1: ffffffffc0000005



BUGCHECK_P2: fffff80118f0e354



BUGCHECK_P3: 0



BUGCHECK_P4: ffffffffffffffff



READ_ADDRESS: ffffffffffffffff



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



FAULTING_IP:

nt!ExpGetPoolTagInfoTarget+d4

fffff801`18f0e354 8b0a mov ecx,dword ptr [rdx]



EXCEPTION_PARAMETER2: ffffffffffffffff



BUGCHECK_STR: 0x1E_c0000005_R



CPU_COUNT: 6



CPU_MHZ: af8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXWINLOGON: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: DESKTOP-NPCV3



ANALYSIS_SESSION_TIME: 07-23-2019 19:49:59.0280



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



LAST_CONTROL_TRANSFER: from fffff801190a39ae to fffff80118fbc900



STACK_TEXT:

fffff385`e346e5b8 fffff801`190a39ae : 00000000`0000001e ffffffff`c0000005 fffff801`18f0e354 00000000`00000000 : nt!KeBugCheckEx

fffff385`e346e5c0 fffff801`18fc562f : fffff801`1930c000 fffff801`18e00000 0005e5a8`00ab2000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22

fffff385`e346e600 fffff801`18eca765 : 00000000`00000000 00000000`00000000 fffff385`e346eb70 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf

fffff385`e346e630 fffff801`18ececfe : fffff385`e346f568 fffff385`e346f2b0 fffff385`e346f568 fffff385`e57c2578 : nt!RtlDispatchException+0x4a5

fffff385`e346ed80 fffff801`18fce81d : 00000000`00000000 00001f80`00000200 00000000`00000103 00000000`00000000 : nt!KiDispatchException+0x16e

fffff385`e346f430 fffff801`18fca5a2 : ffffc202`1b451f70 ffffab01`74ec5f10 00000000`00000001 fffff801`18e233cf : nt!KiExceptionDispatch+0x11d

fffff385`e346f610 fffff801`18f0e354 : ffffc202`182d3420 00000000`00010001 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x322

fffff385`e346f7a0 fffff801`18e72a95 : ffffab01`74ec2f80 00000000`00000001 fffff385`e346f7a8 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0xd4

fffff385`e346f7f0 fffff801`18e720ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305

fffff385`e346f930 fffff801`18fc03c4 : ffffffff`00000000 ffffab01`74ec0180 ffffab01`74ed11c0 ffffc202`152ac080 : nt!KiRetireDpcList+0x1ef

fffff385`e346fb60 00000000`00000000 : fffff385`e3470000 fffff385`e3469000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84





THREAD_SHA1_HASH_MOD_FUNC: 1bbc297b1ce92dd57f8a5ce8fa2501473efd5aa0



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7d5d3631c1558fcc8fd9c35b093149d4b6daf391



THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c



FOLLOWUP_IP:

nt!ExpGetPoolTagInfoTarget+d4

fffff801`18f0e354 8b0a mov ecx,dword ptr [rdx]



FAULT_INSTR_CODE: c9850a8b



SYMBOL_STACK_INDEX: 7



SYMBOL_NAME: nt!ExpGetPoolTagInfoTarget+d4



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 3ed0f42



IMAGE_VERSION: 10.0.18362.239



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: d4



FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!ExpGetPoolTagInfoTarget



BUCKET_ID: 0x1E_c0000005_R_nt!ExpGetPoolTagInfoTarget



PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!ExpGetPoolTagInfoTarget



TARGET_TIME: 2019-07-23T10:15:29.000Z



OSBUILD: 18362



OSSERVICEPACK: 239



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: 1972-02-02 15:33:06



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 755



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!expgetpooltaginfotarget



FAILURE_ID_HASH: {e64504ba-aa08-41df-ee51-3f83a3a25c62}



Followup: MachineOwner

:)

 

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.

 

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.