Çözüldü "MEMORY_MANAGEMENT" hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

goktug.59

Kilopat
Katılım
26 Mart 2021
Mesajlar
5.565
Makaleler
3
Çözümler
39
Yer
Tekirdağ
Daha fazla  
Sistem Özellikleri
Lenovo LOQ 15IAX9 - RTX 4050 / 24GB RAM / i5 12450HX
Cinsiyet
Erkek
RAM
8GB DDR2
SSD veya HDD modeli
GoodRam 256GB
Ekran kartı
ATI HD 4350
Anakart
Asus M3A78-CM
İşlemci
AMD Athlon II X4
Bilgisayara yeni RAM aldığımızdan beri bilgisayar değişik değişik mavi ekran hataları vermeye başladı.

Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
 ExtensionRepository : Implicit.
 UseExperimentalFeatureForNugetShare : true.
 AllowNugetExeUpdate : true.
 NonInteractiveNuget : true.
 AllowNugetMSCredentialProviderInstall : true.
 AllowParallelInitializationOfLocalRepositories : true.
 EnableRedirectToChakraJsProvider : false.

 -- Configuring repositories.
 ----> Repository : LocalInstalled, Enabled: true.
 ----> Repository : UserExtensions, Enabled: true.

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds.

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds.
 ----> Repository : UserExtensions, Enabled: true, Packages count: 0
 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42.

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

Loading Dump File [C:\Users\cemal\Desktop\112424-6750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS Personal.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`03800000 PsLoadedModuleList = 0xfffff804`0442a2b0
Debug session time: Sun Nov 24 01:00:27.066 2024 (UTC + 3:00)
System Uptime: 0 days 0:10:06.849
Loading Kernel Symbols.
...............................................................
................................................................
....................................................
Loading User Symbols.
PEB is paged out (Peb.Ldr = 000000d8`63f5c018). Type ".hh dbgerr001" for details.
Loading unloaded module list.
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`03bfbca0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffffc85`8d96b680=000000000000001a
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the BugCheck.
Arg2: ffffe50aa9abb2b0.
Arg3: ffffce819e201000.
Arg4: ffffb98de82562a8.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 3171.

 Key : Analysis.Elapsed.mSec
 Value: 3291.

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

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

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

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

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

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

 Key : Analysis.Version.DbgEng
 Value: 10.0.27725.1000

 Key : Analysis.Version.Description
 Value: 10.2408.27.01 amd64fre.

 Key : Analysis.Version.Ext
 Value: 1.2408.27.1

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1a.

 Key : Bugcheck.Code.TargetModel
 Value: 0x1a.

 Key : Failure.Bucket
 Value: 0x1a_31_nt!MiApplyCompressedFixups

 Key : Failure.Hash
 Value: {c331f2d1-f573-4955-bed6-0e48314e3a31}

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 1a.

BUGCHECK_P1: 31.

BUGCHECK_P2: ffffe50aa9abb2b0.

BUGCHECK_P3: ffffce819e201000.

BUGCHECK_P4: ffffb98de82562a8.

FILE_IN_CAB: 112424-6750-01.dmp

FAULTING_THREAD: ffffe50aaefc4080.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: InstallManagerApp.exe

STACK_TEXT:
fffffc85`8d96b678 fffff804`0400a267 : 00000000`0000001a 00000000`00000031 ffffe50a`a9abb2b0 ffffce81`9e201000 : nt!KeBugCheckEx
fffffc85`8d96b680 fffff804`03e81ca0 : ffffce81`9e201000 ffffb98d`e82562a0 00000000`000011e3 00000000`00000000 : nt!MiApplyCompressedFixups+0x188447
fffffc85`8d96b6e0 fffff804`03e81a4d : ffffe50a`aefc4080 ffffe50a`a9abb2b0 00007ff6`b0600000 00000000`000011e3 : nt!MiPerformFixups+0x88
fffffc85`8d96b780 fffff804`03ac9ff0 : 00000000`00000000 00000000`0000000c 00000000`00000000 00000000`00000008 : nt!MiRelocateImagePfn+0x18d
fffffc85`8d96b7f0 fffff804`03ad0a24 : ffffe50a`00000000 00000000`00000000 00000000`00000000 ffffe50a`aee1d080 : nt!MiValidateInPage+0x260
fffffc85`8d96b8a0 fffff804`03ad0365 : fffffc85`00004000 fffffc85`8d96ba00 fffffc85`8d96ba30 fffff804`00000000 : nt!MiWaitForInPageComplete+0x314
fffffc85`8d96b990 fffff804`03a6e818 : 00000000`c0033333 00000000`00000001 00007ff8`317e22c8 ffffb98d`e737ef10 : nt!MiIssueHardFault+0x3c5
fffffc85`8d96baa0 fffff804`03c0b7d8 : ffffe50a`aefc4080 ffffe50a`00000000 00000000`00da7de4 ffffe50a`afd668f0 : nt!MmAccessFault+0x468
fffffc85`8d96bc40 00007ff8`3090510d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
000000d8`63d18a90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`3090510d

SYMBOL_NAME: nt!MiApplyCompressedFixups+188447

MODULE_NAME: nt.

IMAGE_VERSION: 10.0.19041.2965

STACK_COMMAND: .process /r /p 0xffffe50aaee1d080; .thread 0xffffe50aaefc4080 ; kb.

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 188447.

FAILURE_BUCKET_ID: 0x1a_31_nt!MiApplyCompressedFixups

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {c331f2d1-f573-4955-bed6-0e48314e3a31}

Followup: MachineOwner.
---------
 
Son düzenleyen: Moderatör:
Çözüm
4 RAM varsa tek tek test edin. Dilerim 1 tanesinde sorun vardır. Ve hatta RAM'leri tek tek çıkarıp Windows'u test etseniz de olur.
@goktug.59


 
@goktug.59


Dün akşamdan beri testte sanırım RAM bozuk baya hata verdi.

@turko35408 hocam peki hangi RAM arızalı görebilir miyiz Memtest ekranından? En son 22 tane hata vardı 33 tane hataya çıkınca kapattım fotoğraf çekmedim.


IMG_20241124_171127_602.jpg
 
Son düzenleme:
4 RAM varsa tek tek test edin. Dilerim 1 tanesinde sorun vardır. Ve hatta RAM'leri tek tek çıkarıp Windows'u test etseniz de olur.
Çok sağolun hocam. İnşallah tek modülde vardır problem. Bir kere Dolap'tan ağzımız yandı bir daha hayatta 2. el ürün almam.
 

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı