Windows 7 MEMORY_MANAGEMENT Hatası

Tarihe göre sırala Puana göre sırala
1. Aşağıdaki rehberden yararlanarak ekran kartı sürücünüzü kaldırın ve güncelleyin.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net

2. Aşağıdaki rehberden yararlanarak RAM'lerini kontrol edin ve sonucu paylaşın.
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.

Win 7 versiyonunuz güncel mi?


Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 000007fee1547001
Arg3: 00000000000139f5
Arg4: 000007dfe1547005

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

GetUlongPtrFromAddress: unable to read from fffff80002eaf300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1311

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7568

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

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

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

    Key  : WER.OS.Branch
    Value: win7sp1_ldr_escrow

    Key  : WER.OS.Timestamp
    Value: 2020-10-28T19:27:00Z

    Key  : WER.OS.Version
    Value: 7.1.7601.24562


BUGCHECK_CODE:  1a

BUGCHECK_P1: 41289

BUGCHECK_P2: 7fee1547001

BUGCHECK_P3: 139f5

BUGCHECK_P4: 7dfe1547005

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  slimjet.exe

STACK_TEXT: 
fffff880`05e9a918 fffff800`02c8c603     : 00000000`0000001a 00000000`00041289 000007fe`e1547001 00000000`000139f5 : nt!KeBugCheckEx
fffff880`05e9a920 fffff800`02d290cc     : 1f500000`841aa025 00000000`74c88121 f8a00374`2bc80400 fffff800`02c9df35 : nt!MiLocateWsle+0x1a3
fffff880`05e9a960 fffff800`02c6c4b9     : 1f500000`841aa025 00800000`3229a867 fffffa80`05704c20 00000000`00000000 : nt!MiGetPageProtection+0x17c
fffff880`05e9a9b0 fffff800`02c6c03a     : fffffa80`02b98b50 fffff880`05e9ac60 fffffa80`05e6e710 fffff880`05e9aa80 : nt!MiQueryAddressState+0x3c9
fffff880`05e9aa10 fffff800`02f1a264     : 000007ff`00000020 000007fe`e1548000 fffffa80`05704c20 fffff880`00000000 : nt!MiQueryAddressSpan+0xba
fffff880`05e9aa80 fffff800`02cb3c53     : 00000000`0000017c fffffa80`02b98b50 fffff880`00000000 00000000`0647eb48 : nt!NtQueryVirtualMemory+0x3a4
fffff880`05e9ab70 00000000`76e18f4a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0647eb28 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e18f4a


SYMBOL_NAME:  nt!MiLocateWsle+1a3

MODULE_NAME: nt

IMAGE_VERSION:  6.1.7601.24562

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

FAILURE_BUCKET_ID:  0x1a_41289_nt!MiLocateWsle+1a3

OS_VERSION:  7.1.7601.24562

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {e9ce92cb-ea41-9188-be17-9ed9301b2f4f}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000005d5b
Arg4: 0000004fb81ec009

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

GetUlongPtrFromAddress: unable to read from fffff80002ead300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1281

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11108

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

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

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

    Key  : WER.OS.Branch
    Value: win7sp1_ldr_escrow

    Key  : WER.OS.Timestamp
    Value: 2020-10-28T19:27:00Z

    Key  : WER.OS.Version
    Value: 7.1.7601.24562


BUGCHECK_CODE:  1a

BUGCHECK_P1: 5003

BUGCHECK_P2: fffff70001080000

BUGCHECK_P3: 5d5b

BUGCHECK_P4: 4fb81ec009

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  slimjet.exe

STACK_TEXT:  
fffff880`03b22728 fffff800`02c77a3c     : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00005d5b : nt!KeBugCheckEx
fffff880`03b22730 fffff800`02d4f7bb     : 00000000`00000000 00000000`0ec7e008 00000000`00000040 fffff800`02c9c99e : nt!MiAllocateWsle+0x28c
fffff880`03b22790 fffff800`02d4ff6c     : 80000000`c621d867 fffffa80`058dae98 00000000`0ec7e008 80000000`c621d963 : nt!MiCompleteProtoPteFault+0x68b
fffff880`03b22820 fffff800`02d6fb4b     : 00000000`00000001 00000000`0ec7e008 00000000`00000000 ffffffff`00000480 : nt!MiResolveDemandZeroFault+0x68c
fffff880`03b22900 fffff800`02d70336     : 00000000`00000040 00000000`00000040 fffff680`000763f0 fffffa80`058dae98 : nt!MiResolveProtoPteFault+0x71b
fffff880`03b229a0 fffff800`02d7f430     : ffffffff`ffffff00 00000000`0ec7e008 00000000`000d7f3e ffffffff`ffffffff : nt!MiDispatchFault+0x796
fffff880`03b22a90 fffff800`02cafcdc     : 00000000`00000001 00000000`0ec7e008 fffffa80`0293b401 00000000`00000000 : nt!MmAccessFault+0x4090
fffff880`03b22be0 000007fe`d7d89916     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35c
00000000`0ac7d900 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`d7d89916


SYMBOL_NAME:  nt!MiAllocateWsle+28c

MODULE_NAME: nt

IMAGE_VERSION:  6.1.7601.24562

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+28c

OS_VERSION:  7.1.7601.24562

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {1a2d3dc6-22f7-36d5-099d-bc77a64e6681}

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


*******************************************************************************
*                                                                             *
*                        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: fffffa814c0f3fb8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002de3603, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name
GetUlongPtrFromAddress: unable to read from fffff80002f01300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1343

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3620

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

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

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

    Key  : WER.OS.Branch
    Value: win7sp1_ldr_escrow

    Key  : WER.OS.Timestamp
    Value: 2020-10-28T19:27:00Z

    Key  : WER.OS.Version
    Value: 7.1.7601.24562


BUGCHECK_CODE:  50

BUGCHECK_P1: fffffa814c0f3fb8

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80002de3603

BUGCHECK_P4: 5

READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80002f012f0
GetUlongPtrFromAddress: unable to read from fffff80002f014a8
 fffffa814c0f3fb8 Nonpaged pool

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  slimjet.exe

TRAP_FRAME:  fffff8800789a4a0 -- (.trap 0xfffff8800789a4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=fffffa814c0f3fa0
rdx=0000000006eafbfe rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002de3603 rsp=fffff8800789a630 rbp=0000000000000005
 r8=fffffa80020b7a90  r9=00000003ff6d4398 r10=fffff683ff6d4398
r11=fffff8800789a650 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiEmptyWorkingSet+0x203:
fffff800`02de3603 66395918        cmp     word ptr [rcx+18h],bx ds:fffffa81`4c0f3fb8=????
Resetting default scope

STACK_TEXT:  
fffff880`0789a348 fffff800`02dcfad6     : 00000000`00000050 fffffa81`4c0f3fb8 00000000`00000000 fffff880`0789a4a0 : nt!KeBugCheckEx
fffff880`0789a350 fffff800`02d03cdc     : 00000000`00000000 fffffa81`4c0f3fb8 00000000`06750000 00000000`00000001 : nt!MmAccessFault+0x736
fffff880`0789a4a0 fffff800`02de3603     : c1700000`ae7e3025 00000000`00000001 00000003`00000000 00000000`00000007 : nt!KiPageFault+0x35c
fffff880`0789a630 fffff800`02f1362d     : fffffa80`05f3eb50 ffffffff`00000001 ffffffff`ffffffff fffff880`0789ac60 : nt!MiEmptyWorkingSet+0x203
fffff880`0789a6e0 fffff800`03108ded     : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`00000000 : nt!MmAdjustWorkingSetSizeEx+0xad
fffff880`0789a760 fffff800`031099f9     : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`00a1ebf0 : nt!PspSetQuotaLimits+0x32d
fffff880`0789a8b0 fffff800`02d05c53     : 00000000`00000008 000007fe`da6e3320 00000000`00000001 00000000`00000258 : nt!NtSetInformationProcess+0x8c9
fffff880`0789abe0 00000000`76f98eda     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00a1ebb8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f98eda


SYMBOL_NAME:  nt!MiEmptyWorkingSet+203

MODULE_NAME: nt

IMAGE_VERSION:  6.1.7601.24562

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

FAILURE_BUCKET_ID:  0x50_nt!MiEmptyWorkingSet+203

OS_VERSION:  7.1.7601.24562

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {f6898fdb-61da-0aad-4f0e-4377632d62d0}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

Windows 7 Ultimate Lite kullandığımdan, içinde Windows Update yok hocam.
 
Artı 0 Eksi
Sefa70 dedi:
Hayır hatta daha iyi olur.
Genişletmek için tıkla...

Çünkü, normal Windows'a giriş yaptığım zaman, mavi ekran veriyor.
Sefa70 dedi:
Hayır hatta daha iyi olur.
Genişletmek için tıkla...

Mavi ekran sadece Windows'u normal olarak başlat seçeneğinde çıktığına göre RAM'lerde sorun yoktur, doğru değil mi?
RAM'lerde sorun olsaydı, güvenli modda bile fazla açık kalamazdı.
 
Artı 0 Eksi
MustafaİRen dedi:
Mavi ekran, sadece Windows'u normal olarak başlat, seçeneğinde çıktığına göre, RAM'lerde sorun yoktur, doğru değil mi?
Genişletmek için tıkla...
Kesin bir cevap veremem.

MemTest86 ile kesin bir bilgiye ulaşabiliriz.
Fakat vaktiniz varsa yapın çünkü çok detaylı olduğundan çok uzun sürüyor.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
Windows 7 MEMORY_MANAGEMENT mavi ekran hatası
Mesaj
6
Görüntüleme
832
MayCrasH
T
  • Soru
Windows 7 Mavi Ekran MEMORY_MANAGEMENT
Mesaj
4
Görüntüleme
1.639
thereturn06
T
  • Soru
Windows 10 MEMORY_MANAGEMENT hatası
2
Mesaj
14
Görüntüleme
835
EgoWaixx
D
  • Soru
Windows 11 MEMORY_MANAGEMENT hatası
Mesaj
1
Görüntüleme
380
Lindorie Miriel
  • Soru
Windows 11 "MEMORY_MANAGEMENT" hatası
Mesaj
2
Görüntüleme
661
KojiroHyuga04
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…