windbg分析蓝屏原因,显示为hardware,但是不知道具体是哪一个硬件,感谢分析




```Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64

```shell



```Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\minidump\122421-10265-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 18362 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`75e00000 PsLoadedModuleList = 0xfffff805`76248150
Debug session time: Fri Dec 24 11:49:52.049 2021 (UTC + 8:00)
System Uptime: 0 days 2:55:58.875
Loading Kernel Symbols
...............................................................
................................................................
..............................................................

```shell



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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff8381d170c3b0
Arg3: fffff2050b961020
Arg4: fffff80575fcf1c6

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2905

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 27744

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

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

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

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffff8381d170c3b0

BUGCHECK_P3: fffff2050b961020

BUGCHECK_P4: fffff80575fcf1c6

TRAP_FRAME:  ffff8381d170c3b0 -- (.trap 0xffff8381d170c3b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffaf04c07aed00 rbx=0000000000000000 rcx=ffffde0dd53a4780
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80575fcf1c6 rsp=fffff2050b961020 rbp=0000000000000000
 r8=0000000000000002  r9=0000000000000000 r10=fffff805764af100
r11=ffffaf03eb40a580 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiPageFault+0x6:
fffff805`75fcf1c6 0000            add     byte ptr [rax],al ds:ffffaf04`c07aed00=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RTX.exe

MISALIGNED_IP: 
nt!KiPageFault+6
fffff805`75fcf1c6 0000            add     byte ptr [rax],al

STACK_TEXT:  
ffff8381`d170c268 fffff805`75fd32e9     : 00000000`0000007f 00000000`00000008 ffff8381`d170c3b0 fffff205`0b961020 : nt!KeBugCheckEx
ffff8381`d170c270 fffff805`75fce145     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8381`d170c3b0 fffff805`75fcf1c6     : 00000000`00000002 fffff805`75fcf1c6 00000000`00000010 00000000`00050086 : nt!KiDoubleFaultAbort+0x2c5
fffff205`0b961020 00000000`00000010     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x6
00000000`00000018 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10


SYMBOL_NAME:  nt!KiDoubleFaultAbort+2c5

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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