BIOS sürümünüz
F50 sürümü, lütfen onu
F52 sürümüne yükseltin.
F52 sürümlü BIOS'un dosyasını aşağıdan indirebilirsiniz.
Ayrıca sorun XMP kaynaklı da olabilir. XMP kapatınca sorun çözülürse bırakın test yapmaya gerek yok ama XMP kapalı olmasına rağmen sorun devam ederse Memtest86 testini uygulamak zorunda kalırsınız.
[CODE title="Dökümler"]Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO48E3F47D\021821-11343-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 = 0xfffff804`32200000 PsLoadedModuleList = 0xfffff804`32e2a390
Debug session time: Thu Feb 18 22:04:38.481 2021 (UTC + 3:00)
System Uptime: 0 days 1:58:30.126
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`325f5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffcd81`9e028960=000000000000001a
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 00007ff779bb4440
Arg3: 000000000000000d
Arg4: ffffcd819e028b00
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6671
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 13391
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1a
BUGCHECK_P1: 61941
BUGCHECK_P2: 7ff779bb4440
BUGCHECK_P3: d
BUGCHECK_P4: ffffcd819e028b00
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: VALORANT-Win64-Shipping.exe
STACK_TEXT:
ffffcd81`9e028958 fffff804`32618a84 : 00000000`0000001a 00000000`00061941 00007ff7`79bb4440 00000000`0000000d : nt!KeBugCheckEx
ffffcd81`9e028960 fffff804`32603c5e : 000001fd`df1df100 ffff9b09`2b220e60 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x20c524
ffffcd81`9e028b00 00007ff7`7580a2cf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000074`a9c9fb90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`7580a2cf
MODULE_NAME: hardware
IMAGE_NAME: hardware_ram
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}
Followup: MachineOwner
---------[/CODE]
Neden olmasın? İşlemciye çok yük binerse ve işlemci kendini kilitlerse mavi ekran alabilirsiniz. Uyumlu bir donanım seçmek önemli ama bu sistemde ben pek bir darboğaz göremiyorum açıkçası.