Windows 10: KMODE Exception not handled BSOD in clean boot after update KB4601319

I recently updated my system with KB4601319 and KB4601050, and immediately started getting BSOD's with KMODE_EXCEPTION_NOT_HANDLED.


I have tried a lot to diagnose the issue, but I cannot figure out what the problem is.


System information:

- Custom desktop PC

- Core i7 2600k

- ASROCK H67m

- NVIDIA GTX 1080 Ti

- Creative XFi audio card

- Windows 10 20H2 / Ubuntu 20.04 Dual boot


I know the issue is not hardware related, as I have zero issues with Ubuntu. I've also run a memtest to ensure the RAM is good.


So far, the system will boot fine in safemode, but crashes after 1-20 minutes in clean boot mode all startup and services disabled.


What I have tried:

- Uninstall the updates

- Reinstall graphics drivers

- Booting with the sound card removed

- chkdsk Found and corrected one small error


Any help is much appreciated.


Here is a copy of the most recent minidump output opened on a different computer for obvious reasons


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

* *

* 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: ffffffffc0000094, The exception code that was not handled

Arg2: fffff8006ee89041, The address that the exception occurred at

Arg3: 0000000000000064, Parameter 0 of the exception

Arg4: 0000000000000001, Parameter 1 of the exception


Debugging Details:

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


KEY_VALUES_STRING: 1


Key : Analysis.CPU.Sec

Value: 7


Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on LAPTOP-HT55N3AH


Key : Analysis.DebugData

Value: CreateObject


Key : Analysis.DebugModel

Value: CreateObject


Key : Analysis.Elapsed.Sec

Value: 7


Key : Analysis.Memory.CommitPeak.Mb

Value: 78


Key : Analysis.System

Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump


BUGCHECK_CODE: 1e


BUGCHECK_P1: ffffffffc0000094


BUGCHECK_P2: fffff8006ee89041


BUGCHECK_P3: 64


BUGCHECK_P4: 1


EXCEPTION_PARAMETER1: 0000000000000064


EXCEPTION_PARAMETER2: 0000000000000001


BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1


CUSTOMER_CRASH_COUNT: 1


PROCESS_NAME: svchost.exe


BAD_STACK_POINTER: ffffa480235fd148


STACK_TEXT:

ffffa480`235fd148 fffff800`6f08f83e : 00000000`0000001e ffffffff`c0000094 fffff800`6ee89041 00000000`00000064 : nt!KeBugCheckEx

ffffa480`235fd150 fffff800`6efa6702 : fffff800`6f08f81c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22

ffffa480`235fd190 fffff800`6ee485d0 : 00000000`00000000 ffffa480`235fd700 ffff9285`d7c4cfb0 00000000`00000000 : nt!RtlpExecuteHandlerForException+0x12

ffffa480`235fd1c0 fffff800`6eeccdd6 : ffff9285`d7c4c958 ffffa480`235fde20 ffff9285`d7c4c958 00000000`00000000 : nt!RtlDispatchException+0x280

ffffa480`235fd8f0 fffff800`6ef9e6d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

ffffa480`235fdfb0 fffff800`6ef9e6a0 : fffff800`6efaf865 00000000`00000001 ffff9285`00000000 ffffdf07`eb2c9000 : nt!KxExceptionDispatchOnExceptionStack+0x12

ffff9285`d7c4c818 fffff800`6efaf865 : 00000000`00000001 ffff9285`00000000 ffffdf07`eb2c9000 ffffa480`22fec180 : nt!KiExceptionDispatchOnExceptionStackContinue

ffff9285`d7c4c820 fffff800`6efa850a : 00000000`00000000 00000000`00000001 ffffdf07`e69ac590 ffffdf07`e69ac5d0 : nt!KiExceptionDispatch+0x125

ffff9285`d7c4ca00 fffff800`6ee89041 : 00000000`00000064 ffffdf07`00003ff8 ffffdf07`00000064 fffff800`00000064 : nt!KiDivideErrorFault+0x30a

ffff9285`d7c4cb90 fffff800`6ee88e90 : ffffa480`22ff42e8 00000000`00000000 00000000`00000014 ffffa480`00000001 : nt!PpmPerfSelectProcessorState+0x199

ffff9285`d7c4cc60 fffff800`6eebca7b : ffffa480`22fef240 ffffa480`22fec180 ffff9285`d7c4cdc9 ffffa480`22fec180 : nt!PpmPerfSelectProcessorStates+0x70

ffff9285`d7c4cc90 fffff800`6ee83327 : ffffa480`22fef240 ffffa480`22fef240 ffff9285`d7c4cdc9 00000000`00000001 : nt!PpmCheckRun+0x3b

ffff9285`d7c4cd00 fffff800`6ee82f70 : ffffa480`22fec180 fffff780`00000014 00000000`00000002 ffffa480`22fec180 : nt!KiExecuteAllDpcs+0x1f3

ffff9285`d7c4ce30 fffff800`6efa4885 : 00000000`00000000 ffffa480`22fec180 ffff9285`dbe4cb80 00000000`00000000 : nt!KiRetireDpcList+0x90

ffff9285`d7c4cfb0 fffff800`6efa4670 : 0000020c`95fc0340 00000000`0000007f 00000000`00000001 0000020c`9f313000 : nt!KxRetireDpcList+0x5

ffff9285`dbe4cad0 fffff800`6efa3d3e : 00000000`40000000 ffffdf07`e48a5d40 00000000`00000020 ffffdf07`ed61a080 : nt!KiDispatchInterruptContinue

ffff9285`dbe4cb00 00007ffd`4701f207 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee

00000033`8d87c700 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4701f207


SYMBOL_NAME: nt!PpmPerfSelectProcessorState+199


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


IMAGE_VERSION: 10.0.19041.1


STACK_COMMAND: .thread ; .cxr ; kb


BUCKET_ID_FUNC_OFFSET: 199


FAILURE_BUCKET_ID: 0x1E_c0000094_STACKPTR_ERROR_nt!PpmPerfSelectProcessorState


OSPLATFORM_TYPE: x64


OSNAME: Windows 10


FAILURE_ID_HASH: {a349e6fc-c773-5f1f-3d98-37443aaf47b7}


Followup: MachineOwner

:)

 

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED (cng.sys)

Hi,

We suggest that you try the workaround suggested on DonchakVS's reply on August 5, 2015 and check if it resolves the issue:

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED (cng.sys).

 

BSOD KMODE EXCEPTION NOT HANDLED

Newly updated to Windows 10 Pro and now getting BSOD KMODE EXCEPTION NOT HANDLED. System in rebooting shortly after starting up. Any help appreciated.

 

KMode Exception Not Handled BSOD

Started receiving this lovely error yesterday Getting BSOD KMode Exception Not handled. Tried updating the drivers, tried setting what the power buttons do. I tried CCcleaner, Virus Scans, Tried setting a dump folder. And I still get the Same BSOD with no additional Errors other than KMode Exception not handled. Please helpAttachment 182877