3080 Sistemde "MEMORY_MANAGEMENT" hatası

2pactr

Hectopat
Katılım
24 Ekim 2015
Mesajlar
21
Ryzen 5900X.
MSI X570 Tomahawk Wi-Fi
EVGA RTX 3080 FTW 3
G.Skill Ripjaws DDR4 2400 C15D - 16 gvr ( CL-15-15-15-35 1.20v Intel XMP 2.0 ready )
Arctik Liquid Freezer II 360.
Thermaltake Toughpower Gold 750W.

Merhaba sistemim bu şekilde yeni topladım RAM-PSU- GPU ve SSD'ler eski sistemimde hatasız bir şekilde kullandığım parçalarım. Yeni sistemde de bunları kullanıyorum fakat sürekli mavi ekran MEMORY_MANAGEMENT hatası alıyorum.

Yaptıklarım.
SSD'ye temiz kurulum Windows yükleme.
Memtest 86 ile test ( error hata yok )
Windows bellek tesli ( hata yok )
BIOS güncel sürüm güncelleme.
Driverları kurma.

Ne yaparsam yapayım MEMORY_MANAGEMENT mavi ekran hatası almaya devam ediyorum. Yardımcı olursanız çok sevinirim.

 

PanzerTR

Megapat
Süper Moderatör
Katılım
29 Ocak 2019
Mesajlar
8.186
Makaleler
21
Çözümler
213
Yer
BTW
Gameloop kaldır.

BIOS sıfırlayın. Beta bir BIOS sürümündesiniz. Sorunun ana kaynağı bu olabilir.

F61 sürümünü kurun buradan.

 
KS
KS
2

2pactr

Hectopat
Katılım
24 Ekim 2015
Mesajlar
21
GameLoop kaldır.

BIOS sıfırlayın. Beta bir BIOS sürümündesiniz. Sorunun ana kaynağı bu olabilir.

F61 sürümünü kurun buradan.


Hocam BIOS beta sürümü vardı en son onu yüklemedim. Son güncel sürümü yükledim, beta değil. Attığınız gigagbyte B450 anakart nedır anlamadım onu. MSI X570 Tomahawk kullanıyorum ben.

10.0.22415 hangi Build bu tam olarak? Windows 11 mi kullanıyorsunuz?

Microsoft'tan güncel Windows 10'u indirdim.
GameLoop dediğiniz şeyi bilmiyorum. Control Panel'de yok öyle bir şey. Aratınca Google'da PUBG ile alakalı bir şey çıkıyor.
Version.
7C84V17.
Release date.
2021-07-06
File size.
17.3 MB.

MSI'ın sitesindeki en güncel BIOS bu ( beta hariç ). Bunu yükledim bende.
 
Son düzenleyen: Moderatör:

PanzerTR

Megapat
Süper Moderatör
Katılım
29 Ocak 2019
Mesajlar
8.186
Makaleler
21
Çözümler
213
Yer
BTW
MSI X570 Tomahawk kullanıyorum ben.
Yanlış dump yüklenmiş o halde.

Kod:
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends International, LLC.
BiosVersion = F62b
BiosReleaseDate = 09/06/2021
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M S2H
SystemFamily = B450 MB
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B450M S2H
BaseBoardVersion = x.x
 
KS
KS
2

2pactr

Hectopat
Katılım
24 Ekim 2015
Mesajlar
21
Kod:
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends International, LLC.
BiosVersion = F62b
BiosReleaseDate = 09/06/2021
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M S2H
SystemFamily = B450 MB
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B450M S2H
BaseBoardVersion = x.x
Niye öyle gösteriyor anlamadım
Microsoft (R) Windows Debugger Version 10.0.22415.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Desktop\Minidump\101621-7625-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`28e00000 PsLoadedModuleList = 0xfffff803`29a2a270
Debug session time: Sat Oct 16 05:37:08.537 2021 (UTC + 3:00)
System Uptime: 0 days 0:22:49.141
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`291f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9e8b`1f9572f0=000000000000001a
18: 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: ffff9b011c62a988
Arg3: 4000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1968

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 11990

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

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

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

Key : MemoryManagement.PFN
Value: 0

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

BUGCHECK_P3: 4000000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffff9e8b`1f9572e8 fffff803`290440ca : 00000000`0000001a 00000000`00041792 ffff9b01`1c62a988 40000000`00000000 : nt!KeBugCheckEx
ffff9e8b`1f9572f0 fffff803`290428ff : ffffdc8a`bdd79740 00000000`00000000 ffff9b01`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
ffff9e8b`1f9573f0 fffff803`29012aa0 : 00000000`00000001 ffff9e8b`00000000 ffffdc8a`bdd79590 ffffdc8a`bc599080 : nt!MiDeletePagablePteRange+0x48f
ffff9e8b`1f957700 fffff803`294007f3 : ffffdc8a`bc599080 00000000`00000000 ffffdc8a`00000000 ffffdc8a`00000000 : nt!MiDeleteVad+0x360
ffff9e8b`1f957810 fffff803`293feaaf : ffffdc8a`bdf9c5c0 ffffdc8a`bdf9c5c0 ffffdc8a`bd620b90 ffffdc8a`bdd790c0 : nt!MiCleanVad+0x43
ffff9e8b`1f957840 fffff803`2945c5a8 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffdc8a`bdd790c0 : nt!MmCleanProcessAddressSpace+0x137
ffff9e8b`1f9578c0 fffff803`294b0ab6 : ffffdc8a`bdd790c0 ffffcb09`1873f060 00000000`00000000 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffff9e8b`1f957950 fffff803`294b401e : ffffdc8a`00000000 00000000`00000001 00000000`00000000 00000054`f8368000 : nt!PspExitThread+0x5f6
ffff9e8b`1f957a50 fffff803`29208bb8 : ffffdc8a`bdd790c0 ffffdc8a`bc599080 ffff9e8b`1f957b40 ffff9e8b`1f957b40 : nt!NtTerminateProcess+0xde
ffff9e8b`1f957ac0 00007ff8`7962d2f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000054`f816fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`7962d2f4


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

18: 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: ffff9b011c62a988
Arg3: 4000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1640

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2725

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

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

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

Key : MemoryManagement.PFN
Value: 0

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

BUGCHECK_P3: 4000000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffff9e8b`1f9572e8 fffff803`290440ca : 00000000`0000001a 00000000`00041792 ffff9b01`1c62a988 40000000`00000000 : nt!KeBugCheckEx
ffff9e8b`1f9572f0 fffff803`290428ff : ffffdc8a`bdd79740 00000000`00000000 ffff9b01`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
ffff9e8b`1f9573f0 fffff803`29012aa0 : 00000000`00000001 ffff9e8b`00000000 ffffdc8a`bdd79590 ffffdc8a`bc599080 : nt!MiDeletePagablePteRange+0x48f
ffff9e8b`1f957700 fffff803`294007f3 : ffffdc8a`bc599080 00000000`00000000 ffffdc8a`00000000 ffffdc8a`00000000 : nt!MiDeleteVad+0x360
ffff9e8b`1f957810 fffff803`293feaaf : ffffdc8a`bdf9c5c0 ffffdc8a`bdf9c5c0 ffffdc8a`bd620b90 ffffdc8a`bdd790c0 : nt!MiCleanVad+0x43
ffff9e8b`1f957840 fffff803`2945c5a8 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffdc8a`bdd790c0 : nt!MmCleanProcessAddressSpace+0x137
ffff9e8b`1f9578c0 fffff803`294b0ab6 : ffffdc8a`bdd790c0 ffffcb09`1873f060 00000000`00000000 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffff9e8b`1f957950 fffff803`294b401e : ffffdc8a`00000000 00000000`00000001 00000000`00000000 00000054`f8368000 : nt!PspExitThread+0x5f6
ffff9e8b`1f957a50 fffff803`29208bb8 : ffffdc8a`bdd790c0 ffffdc8a`bc599080 ffff9e8b`1f957b40 ffff9e8b`1f957b40 : nt!NtTerminateProcess+0xde
ffff9e8b`1f957ac0 00007ff8`7962d2f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000054`f816fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`7962d2f4


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

PanzerTR

Megapat
Süper Moderatör
Katılım
29 Ocak 2019
Mesajlar
8.186
Makaleler
21
Çözümler
213
Yer
BTW
Ben mi yanlış dosyaya bakıyorum acaba.

Neyse belleklerinizi XMP kapatarak test ediniz.
 
KS
KS
2

2pactr

Hectopat
Katılım
24 Ekim 2015
Mesajlar
21
Ben mi yanlış dosyaya bakıyorum acaba.

Neyse belleklerinizi XMP kapatarak test ediniz.

XMP kapalı şekilde test ettim hocam. Dediğim gibi bir error vermedi.
 
Son düzenleyen: Moderatör:

Yeni konular

Yukarı