Windows 10: BSOD KMODE_EXCEPTION_NOT_HANDLED 1e

A friend gets BSOD all the time after reboot in 1~10 min. The memory dump file gives the following information. I dont know how to pinpoint witch driver or application is failing. Can you help me?



KMODE_EXCEPTION_NOT_HANDLED 1eThis 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: ffffffffc0000094, The exception code that was not handledArg2: fffff8050c0e8616, The address that the exception occurred atArg3: ffff930a605f2be0, Parameter 0 of the exceptionArg4: 000000000000005a, Parameter 1 of the exception


SYMBOL_NAME: nt!PpmPerfSelectProcessorState+1a6MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1a6FAILURE_BUCKET_ID: 0x1E_c0000094_nt!PpmPerfSelectProcessorStateOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {bde8e2c9-df0d-be8a-6751-181f4d2268d0}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.

 

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]

 

BSOD - KMODE_EXCEPTION_NOT_HANDLED

Hello Nathan,

We realize the inconvenience you are experiencing with frequent BSOD after upgrading to Windows 10. We will certainly help you.

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

Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM,
and video card problem.

We suggest you to follow the steps from the links below and check if it helps:

Troubleshoot blue screen errors

How to troubleshoot blue screen errors in Windows 10

Let us know the results. We will be happy to assist you further.

Thank you.