MEMORY_MANAGEMENT hatası

Katılım
17 Ekim 2021
Mesajlar
1
Daha fazla  
Cinsiyet
Erkek
İyi günler. Bilgisayarımda YouTube'da video izlerken bir anda mavi ekran hatası verdi ve hata kısmında MEMORY_MANAGEMENT yazıyordu. Bu problem karşıma bir daha gelir mi ya da bir çözümü var mı? Yardım ederseniz çok sevinirim. Altta minidub dosyasını da paylaştım. Ek olarak da windows bellek tanımlama aracını çalıştırdım ve olay günlüklerinden kontrol ettim hiçbir sıkıntı çıkmadı.

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


Loading Dump File [C:\Users\emina\Desktop\101721-12515-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`0ea00000 PsLoadedModuleList = 0xfffff800`0f62a270
Debug session time: Sun Oct 17 13:38:18.018 2021 (UTC + 3:00)
System Uptime: 1 days 13:58:55.285
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`0edf71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff487`0756f480=000000000000001a
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffffc80f3642ca0
Arg3: 0000001004100000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9390

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16925

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

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

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

Key : MemoryManagement.PFN
Value: 1004100

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: fffffc80f3642ca0

BUGCHECK_P3: 1004100000

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: node.exe

STACK_TEXT:
fffff487`0756f478 fffff800`0ec440ca : 00000000`0000001a 00000000`00041792 fffffc80`f3642ca0 00000010`04100000 : nt!KeBugCheckEx
fffff487`0756f480 fffff800`0ec428ff : ffffc68f`f1009700 00000000`00000000 ffffffff`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
fffff487`0756f580 fffff800`0ec12aa0 : 00000000`00000001 fffff487`00000000 ffffc68f`f1009550 ffffc68f`f31e5080 : nt!MiDeletePagablePteRange+0x48f
fffff487`0756f890 fffff800`0f001149 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc68f`00000000 : nt!MiDeleteVad+0x360
fffff487`0756f9a0 fffff800`0f0007e0 : ffffc68f`f312e680 ffffc68f`e7ee0260 ffffc68f`f31e5080 00000000`00000000 : nt!MiUnmapVad+0x49
fffff487`0756f9d0 fffff800`0effeaaf : ffffc681`03a342a0 ffffc681`03a342a0 ffffc68f`f312e680 ffffc68f`f1009080 : nt!MiCleanVad+0x30
fffff487`0756fa00 fffff800`0f05c5a8 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffc68f`f1009080 : nt!MmCleanProcessAddressSpace+0x137
fffff487`0756fa80 fffff800`0f0b0ab6 : ffffc68f`f1009080 ffff8286`399ac060 fffff487`0756fcd0 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
fffff487`0756fb10 fffff800`0f0f53c8 : 00000000`c0000005 00000000`00000001 00000000`00000000 000000b3`5adb7000 : nt!PspExitThread+0x5f6
fffff487`0756fc10 fffff800`0ec0ef67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
fffff487`0756fc50 fffff800`0edfb750 : 00000000`00000000 fffff487`0756fd00 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x487
fffff487`0756fd00 fffff800`0ee08c5f : ffffc68f`000000f7 00000000`00004005 00000000`00004005 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff487`0756fe40 00007ffa`62150b80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000b3`5b1ff960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`62150b80


SYMBOL_NAME: nt!MiDeleteVa+153a

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.1288

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 153a

FAILURE_BUCKET_ID: 0x1a_41792_nt!MiDeleteVa

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ad6dfca3-101b-35a8-d6e1-12de9ecbc1f5}

Followup: MachineOwner
---------
 
Son düzenleme:
Memtest86 ile de test yapın. Tek ve XMP kapalı olarak deneyin.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
 

Yeni konular

Geri
Yukarı