BSOD Windows 11 mit AMD

Hallo zusammen,

ich bin eventuell nicht der einzige, jedoch habe ich seit einer kurzen Zeit richtig schön Probleme mit auftretenden BSOD. Es gibt ja die beiden Windows Updates KB5023706 und vorher KB5022913 welche in Zusammenspiel mit AMD anscheinend richtig schön Probleme machen. Was ich bestätigen kann, mein Windows wollte nämlich gar nicht mehr starten. Acronis Image zurück gespielt und Updates mal aktuell deaktiviert. Ich schaffe es aber ab und zu immer noch einen BSOD zu bekommen. Mein System wäre:

Mainboard: Asus Tuf X570-Plus
CPU: AMD Ryzen 9 5900X
Ram: Corsair DDR4 3600 Mhz (Model gerade nicht exakt im Kopf)
HDD: Samsung NV SSD

BIOS, Chipsatz Treiber, Grafikkarte sind alle aktuell. Ich hätte vom Absturz gerade auch noch den Dump. Leider bin ich nicht wirklich schlauer. Vielleicht kann mir ja jemand sagen, was das ganze verursacht hat.

Vielen Dank für die Hilfe.

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


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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`0d200000 PsLoadedModuleList = 0xfffff800`0de13450
Debug session time: Tue Mar 21 16:19:59.432 2023 (UTC + 1:00)
System Uptime: 0 days 0:02:03.064
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`0d628c50 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe500`ee77bdd0=000000000000000a
11: 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: 00007fffffff0000, memory referenced
Arg2: 0000000000000002, 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: fffff8000d64b733, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1687

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2443

    Key  : Analysis.IO.Other.Mb
    Value: 13

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 30

    Key  : Analysis.Init.CPU.mSec
    Value: 781

    Key  : Analysis.Init.Elapsed.mSec
    Value: 21063

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  032123-8640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a

BUGCHECK_P1: 7fffffff0000

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8000d64b733

READ_ADDRESS: fffff8000df1c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 00007fffffff0000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffe500ee77bf10 -- (.trap 0xffffe500ee77bf10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00007fffffff0000 rbx=0000000000000000 rcx=00007fffffff0000
rdx=ffffe500ee77c258 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000d64b733 rsp=ffffe500ee77c0a0 rbp=ffffe500ee77c6c0
 r8=0000000000000001  r9=0000000000000000 r10=ffffe500ee77c1c0
r11=ffff9b93c1600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!RtlpxVirtualUnwind+0x239e23:
fffff800`0d64b733 0fb600          movzx   eax,byte ptr [rax] ds:00007fff`ffff0000=??
Resetting default scope

STACK_TEXT:  
ffffe500`ee77bdc8 fffff800`0d63e2a9     : 00000000`0000000a 00007fff`ffff0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffe500`ee77bdd0 fffff800`0d639934     : 00000000`00000000 fffff800`0d2b4778 ffffe500`ee77c1c0 fffff50d`b4a46268 : nt!KiBugCheckDispatch+0x69
ffffe500`ee77bf10 fffff800`0d64b733     : fffff50d`bb236df0 ffffc50e`fa99282c 00000000`00258816 fffff800`0d5eb13b : nt!KiPageFault+0x474
ffffe500`ee77c0a0 fffff800`0d40f9e5     : fffff50d`bb236df0 fffff50d`bb236bb8 00000000`00000001 00000000`00000000 : nt!RtlpxVirtualUnwind+0x239e23
ffffe500`ee77c160 fffff800`0d413907     : ffffffff`ffffffff fffff50d`bb236c60 fffff50d`bb236c60 ffffe500`ee77c900 : nt!RtlDispatchException+0x215
ffffe500`ee77c8d0 fffff800`0d629e12     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x317
ffffe500`ee77cfb0 fffff800`0d629de0     : fffff800`0d63e3f5 ffffc50f`155a5100 00000000`00000000 ffffffff`80001370 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff50d`bb236a78 fffff800`0d63e3f5     : ffffc50f`155a5100 00000000`00000000 ffffffff`80001370 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff50d`bb236a80 fffff800`0d639483     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x135
fffff50d`bb236c60 ffffc50e`fa99282c     : 00000000`00000001 ffffffff`b8797400 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x343
fffff50d`bb236df0 00000000`00000001     : ffffffff`b8797400 00000000`00000000 00000000`00000000 fffff800`0981c180 : 0xffffc50e`fa99282c
fffff50d`bb236df8 ffffffff`b8797400     : 00000000`00000000 00000000`00000000 fffff800`0981c180 00000000`00000000 : 0x1
fffff50d`bb236e00 00000000`00000000     : 00000000`00000000 fffff800`0981c180 00000000`00000000 fffff800`0df0e980 : 0xffffffff`b8797400


SYMBOL_NAME:  nt!RtlpxVirtualUnwind+239e23

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1194

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  239e23

FAILURE_BUCKET_ID:  AV_nt!RtlpxVirtualUnwind

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {90caf8d4-a034-a257-3599-d8f696fd9681}

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

Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben

Content-ID: 6452985804

Url: https://administrator.de/contentid/6452985804

Ausgedruckt am: 05.11.2024 um 21:11 Uhr

6 Kommentare

Neuester Kommentar

Moin,

hast du auch eine AMD GPU und aktuelle Treiber installiert? Die sorgen derzeit für ähnliche Probleme.

Gruß
Spirit

Ja. Also am besten Rollback auf den vorletzten Treiber? Hab jetzt Adrenalin 23.3.1 (WHQL Recommended) drauf. Vorletzte müsste glaub vom Dezember 22.11.2 sein.