Laptop Klavyesine Telefon Düştü ve Mavi Ekran Aldım DMP Dosyası Ekte

Merhabalar,

Konu başlığındaki gibi ağır bir akıllı telefon elimden monsteer marka laptopımın klavyesine düştü ve direkt mavi ekran aldım. DMP dosyasını ekte bıraktım. Yorumlar mısınız lütfen? Çok teşekkür ederim.

-

Kod 
Yığını:
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`82600000 PsLoadedModuleList = 0xfffff801`8322a210
Debug session time: Fri Mar  3 17:46:06.387 2023 (UTC + 3:00)
System Uptime: 2 days 21:32:06.230
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`829fa090 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8c00`1b0c7250=0000000000000050
1: 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: ffff8c001b000010, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
	bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the processor decided the fault was due to a corrupted PTE.
	bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
	- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8018288edc7, 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: 2811

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7891

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x50

    Key  : Bugcheck.Code.Register
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  030323-26265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  50

BUGCHECK_P1: ffff8c001b000010

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8018288edc7

BUGCHECK_P4: 2

READ_ADDRESS: fffff801832fa390: 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
 ffff8c001b000010 

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  ffff8c001b0c74f0 -- (.trap 0xffff8c001b0c74f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8c001b000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80182600000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8018288edc7 rsp=ffff8c001b0c7680 rbp=ffff8c001b0c7a80
 r8=0000000000000001  r9=fffff780000003d8 r10=ffff8c001b0c5e70
r11=00000000000001e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExFreeHeapPool+0xb7:
fffff801`8288edc7 488b5810        mov     rbx,qword ptr [rax+10h] ds:ffff8c00`1b000010=????????????????
Resetting default scope

STACK_TEXT:  
ffff8c00`1b0c7248 fffff801`82a744bf     : 00000000`00000050 ffff8c00`1b000010 00000000`00000000 ffff8c00`1b0c74f0 : nt!KeBugCheckEx
ffff8c00`1b0c7250 fffff801`828a4d70     : 00000000`00000000 00000000`00000000 ffff8c00`1b0c7570 00000000`00000000 : nt!MiSystemFault+0x1b171f
ffff8c00`1b0c7350 fffff801`82a09bd8     : 00000000`00000000 ffffcf0f`d9e3f639 ffffcf0f`d9e3f500 00000000`00000000 : nt!MmAccessFault+0x400
ffff8c00`1b0c74f0 fffff801`8288edc7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
ffff8c00`1b0c7680 fffff801`82882a9b     : 00000000`00000000 00000000`00000000 00000000`00010000 01000000`00100000 : nt!ExFreeHeapPool+0xb7
ffff8c00`1b0c7760 fffff801`82a0e09a     : 00000185`be8be408 fffff801`82ba7956 00000000`00000000 00000000`00000101 : nt!NtWaitForWorkViaWorkerFactory+0x118b
ffff8c00`1b0c7990 00007ff8`b4350b14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3ef
0000007f`0d97f5f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`b4350b14


SYMBOL_NAME:  nt!MiSystemFault+1b171f

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2604

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1b171f

FAILURE_BUCKET_ID:  AV_R_(null)_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {636dd506-1acb-bac0-a568-0355527c550f}

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

+1 güncel

sistem açılıyor mu

evet mavi ekran sonrası yeniden başladı sistem herhangi bi problem gözükmüyo oyuna da devam ettim ama aklıma takıldı

rami yerinden oynatmıştır. sorun yok

Anladım. peki ramler olması gerektiği şekilde mi şuan acaba? Onu nasıl test ederim