Gelegentllicher Bluescreen

tomtom19861 · 4. Oktober 2021

Hab seit ca. 2 Wochen das das System gelegentlich abstürzt. Hab schon ein paar Sachen durchgetestet. Grafikkarte über FurMark belastet und CPU übder Prime95 da hat sich jeweils nichts getan weshalb ich vermute das da kein Problem vorliegt Ramspeicher hätte ich auch mit einem WindowsTool überprüft was auch nichts ergeben hat.
Hab vor den Vorfällen die Tastatur getauscht bin aber nicht sicher ob das nen Bluescreen hervorrufen kann.

Hab den Bluescreen jetzt auslesen lassen nach Anleitung:

Code:

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
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.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`43800000 PsLoadedModuleList = 0xfffff802`4442a230
Debug session time: Fri Oct  1 21:34:21.866 2021 (UTC + 2:00)
System Uptime: 0 days 2:01:17.522
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8013f93be00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8023f91ee73, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 26

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8013f93be00

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8023f91ee73

BUGCHECK_P4: 2

READ_ADDRESS:  fffff8013f93be00

MM_INTERNAL_CODE:  2

IMAGE_NAME:  bddci.sys

MODULE_NAME: bddci

FAULTING_MODULE: fffff8023f8f0000 bddci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  fffff4032c097380 -- (.trap 0xfffff4032c097380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8013f93be00 rbx=0000000000000000 rcx=0000000000000014
rdx=0000000000000164 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023f91ee73 rsp=fffff4032c097510 rbp=ffffe00aa718f4f0
 r8=ffffe00aa8df0ee0  r9=ffff9b00bd9c0000 r10=fffff80243a3a390
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
bddci+0x2ee73:
fffff802`3f91ee73 488b18          mov     rbx,qword ptr [rax] ds:fffff801`3f93be00=????????????????
Resetting default scope

STACK_TEXT: 
fffff403`2c0970d8 fffff802`43c4a46f : 00000000`00000050 fffff801`3f93be00 00000000`00000000 fffff403`2c097380 : nt!KeBugCheckEx
fffff403`2c0970e0 fffff802`43a9f500 : 00000000`00000000 00000000`00000000 fffff403`2c097400 00000000`00000000 : nt!MiSystemFault+0x18d0bf
fffff403`2c0971e0 fffff802`43c0535e : 00000000`00000103 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff403`2c097380 fffff802`3f91ee73 : 00000000`00000000 fffff802`3f91ee50 00000000`00000164 01000000`00100000 : nt!KiPageFault+0x35e
fffff403`2c097510 fffff802`47450577 : ffffe00a`9498a400 fffff802`3f91ee50 ffffe00a`94aaef40 fffff802`472c5a2b : bddci+0x2ee73
fffff403`2c097540 fffff802`47450037 : 00000000`00003b5b ffffe00a`a9ee94d0 ffffe00a`a5affd00 ffffe00a`94aaef40 : NETIO!WfpNotifyFlowContextDelete+0x20b
fffff403`2c0975c0 fffff802`475824f9 : ffffe00a`ac00ff00 ffffe00a`a718f4f0 fffff403`2c097720 ffffe00a`a9ee94a0 : NETIO!KfdAleNotifyFlowDeletion+0x1c7
fffff403`2c097620 fffff802`47580333 : 00000000`00000000 fffff403`2c0979b8 00000000`00000000 ffffe00a`aead9550 : tcpip!TcpCleanupTcbWorkQueueRoutine+0x149
fffff403`2c097780 fffff802`4754910f : 00000000`00000000 ffffe00a`aead71c0 00000000`00000000 fffff802`4748f5d3 : tcpip!TcpCleanupTcb+0x47
fffff403`2c0977b0 fffff802`47610bba : 00000000`00000000 ffffe00a`a74da410 00000000`00000000 fffff802`4748f65c : tcpip!TcpDereferenceTcb+0x2b
fffff403`2c0977e0 fffff802`47651634 : ffffe00a`a4d344d8 fffff802`474502ff 00000000`00000103 fffff802`4748f307 : tcpip!InetInspectDereferenceEndpoint+0x1a
fffff403`2c097810 fffff802`47650893 : ffffe00a`9dfd7560 ffffe00a`a74da8a0 ffffe00a`aead9550 ffffe00a`a74da8a0 : tcpip!AleReleseDeactivateNotifyContext+0x74
fffff403`2c097860 fffff802`4748ecbd : 00001b7b`0000153e 00000000`00000001 9a7c6609`0ed91ac2 00000000`00000000 : tcpip!AleNotifyEndpointDeactivateComplete+0x23
fffff403`2c097890 fffff802`47827965 : ffffe00a`a74da8a0 ffffe00a`a5daf4f0 00000000`00000000 ffffe00a`a4d344a0 : NETIO!FeCompleteClassify+0x19d
fffff403`2c0978f0 fffff802`3f92298b : fffff802`3f8f5730 fffff802`441b2149 ffffe00a`00000000 fffff802`3f92558a : fwpkclnt!FwpsCompleteClassify0+0x15
fffff403`2c097920 fffff802`3f922920 : fffff802`3f921740 fffff802`3f925799 00000000`00000001 fffff802`3f9415f8 : bddci+0x3298b
fffff403`2c097950 fffff802`3f923a2c : fffff802`3f8f5730 ffffe00a`9dae4f48 fffff403`2c097a09 ffffe00a`9dae4dc0 : bddci+0x32920
fffff403`2c097990 fffff802`3f924b41 : 00000000`00000000 ffffe00a`9dae4dc0 fffff802`3f924a20 ffffe00a`9dae4dc0 : bddci+0x33a2c
fffff403`2c097a70 fffff802`3f924a43 : 00000000`00000000 00000000`00000080 00000000`00000000 ffffe00a`92b081c0 : bddci+0x34b41
fffff403`2c097ae0 fffff802`43b55855 : ffffe00a`9daf1040 fffff802`3f924a20 ffffe00a`9dae4dc0 00000000`00000001 : bddci+0x34a43
fffff403`2c097b10 fffff802`43bfe818 : ffff9b00`bd8e4180 ffffe00a`9daf1040 fffff802`43b55800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff403`2c097b60 00000000`00000000 : fffff403`2c098000 fffff403`2c091000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bddci+2ee73

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2ee73

FAILURE_BUCKET_ID:  AV_R_INVALID_bddci!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b13fb0b8-ac03-1897-350a-0adedfcd4556}

Followup:     MachineOwner

ShiZon · 4. Oktober 2021

Gab es vor zwei Wochen ein Update oder ein Programm, was du aus nicht sicher Quelle herunter gezogen hast? Es könnte auf eine Maleware hindeuten. Hast du ein Antiviren Programm drauf und wenn ja dann bitte welches? Wenn ich das richtig lese, hängt es am bddci.sys und das stammt von Bitfender, hast du evtl. Bitfender drauf? Wenn ja weg damit und Windows Defender anwerfen. Wann wurde Windows zu letzten mal neu aufgesetzt? Hast du ein Backup erstellt? Sind alle Treiber aktuell?

Werde aber aus diesem hier nicht schlau, es steht ganz unten, was auch daran liegt das ich echt eingerostet bin. :-(

SYMBOL_NAME: bddci+2ee73

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2ee73

FAILURE_BUCKET_ID: AV_R_INVALID_bddci!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b13fb0b8-ac03-1897-350a-0adedfcd4556}

Followup: MachineOwner

doedelmeister · 4. Oktober 2021

bei RAM testen immer den memtest86 nehmen und von nem USB Stick damit booten und 1-2 Stunden testen lassen.

Ansonsten mal das Übliche: Übertaktungen und RAM Einstellungen auf Standart setzen und Grafikkartentreiber sauber deinstallieren. GGf. Windows sauber neuinstallieren. Wenn das alles nix hilft kann man immer noch weitersehen. Aber zu 70% löst das schon die Probleme.

tomtom19861 · 4. Oktober 2021

AntiViren Programm: Kaspersky
Bitdefender hab ich nicht installiert und es läuft auch kein prozess mit Bitdefender.
Windows Defender wird über Kaspersky Intenet Security gedeckt.
Malewarebytes hab ich auch schon drüberlaufen lassen und PC ist danach trotzdem noch abgestürzt.
Hab die zuletzt installierten Programme unten angehängt da ist meiner Meinung nach nichts dubioses dabei.
Neu Aufgesetzt hab ich den PC schon lange nicht mehr. Mindestens 1 Jahr her. Hab aber kein Backup gemacht.

Code:

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
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.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`43800000 PsLoadedModuleList = 0xfffff802`4442a230
Debug session time: Fri Oct  1 21:34:21.866 2021 (UTC + 2:00)
System Uptime: 0 days 2:01:17.522
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8013f93be00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8023f91ee73, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8013f93be00

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8023f91ee73

BUGCHECK_P4: 2

READ_ADDRESS:  fffff8013f93be00

MM_INTERNAL_CODE:  2

IMAGE_NAME:  bddci.sys

MODULE_NAME: bddci

FAULTING_MODULE: fffff8023f8f0000 bddci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  fffff4032c097380 -- (.trap 0xfffff4032c097380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8013f93be00 rbx=0000000000000000 rcx=0000000000000014
rdx=0000000000000164 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023f91ee73 rsp=fffff4032c097510 rbp=ffffe00aa718f4f0
 r8=ffffe00aa8df0ee0  r9=ffff9b00bd9c0000 r10=fffff80243a3a390
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
bddci+0x2ee73:
fffff802`3f91ee73 488b18          mov     rbx,qword ptr [rax] ds:fffff801`3f93be00=????????????????
Resetting default scope

STACK_TEXT:
fffff403`2c0970d8 fffff802`43c4a46f : 00000000`00000050 fffff801`3f93be00 00000000`00000000 fffff403`2c097380 : nt!KeBugCheckEx
fffff403`2c0970e0 fffff802`43a9f500 : 00000000`00000000 00000000`00000000 fffff403`2c097400 00000000`00000000 : nt!MiSystemFault+0x18d0bf
fffff403`2c0971e0 fffff802`43c0535e : 00000000`00000103 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff403`2c097380 fffff802`3f91ee73 : 00000000`00000000 fffff802`3f91ee50 00000000`00000164 01000000`00100000 : nt!KiPageFault+0x35e
fffff403`2c097510 fffff802`47450577 : ffffe00a`9498a400 fffff802`3f91ee50 ffffe00a`94aaef40 fffff802`472c5a2b : bddci+0x2ee73
fffff403`2c097540 fffff802`47450037 : 00000000`00003b5b ffffe00a`a9ee94d0 ffffe00a`a5affd00 ffffe00a`94aaef40 : NETIO!WfpNotifyFlowContextDelete+0x20b
fffff403`2c0975c0 fffff802`475824f9 : ffffe00a`ac00ff00 ffffe00a`a718f4f0 fffff403`2c097720 ffffe00a`a9ee94a0 : NETIO!KfdAleNotifyFlowDeletion+0x1c7
fffff403`2c097620 fffff802`47580333 : 00000000`00000000 fffff403`2c0979b8 00000000`00000000 ffffe00a`aead9550 : tcpip!TcpCleanupTcbWorkQueueRoutine+0x149
fffff403`2c097780 fffff802`4754910f : 00000000`00000000 ffffe00a`aead71c0 00000000`00000000 fffff802`4748f5d3 : tcpip!TcpCleanupTcb+0x47
fffff403`2c0977b0 fffff802`47610bba : 00000000`00000000 ffffe00a`a74da410 00000000`00000000 fffff802`4748f65c : tcpip!TcpDereferenceTcb+0x2b
fffff403`2c0977e0 fffff802`47651634 : ffffe00a`a4d344d8 fffff802`474502ff 00000000`00000103 fffff802`4748f307 : tcpip!InetInspectDereferenceEndpoint+0x1a
fffff403`2c097810 fffff802`47650893 : ffffe00a`9dfd7560 ffffe00a`a74da8a0 ffffe00a`aead9550 ffffe00a`a74da8a0 : tcpip!AleReleseDeactivateNotifyContext+0x74
fffff403`2c097860 fffff802`4748ecbd : 00001b7b`0000153e 00000000`00000001 9a7c6609`0ed91ac2 00000000`00000000 : tcpip!AleNotifyEndpointDeactivateComplete+0x23
fffff403`2c097890 fffff802`47827965 : ffffe00a`a74da8a0 ffffe00a`a5daf4f0 00000000`00000000 ffffe00a`a4d344a0 : NETIO!FeCompleteClassify+0x19d
fffff403`2c0978f0 fffff802`3f92298b : fffff802`3f8f5730 fffff802`441b2149 ffffe00a`00000000 fffff802`3f92558a : fwpkclnt!FwpsCompleteClassify0+0x15
fffff403`2c097920 fffff802`3f922920 : fffff802`3f921740 fffff802`3f925799 00000000`00000001 fffff802`3f9415f8 : bddci+0x3298b
fffff403`2c097950 fffff802`3f923a2c : fffff802`3f8f5730 ffffe00a`9dae4f48 fffff403`2c097a09 ffffe00a`9dae4dc0 : bddci+0x32920
fffff403`2c097990 fffff802`3f924b41 : 00000000`00000000 ffffe00a`9dae4dc0 fffff802`3f924a20 ffffe00a`9dae4dc0 : bddci+0x33a2c
fffff403`2c097a70 fffff802`3f924a43 : 00000000`00000000 00000000`00000080 00000000`00000000 ffffe00a`92b081c0 : bddci+0x34b41
fffff403`2c097ae0 fffff802`43b55855 : ffffe00a`9daf1040 fffff802`3f924a20 ffffe00a`9dae4dc0 00000000`00000001 : bddci+0x34a43
fffff403`2c097b10 fffff802`43bfe818 : ffff9b00`bd8e4180 ffffe00a`9daf1040 fffff802`43b55800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff403`2c097b60 00000000`00000000 : fffff403`2c098000 fffff403`2c091000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bddci+2ee73

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2ee73

FAILURE_BUCKET_ID:  AV_R_INVALID_bddci!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b13fb0b8-ac03-1897-350a-0adedfcd4556}

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

Code:

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
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.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`43800000 PsLoadedModuleList = 0xfffff802`4442a230
Debug session time: Fri Oct  1 21:34:21.866 2021 (UTC + 2:00)
System Uptime: 0 days 2:01:17.522
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8013f93be00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8023f91ee73, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 6

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8013f93be00

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8023f91ee73

BUGCHECK_P4: 2

READ_ADDRESS:  fffff8013f93be00

MM_INTERNAL_CODE:  2

IMAGE_NAME:  bddci.sys

MODULE_NAME: bddci

FAULTING_MODULE: fffff8023f8f0000 bddci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  fffff4032c097380 -- (.trap 0xfffff4032c097380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8013f93be00 rbx=0000000000000000 rcx=0000000000000014
rdx=0000000000000164 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023f91ee73 rsp=fffff4032c097510 rbp=ffffe00aa718f4f0
 r8=ffffe00aa8df0ee0  r9=ffff9b00bd9c0000 r10=fffff80243a3a390
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
bddci+0x2ee73:
fffff802`3f91ee73 488b18          mov     rbx,qword ptr [rax] ds:fffff801`3f93be00=????????????????
Resetting default scope

STACK_TEXT: 
fffff403`2c0970d8 fffff802`43c4a46f : 00000000`00000050 fffff801`3f93be00 00000000`00000000 fffff403`2c097380 : nt!KeBugCheckEx
fffff403`2c0970e0 fffff802`43a9f500 : 00000000`00000000 00000000`00000000 fffff403`2c097400 00000000`00000000 : nt!MiSystemFault+0x18d0bf
fffff403`2c0971e0 fffff802`43c0535e : 00000000`00000103 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff403`2c097380 fffff802`3f91ee73 : 00000000`00000000 fffff802`3f91ee50 00000000`00000164 01000000`00100000 : nt!KiPageFault+0x35e
fffff403`2c097510 fffff802`47450577 : ffffe00a`9498a400 fffff802`3f91ee50 ffffe00a`94aaef40 fffff802`472c5a2b : bddci+0x2ee73
fffff403`2c097540 fffff802`47450037 : 00000000`00003b5b ffffe00a`a9ee94d0 ffffe00a`a5affd00 ffffe00a`94aaef40 : NETIO!WfpNotifyFlowContextDelete+0x20b
fffff403`2c0975c0 fffff802`475824f9 : ffffe00a`ac00ff00 ffffe00a`a718f4f0 fffff403`2c097720 ffffe00a`a9ee94a0 : NETIO!KfdAleNotifyFlowDeletion+0x1c7
fffff403`2c097620 fffff802`47580333 : 00000000`00000000 fffff403`2c0979b8 00000000`00000000 ffffe00a`aead9550 : tcpip!TcpCleanupTcbWorkQueueRoutine+0x149
fffff403`2c097780 fffff802`4754910f : 00000000`00000000 ffffe00a`aead71c0 00000000`00000000 fffff802`4748f5d3 : tcpip!TcpCleanupTcb+0x47
fffff403`2c0977b0 fffff802`47610bba : 00000000`00000000 ffffe00a`a74da410 00000000`00000000 fffff802`4748f65c : tcpip!TcpDereferenceTcb+0x2b
fffff403`2c0977e0 fffff802`47651634 : ffffe00a`a4d344d8 fffff802`474502ff 00000000`00000103 fffff802`4748f307 : tcpip!InetInspectDereferenceEndpoint+0x1a
fffff403`2c097810 fffff802`47650893 : ffffe00a`9dfd7560 ffffe00a`a74da8a0 ffffe00a`aead9550 ffffe00a`a74da8a0 : tcpip!AleReleseDeactivateNotifyContext+0x74
fffff403`2c097860 fffff802`4748ecbd : 00001b7b`0000153e 00000000`00000001 9a7c6609`0ed91ac2 00000000`00000000 : tcpip!AleNotifyEndpointDeactivateComplete+0x23
fffff403`2c097890 fffff802`47827965 : ffffe00a`a74da8a0 ffffe00a`a5daf4f0 00000000`00000000 ffffe00a`a4d344a0 : NETIO!FeCompleteClassify+0x19d
fffff403`2c0978f0 fffff802`3f92298b : fffff802`3f8f5730 fffff802`441b2149 ffffe00a`00000000 fffff802`3f92558a : fwpkclnt!FwpsCompleteClassify0+0x15
fffff403`2c097920 fffff802`3f922920 : fffff802`3f921740 fffff802`3f925799 00000000`00000001 fffff802`3f9415f8 : bddci+0x3298b
fffff403`2c097950 fffff802`3f923a2c : fffff802`3f8f5730 ffffe00a`9dae4f48 fffff403`2c097a09 ffffe00a`9dae4dc0 : bddci+0x32920
fffff403`2c097990 fffff802`3f924b41 : 00000000`00000000 ffffe00a`9dae4dc0 fffff802`3f924a20 ffffe00a`9dae4dc0 : bddci+0x33a2c
fffff403`2c097a70 fffff802`3f924a43 : 00000000`00000000 00000000`00000080 00000000`00000000 ffffe00a`92b081c0 : bddci+0x34b41
fffff403`2c097ae0 fffff802`43b55855 : ffffe00a`9daf1040 fffff802`3f924a20 ffffe00a`9dae4dc0 00000000`00000001 : bddci+0x34a43
fffff403`2c097b10 fffff802`43bfe818 : ffff9b00`bd8e4180 ffffe00a`9daf1040 fffff802`43b55800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff403`2c097b60 00000000`00000000 : fffff403`2c098000 fffff403`2c091000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bddci+2ee73

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2ee73

FAILURE_BUCKET_ID:  AV_R_INVALID_bddci!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b13fb0b8-ac03-1897-350a-0adedfcd4556}

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

ShiZon · 6. Oktober 2021

Hast du schon Memtest86 durchlaufen lassen, wie es doedelmeister vorschlug? Wurde jeder RAM-Riegel einzel getestet?

tomtom19861 · 6. Oktober 2021

Ja hab Memtest86 durchlaufen lassen hat kein pr0bleme gefunden. Hab meine alte teils defekte Tastatur angeschl0ssen und seit dem kein absturz mehr. vermute es liegt wirklich an derTastatur keine ahnung warum.

wuselsurfer · 7. Oktober 2021

Wie heißt die fehlerhafte Tastatur?
Kannst Du sie an einem anderen PC / Laptop testen?

tomtom19861 · 12. Oktober 2021

Ist eine Sharkoon PureWriter gewesen. Und ja ist ist jetzt eigentlich sicher das es die Tastatur war hab mir ne neue gekauft und jetzt läuft er wieder problemlos. Beide Tastaturen waren ne Sharkoon PureWriter eine mit und eine ohne RGB vielleicht brauchen die verschiedene Treiber und haben deswegen Probleme gemacht.

Gelegentllicher Bluescreen

tomtom19861

Schraubenverwechsler(in)

ShiZon

PC-Selbstbauer(in)

doedelmeister

Software-Overclocker(in)

tomtom19861

Schraubenverwechsler(in)

ShiZon

PC-Selbstbauer(in)

tomtom19861

Schraubenverwechsler(in)

wuselsurfer

Kokü-Junkie (m/w)

tomtom19861

Schraubenverwechsler(in)

Ähnliche Themen