Windows 10: Bugcheck Code: KMODE_EXCEPTION_NOT_HANDLED 1e

Hey everyone, currently reaching out on my desktop in regards to my laptop. Asus rog strix GL553VE.I recently go the laptop back up and running. Unfortunately, i decided to be careless and try to figure out why the laptop screen was not coming on, so i removed the front bezzle and decided to wiggle around the laptop cable. In the process of doing that, the laptop shut out, battery light was on for like 5 seconds, then completely went blank. I figured if i short circuited anything, it would've immediately shut off. I was able to remove both harddrives from the laptop as well as the m.2 SSD, so

:)

 

[BSDO] KMODE_EXCEPTION_NOT_HANDLED (1e) - ndis.sys

Good morning, After upgrading to Winodows 11, there was a problem with the OpenVPN program.

Reverting back to Windows 10 did not resolve the issue.

The problem that is causing the BSDO is : "KMODE_EXCEPTION_NOT_HANDLED (1e)"

I have tried reinstalling the OpenVPN program.

I have tried updating the drivers for the network cards.

Unfortunately, nothing helped.

Windows update does not show any driver updates.

NIC installed "12.19.1.37 Rev.P"

Is there any help I can get?



I am attaching a minidump:
011022-13140-01.dmp

 

KMODE_EXCEPTION_NOT_HANDLED (1e)

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

Code:

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff80118f0e354, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exceptionDebugging Details:------------------KEY_VALUES_STRING: 1PROCESSES_ANALYSIS: 1SERVICE_ANALYSIS: 1STACKHASH_ANALYSIS: 1TIMELINE_ANALYSIS: 1DUMP_CLASS: 1DUMP_QUALIFIER: 401BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.SYSTEM_PRODUCT_NAME:  H370HD3SYSTEM_SKU:  Default stringSYSTEM_VERSION:  Default stringBIOS_VENDOR:  American Megatrends Inc.BIOS_VERSION:  F1BIOS_DATE:  02/23/2018BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.BASEBOARD_PRODUCT:  H370 HD3-CFBASEBOARD_VERSION:  Default stringDUMP_TYPE:  1BUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff80118f0e354BUGCHECK_P3: 0BUGCHECK_P4: ffffffffffffffffREAD_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+d4fffff801`18f0e354 8b0a            mov     ecx,dword ptr [rdx]EXCEPTION_PARAMETER2:  ffffffffffffffffBUGCHECK_STR:  0x1E_c0000005_RCPU_COUNT: 6CPU_MHZ: af8CPU_VENDOR:  GenuineIntelCPU_FAMILY: 6CPU_MODEL: 9eCPU_STEPPING: aCPU_MICROCODE: 6,9e,a,0 (F,M,S,R)  SIG: B4'00000000 (cache) B4'00000000 (init)BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXWINLOGON: 1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2ANALYSIS_SESSION_HOST:  DESKTOP-NPCV3ANALYSIS_SESSION_TIME:  07-23-2019 19:49:59.0280ANALYSIS_VERSION: 10.0.18362.1 amd64freLAST_CONTROL_TRANSFER:  from fffff801190a39ae to fffff80118fbc900STACK_TEXT:  fffff385`e346e5b8 fffff801`190a39ae : 00000000`0000001e ffffffff`c0000005 fffff801`18f0e354 00000000`00000000 : nt!KeBugCheckExfffff385`e346e5c0 fffff801`18fc562f : fffff801`1930c000 fffff801`18e00000 0005e5a8`00ab2000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22fffff385`e346e600 fffff801`18eca765 : 00000000`00000000 00000000`00000000 fffff385`e346eb70 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xffffff385`e346e630 fffff801`18ececfe : fffff385`e346f568 fffff385`e346f2b0 fffff385`e346f568 fffff385`e57c2578 : nt!RtlDispatchException+0x4a5fffff385`e346ed80 fffff801`18fce81d : 00000000`00000000 00001f80`00000200 00000000`00000103 00000000`00000000 : nt!KiDispatchException+0x16efffff385`e346f430 fffff801`18fca5a2 : ffffc202`1b451f70 ffffab01`74ec5f10 00000000`00000001 fffff801`18e233cf : nt!KiExceptionDispatch+0x11dfffff385`e346f610 fffff801`18f0e354 : ffffc202`182d3420 00000000`00010001 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x322fffff385`e346f7a0 fffff801`18e72a95 : ffffab01`74ec2f80 00000000`00000001 fffff385`e346f7a8 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0xd4fffff385`e346f7f0 fffff801`18e720ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305fffff385`e346f930 fffff801`18fc03c4 : ffffffff`00000000 ffffab01`74ec0180 ffffab01`74ed11c0 ffffc202`152ac080 : nt!KiRetireDpcList+0x1effffff385`e346fb60 00000000`00000000 : fffff385`e3470000 fffff385`e3469000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84THREAD_SHA1_HASH_MOD_FUNC:  1bbc297b1ce92dd57f8a5ce8fa2501473efd5aa0THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7d5d3631c1558fcc8fd9c35b093149d4b6daf391THREAD_SHA1_HASH_MOD:  b28610981796779b4ac02f58898fde25728a775cFOLLOWUP_IP: nt!ExpGetPoolTagInfoTarget+d4fffff801`18f0e354 8b0a            mov     ecx,dword ptr [rdx]FAULT_INSTR_CODE:  c9850a8bSYMBOL_STACK_INDEX:  7SYMBOL_NAME:  nt!ExpGetPoolTagInfoTarget+d4FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  3ed0f42IMAGE_VERSION:  10.0.18362.239STACK_COMMAND:  .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET:  d4FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!ExpGetPoolTagInfoTargetBUCKET_ID:  0x1E_c0000005_R_nt!ExpGetPoolTagInfoTargetPRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_nt!ExpGetPoolTagInfoTargetTARGET_TIME:  2019-07-23T10:15:29.000ZOSBUILD:  18362OSSERVICEPACK:  239SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK:  784PRODUCT_TYPE:  1OSPLATFORM_TYPE:  x64OSNAME:  Windows 10OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS PersonalOS_LOCALE:  USER_LCID:  0OSBUILD_TIMESTAMP:  1972-02-02 15:33:06BUILDDATESTAMP_STR:  190318-1202BUILDLAB_STR:  19h1_releaseBUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202ANALYSIS_SESSION_ELAPSED_TIME:  755ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!expgetpooltaginfotargetFAILURE_ID_HASH:  {e64504ba-aa08-41df-ee51-3f83a3a25c62}Followup:     MachineOwner

 

BSOD KMODE_EXCEPTION_NOT_HANDLED

He's recently happening this BSOD (KMODE_EXCEPTION_NOT_HANDLED): did you know how to spot the problem and how to solve?



Code:

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.18202.amd64fre.winblue_ltsb.160119-0600 Machine Name: Kernel base = 0xfffff801`1aa7b000 PsLoadedModuleList = 0xfffff801`1ad4e630 Debug session time: Mon Mar 14 01:00:08.720 2016 (UTC + 1:00) System Uptime: 0 days 0:31:51.370 Loading Kernel Symbols ............................................................... ................................................................ ................................................. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff8011ac8109f, 1, c} Probably caused by : ntkrnlmp.exe ( nt!PpmEnterPlatformIdle+ab ) Followup: MachineOwner --------- 3: 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: fffff8011ac8109f, The address that the exception occurred at Arg3: 0000000000000001, Parameter 0 of the exception Arg4: 000000000000000c, Parameter 1 of the exception Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 9600.18202.amd64fre.winblue_ltsb.160119-0600 SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M. SYSTEM_SKU: To Be Filled By O.E.M. SYSTEM_VERSION: To Be Filled By O.E.M. BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: P1.90 BIOS_DATE: 01/18/2011 BASEBOARD_MANUFACTURER: ASRock BASEBOARD_PRODUCT: P55 Extreme4 BASEBOARD_VERSION: DUMP_TYPE: 1 BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff8011ac8109f BUGCHECK_P3: 1 BUGCHECK_P4: c WRITE_ADDRESS: 000000000000000c EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: nt!PpmEnterPlatformIdle+ab fffff801`1ac8109f 89410c mov dword ptr [rcx+0Ch],eax EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 000000000000000c BUGCHECK_STR: 0x1E_c0000005_W CPU_COUNT: 4 CPU_MHZ: ec4 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 1e CPU_STEPPING: 5 CPU_MICROCODE: 6,1e,5,0 (F,M,S,R) SIG: 5'00000000 (cache) 5'00000000 (init) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: HM ANALYSIS_SESSION_TIME: 03-15-2016 01:18:28.0699 ANALYSIS_VERSION: 10.0.10586.567 amd64fre EXCEPTION_RECORD: ffffd0019c40c2c0 -- (.exr 0xffffd0019c40c2c0) ExceptionAddress: ffffd0019c40c2c8 ExceptionCode: 00000006 ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: 0000000000000001 -- (.trap 0x1) Unable to read trap frame at 00000000`00000001 LAST_CONTROL_TRANSFER: from fffff8011ac5669e to fffff8011abc93a0 STACK_TEXT: ffffd001`965b9858 fffff801`1ac5669e : 00000000`0000001e ffffffff`c0000005 fffff801`1ac8109f 00000000`00000001 : nt!KeBugCheckEx ffffd001`965b9860 fffff801`1abd08ed : ffffd001`965b9fd0 00000000`00000000 ffffd001`965ba7c8 ffffd001`965b99d0 : nt!KiFatalExceptionHandler+0x22 ffffd001`965b98a0 fffff801`1aaf074d : 00000000`00000001 fffff801`1aa7b000 ffffd001`965ba700 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd ffffd001`965b98d0 fffff801`1aaf4b0e : ffffd001`965ba7c8 ffffd001`965ba4d0 ffffd001`965ba7c8 00000001`a49123c4 : nt!RtlDispatchException+0x1a5 ffffd001`965b9fa0 fffff801`1abd4fc2 : ffffd001`9c40c2c0 ffffd001`965ba700 00000000`00000001 fffff801`1aac0a07 : nt!KiDispatchException+0x646 ffffd001`965ba690 fffff801`1abd3714 : 00000000`00000001 00000000`000000ff ffffe001`68c31900 fffff801`1abcac1c : nt!KiExceptionDispatch+0xc2 ffffd001`965ba870 fffff801`1ac8109f : 00000000`00000010 00000000`00000286 ffffd001`965baa28 00000000`00000018 : nt!KiPageFault+0x214 ffffd001`965baa00 fffff801`1abf2ec3 : ffffd001`9c400180 ffffe001`6e1e6010 ffffe001`6e1e6010 ffffe001`00000003 : nt!PpmEnterPlatformIdle+0xab ffffd001`965baa60 fffff801`1aae6c26 : ffffd001`9c400180 ffffd001`965bac8c ffffd001`965bac90 ffffd001`965bac98 : nt! ?? ::FNODOBFM::`string'+0x19603 ffffd001`965bac50 fffff801`1abccebc : ffffd001`9c400180 ffffd001`9c400180 ffffd001`9c40c2c0 00000000`00011ce3 : nt!PoIdle+0x2f6 ffffd001`965bada0 00000000`00000000 : ffffd001`965bb000 ffffd001`965b5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 6f666851b5417f545f74cd2471a609ce10542218 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 071b7805d16f412b3436fe5d4ef401b9e1c71de9 THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c FOLLOWUP_IP: nt!PpmEnterPlatformIdle+ab fffff801`1ac8109f 89410c mov dword ptr [rcx+0Ch],eax FAULT_INSTR_CODE: 890c4189 SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: nt!PpmEnterPlatformIdle+ab FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 569e61fd BUCKET_ID_FUNC_OFFSET: ab FAILURE_BUCKET_ID: 0x1E_c0000005_W_nt!PpmEnterPlatformIdle BUCKET_ID: 0x1E_c0000005_W_nt!PpmEnterPlatformIdle PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_W_nt!PpmEnterPlatformIdle TARGET_TIME: 2016-03-14T00:00:08.000Z OSBUILD: 9600 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 8.1 OSEDITION: Windows 8.1 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-01-19 17:19:09 BUILDDATESTAMP_STR: 160119-0600 BUILDLAB_STR: winblue_ltsb BUILDOSVER_STR: 6.3.9600.18202.amd64fre.winblue_ltsb.160119-0600 ANALYSIS_SESSION_ELAPSED_TIME: 1165 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1e_c0000005_w_nt!ppmenterplatformidle FAILURE_ID_HASH: {d22748df-3d72-0e5b-f501-11c1cd777fe2} Followup: MachineOwner​

[/quote]