Kmode Exception Not Handled Bluescreen

[123sheep]

Hallo,

bekomme fast täglich immer mal wieder einen Bluescreen in unterschiedlichen Situationen seit ein paar Wochen. Mal öffne ich Photoshop, mal kopiere ich Dateien, mal dies und das und der Bluescreen "Kmode Exception Not Handled" erscheint.

• Meine Hardware ist in der Signatur. Verwinde das neuste "Version 3402" bios.
• Nezteil ist ein dark power pro 12 1200w
• Habe nichts übertaktet, nur der RAM läuft mit dem XMP Profil.
• Memtest86 habe ich schon durchlaufen lassen und er hat keine Fehler gefunden.

Windbg schreibt folgendes, verstehe dort aber nur Bahnhof.

Vielleicht kann sich das mal jemand anschauen und mir sagen was das Problem sein könnte?



************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`53800000 PsLoadedModuleList = 0xfffff803`5442a2f0
Debug session time: Fri Jan 22 10:20:29.202 2021 (UTC + 1:00)
System Uptime: 0 days 1:43:39.853
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`53bf5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`582810b0=000000000000001e
0: 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: fffff80353bfd6b7, The address that the exception occurred at
Arg3: fffffa0cf2ca58e8, Parameter 0 of the exception
Arg4: fffff80358281920, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5437

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-OBEN

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 12949

Key : Analysis.Memory.CommitPeak.Mb
Value: 96

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80353bfd6b7

BUGCHECK_P3: fffffa0cf2ca58e8

BUGCHECK_P4: fffff80358281920

WRITE_ADDRESS: fffff803544fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8035440f330: Unable to get Flags value from nt!KdVersionBlock
fffff8035440f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff80358281920

EXCEPTION_PARAMETER1: fffffa0cf2ca58e8

EXCEPTION_PARAMETER2: fffff80358281920

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

BAD_STACK_POINTER: fffff803582810a8

STACK_TEXT:
fffff803`582810a8 fffff803`53d0ebaf : 00000000`0000001e ffffffff`c0000005 fffff803`53bfd6b7 fffffa0c`f2ca58e8 : nt!KeBugCheckEx
fffff803`582810b0 fffff803`53c11986 : fffff803`58281920 fffff803`53b03845 fffffa0c`f2ca5b20 fffff803`53bfd6b7 : nt!KiFatalFilter+0x1f
fffff803`582810f0 fffff803`53bcbf32 : fffff803`00000002 fffff803`538d8e34 fffffa0c`f2ca2000 fffffa0c`f2ca8000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
fffff803`58281130 fffff803`53bfe642 : fffff803`538d8e34 fffff803`58281710 fffff803`53bcbe90 00000000`00000000 : nt!_C_specific_handler+0xa2
fffff803`582811a0 fffff803`53b2bf97 : fffff803`58281710 00000000`00000000 fffffa0c`f2ca70d0 fffff803`53b54488 : nt!RtlpExecuteHandlerForException+0x12
fffff803`582811d0 fffff803`53b2ab86 : fffffa0c`f2ca58e8 fffff803`58281e20 fffffa0c`f2ca58e8 00000000`00000000 : nt!RtlDispatchException+0x297
fffff803`582818f0 fffff803`53bf6612 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff803`58281fb0 fffff803`53bf65e0 : fffff803`53c078a5 ffffdc0a`baf0dadf ffffdc0a`3e15d3a0 ffffdc0a`2d207a30 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffa0c`f2ca57a8 fffff803`53c078a5 : ffffdc0a`baf0dadf ffffdc0a`3e15d3a0 ffffdc0a`2d207a30 ffffdc0a`2d207a30 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffa0c`f2ca57b0 fffff803`53c035e0 : 00000000`00000000 00000000`3fffffff ffffdc0a`2d276ab0 ffffdc0a`2a669d20 : nt!KiExceptionDispatch+0x125
fffffa0c`f2ca5990 fffff803`53bfd6b7 : ffffdc0a`30158540 fffff803`66394b31 fffff803`6310c6b0 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffffa0c`f2ca5b20 fffff803`66394b31 : fffff803`6310c6b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
fffffa0c`f2ca5b30 fffff803`663933c9 : 00000000`00000000 00060080`02000000 ffffdc0a`398efbd0 00000000`f2ca5e01 : Ndu!NduCreateNblContext+0x59
fffffa0c`f2ca5b70 fffff803`66393251 : 00000000`00000000 00060080`02000000 00000000`00000000 fffff803`6310a580 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0x149
fffffa0c`f2ca5bf0 fffff803`57328cee : fffffa0c`f2ca5dd8 00000000`00000002 00000000`00000004 00000000`00000000 : Ndu!NduOutboundMacClassify+0x151
fffffa0c`f2ca5c70 fffff803`57a814d5 : 00000000`00000000 ffffdc0a`2c7b29e0 ffffdc0a`2917abd0 00000000`00000051 : NETIO!KfdClassify2+0x19e
fffffa0c`f2ca5d40 fffff803`57a810ce : 00000000`00000000 ffffdc0a`2c7658c0 00000000`00000000 00000000`00000000 : wfplwfs!L2InspectNetBufferListsFast+0x165
fffffa0c`f2ca5e50 fffff803`571a58e8 : 00000000`00000001 ffffdc0a`2917abd0 ffffdc0a`287e35f0 fffff803`6301b2c0 : wfplwfs!LwfLowerSendNetBufferLists+0xbe
fffffa0c`f2ca5f00 fffff803`571de102 : 00000000`00000000 fffffa0c`f2ca5fc9 ffffdc0a`28815bb0 00000000`00000000 : ndis!ndisCallSendHandler+0x58
fffffa0c`f2ca5f50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisInvokeNextSendHandler+0x10e


SYMBOL_NAME: Ndu!NduCreateNblContext+59

MODULE_NAME: Ndu

IMAGE_NAME: Ndu.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 59

FAILURE_BUCKET_ID: 0x1E_c0000005_STACKPTR_ERROR_Ndu!NduCreateNblContext

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2b44c6ba-8dbe-d515-a0f4-1d53055ec81c}

Followup: MachineOwner

 

[Silver Server]

IM Ordner C:/Windows/Minidump
befinden sich die Informationen zum blue screen.
Die letzten fünf Files auf den Desktop kopieren.
Mit rar oder zip verpacken.
Hier im Forum hoch laden.

 

[teddy26]

Ich habe mir das mal angesehen:
bitte installiere die neuesten Treiber von der Website des Herstellers
https://docs.microsoft.com/en-us/wi...ode-exception-not-handled?redirectedfrom=MSDN

 

[123sheep]

Ich habe mir das mal angesehen:
bitte installiere die neuesten Treiber von der Website des Herstellers
https://docs.microsoft.com/en-us/wi...ode-exception-not-handled?redirectedfrom=MSDN

Welcher Hersteller?

Habe jetzt Windows neu installiert, wenn es immer noch passiert, poste ich hier die minidump Dateien.