Question I got a BSOD while charging my laptop and i try the memory.dmp but I can't understand it ?

[jemz_0102]

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


Loading Dump File [C:\Users\izraj\OneDrive\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff803`5ea00000 PsLoadedModuleList = 0xfffff803`5f6134a0
Debug session time: Thu Dec 21 15:13:36.310 2023 (UTC + 8:00)
System Uptime: 0 days 5:35:55.119
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000063`31577018). Type ".hh dbgerr001" for details
Loading unloaded module list
................
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff805229fe6d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8035ececb31, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 4140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5196

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

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

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

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


FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 50

BUGCHECK_P1: fffff805229fe6d0

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8035ececb31

BUGCHECK_P4: 2

READ_ADDRESS: fffff805229fe6d0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffffe8e143335f0 -- (.trap 0xfffffe8e143335f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000070ffa360 rbx=0000000000000000 rcx=395d1b6d00140000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8035ececb31 rsp=fffffe8e14333788 rbp=fffffe8e14333b60
r8=0000000000000002 r9=fffff8035ea00000 r10=0000000000000004
r11=fffffe8e14333738 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!CmpRecordRegistryLockAcquire+0x51:
fffff803`5ececb31 85c0 test eax,eax
Resetting default scope

MISALIGNED_IP:
nt!CmpRecordRegistryLockAcquire+51
fffff803`5ececb31 85c0 test eax,eax

STACK_TEXT:
fffffe8e`143333c8 fffff803`5ee8c83a : 00000000`00000050 fffff805`229fe6d0 00000000`00000000 fffffe8e`143335f0 : nt!KeBugCheckEx
fffffe8e`143333d0 fffff803`5ec6211c : ffff8009`71f435c0 00000000`00000000 00000000`00000000 fffff805`229fe6d0 : nt!MiSystemFault+0x1fd42a
fffffe8e`143334d0 fffff803`5ee27929 : ffffce0e`5b000380 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x29c
fffffe8e`143335f0 fffff803`5ececb31 : fffff803`5f4f3523 fffffe8e`746c6644 fffffe8e`14333800 ffffce0e`6a417ce0 : nt!KiPageFault+0x369
fffffe8e`14333788 fffffe8e`14333b60 : ffff8009`71f435c0 fffffe8e`14333840 00000000`00000000 80096ddd`00000001 : nt!CmpRecordRegistryLockAcquire+0x51
fffffe8e`143337d8 ffff8009`71f435c0 : fffffe8e`14333840 00000000`00000000 80096ddd`00000001 fffffe8e`143339a0 : 0xfffffe8e`14333b60
fffffe8e`143337e0 fffffe8e`14333840 : 00000000`00000000 80096ddd`00000001 fffffe8e`143339a0 ffffce00`00340101 : 0xffff8009`71f435c0
fffffe8e`143337e8 00000000`00000000 : 80096ddd`00000001 fffffe8e`143339a0 ffffce00`00340101 ffffce0e`6b924cc0 : 0xfffffe8e`14333840


SYMBOL_NAME: nt!CmpRecordRegistryLockAcquire+51

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

 

[Hellfire13]

Random memory corruption crash, unless this is not the first instance of it. You can run memtest if you want, but I doubt you will find much.