BSODs und Freezes mit SMT

[Joke258]

1. Nenne uns bitte deine aktuelle Hardware:
(Bitte tatsächlich hier auflisten und nicht auf Signatur verweisen, da diese von einigen nicht gesehen wird und Hardware sich ändert)

• Prozessor (CPU): Ryzen 5 3600X
• Arbeitsspeicher (RAM): 2x8GB Corsair RGB Vengeance Pro 3200MhZ
• Mainboard: MSI B450 Tomahawk Max (Aktuellstes Bios)
• Netzteil: Be Quiet 650W 80+ Gold Modular
• Gehäuse: MSI Sekira
• Grafikkarte: Gigabyte RX 5700 XT OC
• HDD / SSD: Crucial 500GB SSD

2. Beschreibe dein Problem. Je genauer und besser du dein Problem beschreibst, desto besser kann dir geholfen werden (zusätzliche Bilder könnten z. B. hilfreich sein):
Ich kämpfe seit langem mit Bluescreens und Freezes.
Ich habe herausgefunden, dass die Freezes und BSODs nur auftreten wenn SMT im Bios aktiviert ist.
Mit SMT regnet es auf der aktuellen BIOS Version BSODs und Freezes im 20 Minuten Takt ohne SMT hatte ich bisher einen innerhalb von 3 Tagen.
Leider merke ich die Leistungseinbußen ohne SMT sehr doll, weshalb ich darüber nachdenke meine CPU oder Motherboard auszutauschen.
BSODs habe ich hier mal einen Kernel dump:

Spoiler: Kernel Abbild

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*http://msdl.microsoft.com/download/symbols
Symbol search path is: Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`79600000 PsLoadedModuleList = 0xfffff806`7a22a1b0
Debug session time: Tue May 18 09:50:29.593 2021 (UTC + 2:00)
System Uptime: 0 days 0:58:45.231
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols

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

• *
• Bugcheck Analysis *
• *

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000006d7d96, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8067994992e, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: a

BUGCHECK_P1: 6d7d96

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8067994992e

WRITE_ADDRESS: 00000000006d7d96

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: fffff60bc9d8d780 -- (.trap 0xfffff60bc9d8d780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff60bc9d8da78 rbx=0000000000000000 rcx=fffff60bc9d8da78
rdx=00000000006d7d96 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8067994992e rsp=fffff60bc9d8d910 rbp=fffff8067a2dfe50
r8=0000000000000000 r9=ffffaf0e39d09710 r10=fffff8067a2dfe40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForLockOwnerShip+0xe:
fffff806`7994992e 48890a mov qword ptr [rdx],rcx ds:00000000`006d7d96=????????????????
Resetting default scope

BAD_STACK_POINTER: fffff60bc9d8d638

STACK_TEXT:
fffff60b`c9d8d638 fffff806`79a08c69 : 00000000`0000000a 00000000`006d7d96 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff60b`c9d8d640 fffff806`79a04f69 : ffffaf0e`3cf32620 fffff806`799f8d55 fffff60b`c9d8d7b0 fffff60b`c9d8d7a8 : nt!KiBugCheckDispatch+0x69
fffff60b`c9d8d780 fffff806`7994992e : ffffaf0e`3c37da50 fffff60b`c9d8d9b9 ffffaf0e`3c29adb8 fffff806`8adfeaeb : nt!KiPageFault+0x469
fffff60b`c9d8d910 fffff806`79923905 : ffffaf0e`00000000 ffffaf0e`3c37da50 ffffaf0e`38598a60 fffff806`8ad87152 : nt!KxWaitForLockOwnerShip+0xe
fffff60b`c9d8d940 fffff806`79810bf2 : 00000000`00000000 ffffaf0e`35523a60 00000000`00000000 ffffaf0e`35523a60 : nt!KxAcquireQueuedSpinLock+0x55
fffff60b`c9d8d970 fffff806`7980db0d : ffffaf0e`39d09710 fffff60b`c9d8da79 fffff60b`c9d8da78 fffff806`00000000 : nt!KiAbEntryGetLockedHeadEntry+0x262
fffff60b`c9d8da10 fffff806`7988cba3 : ffff9c81`00000000 ffff9c81`00000001 00000009`00000000 00000000`00000000 : nt!KiAbProcessContextSwitch+0x11d
fffff60b`c9d8dae0 fffff806`799fdb36 : fffff806`799f2d00 fffff806`798c656a 00000001`00000001 00000001`00000000 : nt!KiQuantumEnd+0x373
fffff60b`c9d8dbe0 fffff806`799fd3d5 : ffffaf0e`3c0b2760 fffff806`799f8d81 ffffaf0e`3c37da50 fffff60b`c9d8e8d0 : nt!KiDispatchInterruptContinue+0x16
fffff60b`c9d8dc10 fffff806`799f8d81 : ffffaf0e`3c37da50 fffff60b`c9d8e8d0 ffffc180`092698b0 fffff60b`c9d8e120 : nt!KiDpcInterruptBypass+0x25
fffff60b`c9d8dc20 fffff806`8ad819c4 : fffff60b`c9d8e0c0 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
fffff60b`c9d8ddb0 fffff806`89358cc9 : ffffaf0e`39d090c0 ffffc18f`f6439180 ffffaf0e`39d097d0 fffff806`79872e19 : dxgmms2!VidMmReferenceWrittenPrimaries+0x4
fffff60b`c9d8de00 fffff806`893594a1 : ffffc18f`f6a79aa0 00000000`00000001 00000000`00000001 ffffc18f`f6a79aa0 : dxgkrnl!DXGCONTEXT::SubmitCommand+0x3d9
fffff60b`c9d8e5c0 fffff806`893588ad : 00000000`00000020 fffff806`89359f84 ffffc180`00f26cc0 00000027`1961c2d0 : dxgkrnl!DxgkSubmitCommandInternal+0x551
fffff60b`c9d8eac0 fffff806`79a086b8 : ffffaf0e`39d090c0 00000000`00000000 ffffaf0e`3a2e0000 00000001`40000000 : dxgkrnl!DxgkSubmitCommand+0x5d
fffff60b`c9d8eb00 00007ffd`57215ae4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000027`1961c208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`57215ae4


SYMBOL_NAME: nt!KxWaitForLockOwnerShip+e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: e

FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!KxWaitForLockOwnerShip

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56c5e1ad-426c-3e07-1dfd-b329bf712cb6}

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

Spoiler: Zuverlässigkeitsverlauf nach einzigen Crash ohne SMT bisher

Es sind aber auch diverse andere Bluescreens dabei die meistens immer auf ntkrnlmp.exe oder ähnliche verweisen.
Weitere Bluescreens:
Watchdog Violations,
System Thread Exception
KMODE Exception

Mit Freezes meine ich das das System einfriert und die Bilder noch da bleiben aber ich den PC force resetten muss oder er von alleine ausgeht und neustartet.

3. Welche Schritte hast du bereits unternommen/versucht, um das Problem zu lösen und was hat es gebracht?
-RAM Ausgetauscht
-XMP an/aus
-RAM Voltage bis auf 1,4v hochgeschraubt
-RAM Timings manuell eingegeben
-RAM auf Stock
-RAM mit Memtest einzeln getestet -> Keine Fehler
-Diverse Treiber geupdated
-Alle Bios Versionen ausprobiert:
Auf v30 (ältestes Bios) läuft das System auch mit SMT an so stabil das es nur 2 Mal am Tag abstürzt, auf den neueren Versionen regnet es BSODs und Freezes beim Spielen im 10-20 Minutentakt wenn SMT aktiviert ist.
-Grafikkarte ist nicht gedaisychained
-SSDs verschiedene ausprobiert
-Windows mehrmals neuaufgesetzt
-Grafikkarte undervolted/underclocked
-Prime95, Furmark -> Crashes nicht reproduzierbar


Ich tippe ja auf die CPU oder das Motherboard, wollte aber mal eure Meinung erfragen bevor ich das Geld für eines von beiden raushaue und wieder dumm dastehe. Sehe das gerade als einzige Möglichkeit das Problem irgendwie zu beheben da ich sonst alles ausprobiert habe.

Vielleicht hat einer von euch noch eine Idee?

 

[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.

 

[Joke258]

Ich hab irgendwie keine Berechtigung die zu verpacken hier aber der Inhalt mit WinDbg und oben im Post ist ja auch noch einer drin.

Spoiler: 1

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\cedri\Documents\Dump1 (2).dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`71c00000 PsLoadedModuleList = 0xfffff804`7282a1b0
Debug session time: Thu May 13 15:31:57.462 2021 (UTC + 2:00)
System Uptime: 0 days 0:01:37.104
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************

• *
• Bugcheck Analysis *
• *

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000100000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff804720082d0, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 7

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: a

BUGCHECK_P1: 100000000

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff804720082d0

READ_ADDRESS: fffff804728fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8047280f378: Unable to get Flags value from nt!KdVersionBlock
fffff8047280f378: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000100000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: ModernWarfare.exe

TRAP_FRAME: ffff8e8b3fd72970 -- (.trap 0xffff8e8b3fd72970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000100000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804720082d0 rsp=ffff8e8b3fd72b00 rbp=ffff8e8b3fd72b80
r8=000000463ec56000 r9=00007ff64290fd41 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!KiSystemCall64+0x110:
fffff804`720082d0 2001 and byte ptr [rcx],al ds:00000001`00000000=??
Resetting default scope

MISALIGNED_IP:
nt!KiSystemCall64+110
fffff804`720082d0 2001 and byte ptr [rcx],al

STACK_TEXT:
ffff8e8b`3fd72828 fffff804`72008c69 : 00000000`0000000a 00000001`00000000 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffff8e8b`3fd72830 fffff804`72004f69 : ffffb78f`8aeb4080 fffff804`721f5e31 ffffd17a`62200000 00000000`00000eec : nt!KiBugCheckDispatch+0x69
ffff8e8b`3fd72970 fffff804`720082d0 : 00000000`00000000 ffffb78f`8aeb4080 ffff8e8b`3fd72b18 00000000`00000000 : nt!KiPageFault+0x469
ffff8e8b`3fd72b00 00007ffb`2464d4a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemCall64+0x110
00000046`41cff638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`2464d4a4


SYMBOL_NAME: nt!KiSystemCall64+110

IMAGE_NAME: hardware

IMAGE_VERSION: 10.0.19041.985

STACK_COMMAND: .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup: MachineOwner

Spoiler: 2

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\cedri\Documents\Dump1.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`7b200000 PsLoadedModuleList = 0xfffff803`7be2a1b0
Debug session time: Thu May 13 15:33:25.211 2021 (UTC + 2:00)
System Uptime: 0 days 0:00:07.855
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
2: 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: fffff8037b42102e, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 7

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8037b42102e

BUGCHECK_P3: 8

BUGCHECK_P4: 0

WRITE_ADDRESS: fffff8037befa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8037be0f378: Unable to get Flags value from nt!KdVersionBlock
fffff8037be0f378: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000000

EXCEPTION_PARAMETER1: 0000000000000008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME: WerFault.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffcb86`17875d88 fffff803`7b63b84b : 00000000`0000001e ffffffff`c0000005 fffff803`7b42102e 00000000`00000008 : nt!KeBugCheckEx
ffffcb86`17875d90 fffff803`7b608dac : 00000000`00001000 ffffcb86`17876630 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b589b
ffffcb86`17876450 fffff803`7b604f43 : 00000000`00000000 00000000`00000000 00000000`ffffffde 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffcb86`17876630 fffff803`7b42102e : ffffa58f`78fcfd90 ffffa58f`78fcfd90 ffffa58f`77f1f0c0 00000000`00000000 : nt!KiPageFault+0x443
ffffcb86`178767c8 00000000`00000001 : ffffbb0f`00000001 ffffa58f`00000001 ffffa58f`00000000 ffffa58f`791c3c00 : nt!MiFinishVadDeletion+0x50e
ffffcb86`17876868 ffffbb0f`00000001 : ffffa58f`00000001 ffffa58f`00000000 ffffa58f`791c3c00 ffffa58f`78fcfd90 : 0x1
ffffcb86`17876870 ffffa58f`00000001 : ffffa58f`00000000 ffffa58f`791c3c00 ffffa58f`78fcfd90 ffffcb86`17876988 : 0xffffbb0f`00000001
ffffcb86`17876878 ffffa58f`00000000 : ffffa58f`791c3c00 ffffa58f`78fcfd90 ffffcb86`17876988 ffff9300`0001ea58 : 0xffffa58f`00000001
ffffcb86`17876880 ffffa58f`791c3c00 : ffffa58f`78fcfd90 ffffcb86`17876988 ffff9300`0001ea58 ffffa58f`77f1f0c0 : 0xffffa58f`00000000
ffffcb86`17876888 ffffa58f`78fcfd90 : ffffcb86`17876988 ffff9300`0001ea58 ffffa58f`77f1f0c0 00000000`03d40000 : 0xffffa58f`791c3c00
ffffcb86`17876890 ffffcb86`17876988 : ffff9300`0001ea58 ffffa58f`77f1f0c0 00000000`03d40000 00000000`03d4dfff : 0xffffa58f`78fcfd90
ffffcb86`17876898 ffff9300`0001ea58 : ffffa58f`77f1f0c0 00000000`03d40000 00000000`03d4dfff 00000000`00000001 : 0xffffcb86`17876988
ffffcb86`178768a0 ffffa58f`77f1f0c0 : 00000000`03d40000 00000000`03d4dfff 00000000`00000001 ffffa58f`77f1f740 : 0xffff9300`0001ea58
ffffcb86`178768a8 00000000`03d40000 : 00000000`03d4dfff 00000000`00000001 ffffa58f`77f1f740 ffffa58f`77e740c0 : 0xffffa58f`77f1f0c0
ffffcb86`178768b0 00000000`03d4dfff : 00000000`00000001 ffffa58f`77f1f740 ffffa58f`77e740c0 ffffa58f`790cb5c0 : 0x3d40000
ffffcb86`178768b8 00000000`00000001 : ffffa58f`77f1f740 ffffa58f`77e740c0 ffffa58f`790cb5c0 ffffa58f`790cb5c0 : 0x3d4dfff
ffffcb86`178768c0 ffffa58f`77f1f740 : ffffa58f`77e740c0 ffffa58f`790cb5c0 ffffa58f`790cb5c0 ffffa58f`77f1f590 : 0x1
ffffcb86`178768c8 ffffa58f`77e740c0 : ffffa58f`790cb5c0 ffffa58f`790cb5c0 ffffa58f`77f1f590 00000000`00000000 : 0xffffa58f`77f1f740
ffffcb86`178768d0 ffffa58f`790cb5c0 : ffffa58f`790cb5c0 ffffa58f`77f1f590 00000000`00000000 00000000`00000000 : 0xffffa58f`77e740c0
ffffcb86`178768d8 ffffa58f`790cb5c0 : ffffa58f`77f1f590 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa58f`790cb5c0
ffffcb86`178768e0 ffffa58f`77f1f590 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa58f`790cb5c0
ffffcb86`178768e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffa58f`77f1f590


SYMBOL_NAME: nt!MiFinishVadDeletion+50e

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.985

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 50e

FAILURE_BUCKET_ID: 0x1E_c0000005_X_nt!MiFinishVadDeletion

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {72e096e3-24cd-3748-532b-eecbccafc69f}

Followup: MachineOwner

Spoiler: 3

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\cedri\Documents\Dump2.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: Srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0d800000 PsLoadedModuleList = 0xfffff806`0e42a1b0
Debug session time: Thu May 13 15:34:17.231 2021 (UTC + 2:00)
System Uptime: 0 days 0:00:10.876
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************

• *
• Bugcheck Analysis *
• *

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: ffffcc82917f7140, Object type of the object whose reference count is being lowered
Arg2: ffff8a0b4d0d2c60, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: ffff8a0b4d0d2c30, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.

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

DBGHELP: Timeout to store: C:\Symbols*http://msdl.microsoft.com/download/symbols

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 27

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 18

BUGCHECK_P1: ffffcc82917f7140

BUGCHECK_P2: ffff8a0b4d0d2c60

BUGCHECK_P3: 1

BUGCHECK_P4: ffff8a0b4d0d2c30

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: services.exe

STACK_TEXT:
ffffc88b`40822968 fffff806`0dc16e66 : 00000000`00000018 ffffcc82`917f7140 ffff8a0b`4d0d2c60 00000000`00000001 : nt!KeBugCheckEx
ffffc88b`40822970 fffff806`0da0827e : ffff8a0b`4d0d2c60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0x20ebd6
ffffc88b`408229b0 fffff806`0e0410cd : ffff8a0b`4d0d2c60 ffffcc82`00000000 ffffcc82`00000000 00000000`000010fc : nt!HalPutDmaAdapter+0xe
ffffc88b`408229e0 00000000`00000000 : ffff99a8`a2620903 fffff806`0dbfdaef fffff806`0dbf2de0 fffff806`0dac656a : nt!NtAlpcImpersonateClientOfPort+0x14c48d


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+20ebd6

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.985

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 20ebd6

FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}

Followup: MachineOwner

 

[Silver Server]

Die Datei ist schreib geschützt.
Du musst sie erst kopieren.
Dann kannst Du sie verpacken.

 

[Joke258]

Ah, hier.

 

[Joke258]

Habe jetzt den 3600x gegen einen 3700x ausgetauscht bisher läuft alles auf stock (1h ohne crash) vorher immer schon viel früher abgestürzt auf stock.
Melde mich mit dem entgültigen Ergebnis wenn der PC mehrere Tage stabil läuft.

//edit: Seit 3 Tagen keinen Crash, damit ist das Problem denke ich behoben. Es lag doch an der CPU.