BSOD ndu.sys and kmode exception not handled

  • Thread starter Thread starter ibs81
  • Start date Start date
I

ibs81

Guest
I am trying to figure out what is causing BSOD on my PC.

Windows 10 Pro
MotherBoard: X570 AORUS ELITE WiFi
Processor: AMD Ryzen 7 3700X 8-Core
Memory: 32GB DDR4
Graphics Card: GeForce RTX 2070 Super

It seems to be related to when either my son or I play video games on the computer.

At first I thought it was related to his FIFA game, from what I have read online. Which is when it was happening mostly. But just happened when I was on Chrome.

I have gotten two types of BSOD:

Stop Code: KMODE EXCEPTION NOT HANDLED

also

Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED. What Failed Ndu.sys.


I have gotten issues mentioning esrv.exe,hid.exe, for which I have now unistalled. The frewuency of the BSOD is almost every 20 minutes now.

I ran MemTest86 V8.4 and had no reported errors. Run took about 7.5 hours.

Here are my latest minidumps:


https://app.box.com/s/x7hpoxjzsyl3ezw5xy3wy2aw6rk32xf1



I installed WinDbg, but cant get too much from the minidumps. This is the last one I got:




*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80122c84ff0, Address of the instruction which caused the bugcheck
Arg3: ffffb7017a538930, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DS9-PC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80122c84ff0

BUGCHECK_P3: ffffb7017a538930

BUGCHECK_P4: 0

CONTEXT: ffffb7017a538930 --
(.cxr 0xffffb7017a538930)
rax=0000000000000001 rbx=ffffc909abed5d00 rcx=ffffc908a92cda40
rdx=0000000000000000 rsi=ffffc909a6cd0710 rdi=ffffc909a358b420
rip=fffff80122c84ff0 rsp=fffffd00dfce50a8 rbp=0000000000000002
r8=0000000000000001 r9=0000000000000010 r10=ffffc909a3fcb430
r11=0000000000000000 r12=0000000000000008 r13=ffffc909ab7cb9a0
r14=ffffc909ab7cb902 r15=0000000000000400
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
Ndu!CarDisableCacheAwareReference+0x30:
fffff801`22c84ff0 488701 xchg rax,qword ptr [rcx] ds:002b:ffffc908`a92cda40=????????????????
Resetting default scope

PROCESS_NAME: AVGSvc.exe

BAD_STACK_POINTER: ffffb7017a537ff8

STACK_TEXT:
fffffd00`dfce50a8 fffff801`22c84e5f : ffffc909`a6cd0710 ffffc909`abed5d00 ffffc909`975271a0 ffffc909`956ec320 : Ndu!CarDisableCacheAwareReference+0x30
fffffd00`dfce50b0 fffff801`29f846ec : ffffc909`974a28a0 fffff801`22c84de0 ffffc909`a6cd0710 00000000`00000000 : Ndu!NduFlowDelete+0x7f
fffffd00`dfce50e0 fffff801`29f841ca : 00000000`0000ff02 ffffc909`a6cd0710 fffffd00`dfce5310 ffffc909`975271a0 : NETIO!WfpProcessFlowDeleteFast+0xe4
fffffd00`dfce5120 fffff801`2a03d61a : ffffc909`0000ff02 badbadfa`badbadfa fffffd00`dfce5310 fffff801`2a229260 : NETIO!KfdAleNotifyFlowDeletion+0x1ea
fffffd00`dfce5190 fffff801`2a039540 : 00000000`000536bc 00000000`00000008 00000000`000536bc ffffc909`a72e5870 : tcpip!WfpAleFreeRemoteEndpoint+0x2a
fffffd00`dfce5210 fffff801`2a038969 : 00000000`00000000 ffffc909`a63045e0 00000000`00000000 00000000`0000afd1 : tcpip!UdpCloseEndpoint+0xbc0
fffffd00`dfce5510 fffff801`2b9ef803 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!UdpTlProviderCloseEndpoint+0x9
fffffd00`dfce5540 fffff801`2b9d2692 : ffffc909`a63044d0 ffffc909`a63045e0 00000000`00000000 00000075`00000000 : afd!AfdTLCloseEndpoint+0x47
fffffd00`dfce5580 fffff801`2b9f06fe : ffffc909`a63044d0 ffffc909`a63045e0 ffffc909`a63044d0 fffffd00`dfce5698 : afd!AfdCloseTransportEndpoint+0x8a
fffffd00`dfce5660 fffff801`2b9f0055 : ffffc909`9f091900 ffffc909`a63044d0 ffffc909`a92deb90 00000000`00000000 : afd!AfdCleanupCore+0x46e
fffffd00`dfce5780 fffff801`26a99eb9 : fffffd00`dfce5a80 fffff801`2bdc039b ffffc909`a92de9a0 fffff801`2bdc3f40 : afd!AfdDispatch+0x95
fffffd00`dfce57f0 fffff801`2bdc3fb1 : 00000000`00000000 ffffc909`a1ed2300 ffffc909`9f0917b0 00000000`00000000 : nt!IofCallDriver+0x59
fffffd00`dfce5830 fffff801`26a99eb9 : ffffc909`9f0917b0 ffffc909`a92de9a0 ffffc909`ac2934b0 00000000`00000000 : avgArPot+0x13fb1
fffffd00`dfce5880 fffff801`27002bb8 : 00000000`00000000 ffffc909`ac2934b0 00000000`00000000 ffffc909`a92de9a0 : nt!IofCallDriver+0x59
fffffd00`dfce58c0 fffff801`2700ad08 : 00000000`00000000 00000000`00000001 ffffc909`00000000 00000000`00007ff4 : nt!IopCloseFile+0x188
fffffd00`dfce5950 fffff801`2701004e : 00000000`00005544 ffff704d`eb2aa145 00000000`00000000 fffff801`26bd412c : nt!ObCloseHandleTableEntry+0x278
fffffd00`dfce5a90 fffff801`26bd4151 : ffffc909`a338d080 00000000`00001588 fffffd00`dfce5b80 00000000`00000000 : nt!NtClose+0xde
fffffd00`dfce5b00 00007ff9`2ecdc254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000075`608ff3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`2ecdc254


SYMBOL_NAME: Ndu!CarDisableCacheAwareReference+30

MODULE_NAME:
Ndu

IMAGE_NAME: Ndu.sys

STACK_COMMAND: .cxr 0xffffb7017a538930 ; kb

BUCKET_ID_FUNC_OFFSET: 30

FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_Ndu!CarDisableCacheAwareReference

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {faa18ff6-4042-6053-f4ec-f56d7c78068e}

Followup: MachineOwner
---------


Continue reading...
 

Similar threads

Back
Top