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

Using NET for debugging
Opened WinSock 2.0
Waiting to reconnect...
You can get the target MAC address by running .kdtargetmac command.
Connected to Windows 10 22621 x64 target at (Mon Apr 10 03:13:37.093 2023 (UTC + 2:00)), ptr64 TRUE
Kernel Debugger connection established.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (1 procs) Free x64
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff802`33000000 PsLoadedModuleList = 0xfffff802`33c13430
System Uptime: 0 days 0:00:01.983
KDTARGET: Refreshing KD connection
KDTARGET: Refreshing KD connection

*** Fatal System Error: 0x00000050
                       (0xFFFFF802332F51AC,0x0000000000000003,0xFFFFF802332F51AC,0x0000000000000002)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

For analysis of this file, run !analyze -v
nt!DbgBreakPointWithStatus:
fffff802`334333e0 cc              int     3
1: kd> !analyze -v
Connected to Windows 10 22621 x64 target at (Mon Apr 10 03:14:31.924 2023 (UTC + 2:00)), ptr64 TRUE
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        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: fffff802332f51ac, memory referenced.
Arg2: 0000000000000003, value 0 = read operation, 1 = write operation.
Arg3: fffff802332f51ac, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.PTE
    Value: Valid

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 3546

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 67082

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

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

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

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff802332f51ac

BUGCHECK_P2: 3

BUGCHECK_P3: fffff802332f51ac

BUGCHECK_P4: 2

WRITE_ADDRESS:  fffff802332f51ac

MM_INTERNAL_CODE:  2

PROCESS_NAME:  System

TRAP_FRAME:  ffff970178b4f4b0 -- (.trap 0xffff970178b4f4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff802332f51ac rbx=0000000000000000 rcx=0000000000001000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802332f51ac rsp=ffff970178b4f648 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=ffffe78e1759e020
r11=ffff970178b4f6b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAllocateInterrupt+0x7c:
fffff802`332f51ac 0000            add     byte ptr [rax],al ds:fffff802`332f51ac=00
Resetting default scope

MISALIGNED_IP:
nt!KeAllocateInterrupt+7c
fffff802`332f51ac 0000            add     byte ptr [rax],al

STACK_TEXT:
ffff9701`78b4ea78 fffff802`335582b2     : ffff9701`78b4ebe0 fffff802`33208440 ffffc381`ae7c3180 fffff802`332f5101 : nt!DbgBreakPointWithStatus
ffff9701`78b4ea80 fffff802`335579a3     : ffffc381`00000003 ffff9701`78b4ebe0 fffff802`33442770 00000000`00000050 : nt!KiBugCheckDebugBreak+0x12
ffff9701`78b4eae0 fffff802`33429507     : 00000000`00000000 00000000`00000000 ffff9701`78b4f4b0 fffff802`33c69500 : nt!KeBugCheck2+0xba3
ffff9701`78b4f250 fffff802`33481ebb     : 00000000`00000050 fffff802`332f51ac 00000000`00000003 ffff9701`78b4f4b0 : nt!KeBugCheckEx+0x107
ffff9701`78b4f290 fffff802`3325766c     : 00000000`00000065 00000000`00000003 ffff9701`78b4f449 00000000`00000000 : nt!MiSystemFault+0x22d76b
ffff9701`78b4f390 fffff802`3343a029     : fffff802`435e3010 fffff802`435e3010 00000000`00000002 00000000`00000000 : nt!MmAccessFault+0x29c
ffff9701`78b4f4b0 fffff802`332f51ac     : fffff802`435e1063 fffff802`33000000 00000000`01047000 fffff802`435e1a20 : nt!KiPageFault+0x369
ffff9701`78b4f648 00000000`00000000     : ffffe78e`1baff000 fffff802`332f51ac 00000000`01047000 fffff802`33000000 : nt!KeAllocateInterrupt+0x7c


SYMBOL_NAME:  nt!KeAllocateInterrupt+7c

IMAGE_NAME:  hardware

STACK_COMMAND:  .cxr; .ecxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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