BSOD bei vermeintlichem Treiberfehler (seit Jan 2020) verursacht durch ndis.sys+79ccb

Diskutiere BSOD bei vermeintlichem Treiberfehler (seit Jan 2020) verursacht durch ndis.sys+79ccb im Windows 10 Forum im Bereich Microsoft Community; Seit Jan 2020 bekomme ich häufig eine BSOD zu sehen. Neuere Netzwerktreiber lassen sich nicht installieren. Windows 10 sagt der aktuelle Treiber...

MS-User

Threadstarter
Dabei seit
20.09.2016
Beiträge
94.184
Seit Jan 2020 bekomme ich häufig eine BSOD zu sehen. Neuere Netzwerktreiber lassen sich nicht installieren. Windows 10 sagt der aktuelle Treiber wäre installiert. Hier die letzten vier Ereignisse lt. BlueScreenView.


041920-5812-01.dmp 19.04.2020 11:18:38 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000001 fffff804`69cb9ccb ndis.sys ndis.sys+79ccb NDIS (Network Driver Interface Specification) Betriebssystem Microsoft® Windows® Microsoft Corporation 10.0.18362.830 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c2390 C:\WINDOWS\Minidump\041920-5812-01.dmp 4 15 18362 628.716 19.04.2020 11:20:07


041920-100468-01.dmp 19.04.2020 10:04:55 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000001 fffff801`346b9ccb ndis.sys ndis.sys+79ccb NDIS (Network Driver Interface Specification) Betriebssystem Microsoft® Windows® Microsoft Corporation 10.0.18362.830 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c2390 C:\WINDOWS\Minidump\041920-100468-01.dmp 4 15 18362 742.852 19.04.2020 10:07:52


041720-100359-01.dmp 17.04.2020 16:06:33 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000001 fffff800`252b9ccb ndis.sys ndis.sys+79ccb NDIS (Network Driver Interface Specification) Betriebssystem Microsoft® Windows® Microsoft Corporation 10.0.18362.830 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c2390 C:\WINDOWS\Minidump\041720-100359-01.dmp 4 15 18362 703.980 17.04.2020 16:09:17


041720-5796-01.dmp 17.04.2020 09:49:05 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000001 fffff800`5aeb9ccb ndis.sys ndis.sys+79ccb NDIS (Network Driver Interface Specification) Betriebssystem Microsoft® Windows® Microsoft Corporation 10.0.18362.830 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c2390 C:\WINDOWS\Minidump\041720-5796-01.dmp 4 15 18362 662.804 17.04.2020 09:50:39


WinDbg zeigt unter Command folgenden Report für ein dmp File an.



Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\013120-5531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff800`84000000 PsLoadedModuleList = 0xfffff800`84448150
Debug session time: Fri Jan 31 09:47:42.941 2020 (UTC + 2:00)
System Uptime: 0 days 0:02:10.635
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff800`841c14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`8826adc0=000000000000000a
0: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800875d9d0b, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 7

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on SCHLIEBER-P710

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 12

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: 28

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff800875d9d0b

WRITE_ADDRESS: fffff800845733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8008442a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8008442a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000028

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXPNP: 1 (
!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff8008826af00 --
(.trap 0xfffff8008826af00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe189fd4c9ec0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800875d9d0b rsp=fffff8008826b090 rbp=fffff8008826b200
r8=ffffe189fdcf71d0 r9=0000000000000000 r10=ffffe189fdd7f1b0
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ndis!ndisFreeConvertedPacket+0x23:
fffff800`875d9d0b 894228 mov dword ptr [rdx+28h],eax ds:00000000`00000028=????????
Resetting default scope

STACK_TEXT:
fffff800`8826adb8 fffff800`841d32e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`8826adc0 fffff800`841cf62b : ffffe18a`0552a560 fffff800`00000000 ffffe18a`0552a560 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`8826af00 fffff800`875d9d0b : ffffe189`fd4c9e60 ffffe189`fd4c9e60 ffffe189`fd4c9f58 fffff800`8826b178 : nt!KiPageFault+0x46b
fffff800`8826b090 fffff800`875db0e1 : fffff800`8826b170 ffffe189`fdc56c00 00000000`00000000 ffffe189`fd451002 : ndis!ndisFreeConvertedPacket+0x23
fffff800`8826b0c0 fffff800`8760e307 : ffffe18a`015c41a0 fffff800`8826b170 fffff800`00000001 00000000`840f2401 : ndis!ndisXlateReturnPacketToNetBufferList+0x61
fffff800`8826b100 fffff800`875b0c97 : 00000000`00000000 ffffe189`fdd7f030 ffffe189`fdd7f030 ffffe189`fd451008 : ndis!ndisIndicateXlatedPacketsToNdis5Protocols+0x143
fffff800`8826b2b0 fffff800`87570eb0 : ffffe18a`015c41a0 ffffe189`00000000 ffffe18a`015c41a0 00000000`00000000 : ndis!ndisMTopReceiveNetBufferLists+0x45e97
fffff800`8826b3b0 fffff800`875a1756 : ffffe189`fdd7f030 fffff800`8826b481 00000000`00000000 fffff800`8826b4b0 : ndis!ndisCallReceiveHandler+0x60
fffff800`8826b400 fffff800`8756e874 : 00000000`000020a8 00000000`00000801 ffffe18a`015c41a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x207a6
fffff800`8826b4d0 fffff800`89c183b3 : 00000000`00000000 00000000`00000801 00000000`00000001 ffffe189`fdd7f030 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffff800`8826b560 fffff800`89c1947a : ffffe189`fdd7f000 ffffe189`fdc73000 ffffe189`fdc74080 00000000`00000000 : e1i65x64!RECEIVE::RxIndicateNBLs+0x12f
fffff800`8826b5c0 fffff800`89c1f020 : ffffe18a`01224370 fffff800`89c1ee00 00000000`00000001 fffff800`00000000 : e1i65x64!RECEIVE::RxProcessInterrupts+0x20a
fffff800`8826b640 fffff800`89c21195 : fffff800`89c1ee90 00000000`00000000 fffff800`8826b738 00000000`00000000 : e1i65x64!INTERRUPT::IntInterruptDPC+0x190
fffff800`8826b6c0 fffff800`89c20668 : ffffe18a`012241f0 00000001`00000000 00000000`00000000 00000000`00000000 : e1i65x64!INTERRUPT::MsgIntMessageInterruptDPC+0x305
fffff800`8826b780 fffff800`8756f2cc : 00000000`00000000 00000000`00000003 fffff800`8d5b15a0 fffff800`840221c6 : e1i65x64!INTERRUPT::MiniportMessageInterruptDPC+0x28
fffff800`8826b7c0 fffff800`8406ae95 : 00000000`00000000 00000000`00000001 fffff800`8826b8a8 00000000`00000000 : ndis!ndisInterruptDpc+0x19c
fffff800`8826b8f0 fffff800`8406a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
fffff800`8826ba30 fffff800`841c5024 : 00000000`00000000 fffff800`7fce0180 fffff800`84591400 ffffe18a`04ec1080 : nt!KiRetireDpcList+0x1ef
fffff800`8826bc60 00000000`00000000 : fffff800`8826c000 fffff800`88266000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


SYMBOL_NAME: e1i65x64!RECEIVE::RxIndicateNBLs+12f

MODULE_NAME:
e1i65x64

IMAGE_NAME: e1i65x64.sys

IMAGE_VERSION: 12.17.10.8

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 12f

FAILURE_BUCKET_ID: AV_e1i65x64!RECEIVE::RxIndicateNBLs

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {057dc173-6e72-06ad-8e0c-3bd33bf6d7e8}

Followup: MachineOwner


Kann mir da jemand weiter helfen?
---------
 
Thema:

BSOD bei vermeintlichem Treiberfehler (seit Jan 2020) verursacht durch ndis.sys+79ccb

BSOD bei vermeintlichem Treiberfehler (seit Jan 2020) verursacht durch ndis.sys+79ccb - Ähnliche Themen

BSOD KMODE_EXCEPTION_NOT_HANDLED in PpmPerfSelectProcessorState: Hi everyone! I was asked to investigate a KMODE_EXCEPTION_NOT_HANDLED BSOD on a Windows 10 system. Its current (minimal) configuration is...
Bluescreen ntoskrnl.exe: 050420-13437-01.dmp 04.05.2020 16:09:04 IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffff8505`fcbb85e1 00000000`00000002 00000000`00000000 fffff802`21ceb393...
Pc stürzt bei spielen ab: Guten Tag, Ich habe ungefähr vor 2 Wochen meinen Pc neu uns sauber aufgesetzt. Allerdings stürzt mein Pc bei Spielen mit mehr Leistung immer...
Bluescreens: Hallo erstmal :) Habe Probleme mit regelmäßigen Bluscreens und zwar fing es vor einigen Wochen an. in der Zwichenzeit habe ich bspw nun auch...
Bluescreens vom ntoskrnl.exe+3f4540: Hallo, ich habe in letzter Zeit öfter das Problem, dass mein PC oder Tabs im Browser plötzlich abstürzen. Bei den Dump-files wird mir dann immer...

Sucheingaben

stations casino

,

pOoker simulator

,

casino app

,
casinYo app
, betonline poker reviews, betonline pouker reviews, ute mountain casino, ute mountain casijno, bwin poker, casino poker, cLasino poker, world series of poker, westgate las vegas resort and casino, poker simulator, how to learn pok0er, how to learn poker, stations cnasino, how to become a poker dealer, kewadin casino, kewadin casiEno, pcoker atlas, sbobet casino, sbobet cbasino, professional poker, vegas casino
Oben