分析这个dmp

[FlorentinoJink]

051826-34500-01.zip

[github-actions]

I now have all the evidence needed for a comprehensive analysis. Here is the report:

---

Crash Dump Analysis Report

Crash Summary

The system encountered an IRQL_NOT_LESS_OR_EQUAL (Bugcheck 0xA) while executing the CPU idle loop on an AMD Ryzen 7 4800U processor. During an idle state transition (PpmIdleExecuteTransition), the CPU's instruction pointer became misaligned by 2 bytes, causing it to decode 00 00 as add [rax], al — an instruction that attempted to dereference address 0x6 at IRQL 0xFF (POWER_LEVEL). The automated analysis correctly flagged this as IP_MISALIGNED_AuthenticAMD.sys, pointing to a microcode-related CPU errata.

---

Detailed Analysis

Exception Details

Field	Value	Meaning
Bugcheck	0xA	IRQL_NOT_LESS_OR_EQUAL
Arg1	0x6	Memory referenced — invalid/non-canonical address
Arg2	0xFF	IRQL at time of fault — POWER_LEVEL (highest)
Arg3	0xDA	Bit 0 = 0 → read operation; Bit 3 = 0 → not execute
Arg4	fffff80237426b1d	Address that referenced memory → nt!PpmIdleExecuteTransition+0x6ad

The Misalignment — Byte-Level Evidence

The raw bytes at the faulting address fffff80237426b1d are:

37426b10  d9                                               ???
37426b11  49 89 9d 28 80 00 00       mov [r13+0x8028], rbx    (7 bytes)
37426b18  49 8b 8d c0 00 00 00       mov rcx, [r13+0xC0h]     (7 bytes)
                              ^^
                              ++--- 37426b1d: 00  ← IP lands HERE (misaligned)
37426b1f  41 0f b6 85 d1 00 00 00    movzx eax, [r13+0xD1h]   (8 bytes) ← correct boundary
37426b27  f0 48 0f ab 41 48          lock bts [rcx+0x48], rax

The faulting IP 37426b1d falls 2 bytes into the mov rcx, [r13+0xC0h] instruction (at offset +0x6ad within PpmIdleExecuteTransition). At this misaligned address, the CPU fetches 00 00 and decodes it as:

add byte ptr [rax], al    ; rax = 0x6 → tries to read from 0x6

The correct next instruction boundary is at 37426b1f — just 2 bytes later.

Trap Frame Analysis

rax=0000000000000006    ← Invalid address being dereferenced
rcx=fffff80237f29440    ← nt!KiBugCheckData (address in kernel)
rdx=0000000002000000
rip=fffff80237426b1d    ← MISALIGNED — offset +0x6ad (should be +0x6af)
r13=0000000000000000    ← NULL! Should have pointed to processor control block

Notably, R13 is NULL (0x0). The correctly-aligned instruction at 37426b1f (movzx eax, [r13+0xD1h]) would have also faulted on a NULL R13 — but the misaligned IP caused the crash first by dereferencing RAX (0x6).

CPU and Microcode Information

Property	Value
CPU	AMD Ryzen 7 4800U with Radeon Graphics
Family/Model/Stepping	23 / 96 / 1 (Renoir)
Microcode Revision	0x08600106
Cached Update	0x00000000 (none available)
Logical Processors	16
mcupdate_AuthenticAMD.dll Timestamp	E4D6B048 — Invalid
OS Version	Windows 10 Build 19041.6456 (vb_release)

---

Stack Trace Analysis

#  Call Site                                Function
--  --------------------------------------  -------------------------------
00  nt!KeBugCheckEx                         Bugcheck entry point
01  nt!KiBugCheckDispatch+0x69              Dispatched from page fault handler
02  nt!KiPageFault+0x478                    Page fault triggered by bad access
03  nt!PpmIdleExecuteTransition+0x6ad       ← MISALIGNED IP (crash origin)
04  nt!PoIdle+0x58a                         Power manager idle routine
05  nt!KiIdleLoop+0x54                      Kernel idle loop (processor 6)

The stack trace shows a clean progression from the kernel idle loop through the power manager into the idle transition routine. The crash originates at PpmIdleExecuteTransition+0x6ad, which is the misaligned IP. The page fault (KiPageFault) occurred because the misaligned decode attempted to read from address 0x6 at IRQL 0xFF, where any pageable/invalid memory access is fatal.

• Processor 6 was the crashing processor (Debugger saved IRQL for processor 0x6).
• The process context is System (nt!PsIdleProcess).

---

Root Cause

Primary Cause: AMD Ryzen CPU Errata — IP Corruption During Idle State Transitions

The root cause is a CPU/microcode-level bug on the AMD Ryzen 7 4800U (Renoir, Family 23 Model 96 Stepping 1) where the instruction pointer can become corrupted by 2 bytes during C-state (idle state) entry or exit in PpmIdleExecuteTransition. This falls into a known class of AMD processor errata related to idle state management.

Evidence:

1. IP_MISALIGNED_AuthenticAMD.sys — The automated WinDbg !analyze -v identified this exact failure bucket, which is a well-known signature for AMD microcode/IP-misalignment issues.

2. Misalignment by exactly 2 bytes — The faulting IP (+0x6ad) lands two bytes inside the prior mov rcx, [r13+0xC0h] instruction, decoding 00 00 (the final bytes of the 32-bit displacement 0x000000C0) as add [rax], al.

3. Invalid mcupdate timestamp — The mcupdate_AuthenticAMD.dll (microcode update driver) has an invalid PE timestamp (E4D6B048), which may indicate a corrupted or outdated microcode update file.

4. No cached microcode update — Cached Update Signature = 0x00000000 indicates no newer microcode was applied beyond the initial BIOS-provided revision 0x08600106.

5. Occurrence in idle loop — The crash is in KiIdleLoop → PoIdle → PpmIdleExecuteTransition, exactly where CPU C-state transitions occur. This is consistent with the class of AMD errata where the CPU mispredicts or corrupts the return address when waking from deep C-states.

---

Recommendations

Immediate Actions

1. Update AMD Chipset Drivers — Download and install the latest AMD Chipset Drivers from the AMD support website. These include updated power management drivers and processor support.

2. Update BIOS/UEFI Firmware — Check for a BIOS update from the system/motherboard manufacturer. BIOS updates often include newer AMD microcode (AGESA firmware) that patches processor errata. Look for AGESA version updates that mention Ryzen 4000-series (Renoir) fixes.

3. Update Windows — Ensure Windows Update has installed all latest patches. Microsoft occasionally distributes microcode updates through Windows Update (KB4589212-style microcode update packages).

Diagnostic Steps

4. Verify microcode after updates — After applying BIOS/chipset updates, verify the microcode revision with:

   wmic cpu get name, currentclockspeed, description, manufacturer, revision
   

   Or check the Update Signature field in the next crash dump's !cpuinfo output.

5. Disable C-States (temporary workaround) — If crashes persist, as a diagnostic step, disable AMD C-states in BIOS (Global C-State Control = Disabled or Power Supply Idle Control = Typical Current Idle). If crashes stop, it confirms the idle transition errata.

6. Check system logs — Look for preceding WHEA-Logger events (Event ID 18/19) in the Windows System Event Log, which may show corrected machine-check exceptions before the fatal crash.

Long-Term

7. Engage AMD support if the issue persists after all firmware/microcode updates, referencing:
   • Processor: AMD Ryzen 7 4800U (Family 23, Model 96, Stepping 1)
   • Microcode: 0x08600106
   • Bugcheck signature: IP_MISALIGNED_AuthenticAMD.sys

---

Analysis performed on crash dump 051826-34500-01.dmp — Windows 10 (Build 19041), AMD Ryzen 7 4800U.

---

_{Model: deepseek-v4-pro | Turns: 9 | Tokens: ~14673}