R5 7600x/6600XT sistemde mavi ekran hatası

İşletim sistemi
Windows 10

CKayraGocmen

Zeptopat
Katılım
29 Mayıs 2023
Mesajlar
2
Daha fazla  
Cinsiyet
Erkek
RAM
XPG 32GB (2x16GB) Lancer Siyah DDR5 6000MHz CL40 1.35V PC Ram
SSD veya HDD modeli
Firecuda M2 520gb
Ekran kartı
SAPPHIRE 6600XT
Anakart
Gigabyte B650M
İşlemci
Ryzen R5 7600X
Merhaba
Öncelikle forumda yeniyim.
Bilgisayar bazen takılıp kalıyor, sonrasında düzeliyor. Bir 5-6 saniyelik takılma yaşıyor(takılma donma olarak değil aşırı kasma anlamında takılma diyorum)
3-4 defada mavi ekran yedim rastgele bir şekilde kasmayla bağlantısı var mı bilmiyorum.
Daha yeni format atmıştım yüklemediğim driver olabilir veya hatalı driver.
Minidump dosyasına bakarsanız sevinirim.
Kolay gelsin iyi akşamlar.

Windows Mavi Ekran .rar - minidump dosyasını Google Drive olarak yükledim.
 
Son düzenleyen: Moderatör:
EasyAntiCheat'ten kaynaklı gibi görünüyor.

EasyAntiCheat'i silin, tamamen kalksın. Oyun dosyalarını doğrulayın ve tekrar yüklensin.

Bunun dışında 2 tane program görüyorum.

GVCIDrv64.sys
ALSysIO64.sys

Core Temp ve Gigabyte araçlarından biri. Mavi ekranlar çözülene kadar mümkün olduğunca kapalı kalsın üçüncü parti sürücüler. Daha sonra açarsınız.

BIOS eskimiş. Güncelleyebilirsiniz.
Rich (BB code):
BiosVersion = F3
BiosReleaseDate = 09/28/2022
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B650M DS3H
SystemFamily = B650 MB
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B650M DS3H



Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        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: fffffc8887b8fc48, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff801586df76e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 8000

    Key  : Analysis.Elapsed.mSec
    Value: 13249

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_EasyAntiCheat!unknown_function

    Key  : Failure.Hash
    Value: {de037a2f-1007-fb78-fc0b-814c5461dfd3}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: fffffc8887b8fc48

BUGCHECK_P2: 0

BUGCHECK_P3: fffff801586df76e

BUGCHECK_P4: 2

FILE_IN_CAB:  052823-6765-01.dmp

READ_ADDRESS: fffff80158afb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffffc8887b8fc48

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

TRAP_FRAME:  ffffee8b0f1d5c50 -- (.trap 0xffffee8b0f1d5c50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffffc8887b8fc rbx=0000000000000000 rcx=00000000000000fc
rdx=fffffc8887b8fc60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801586df76e rsp=ffffee8b0f1d5de8 rbp=ffffd683ce414040
 r8=0000000000000000  r9=fffffc8887b8fc30 r10=000000000003b438
r11=ffffee8b0f1d5e30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nt!ObpCaptureHandleInformation+0x8e:
fffff801`586df76e 410fb64118      movzx   eax,byte ptr [r9+18h] ds:fffffc88`87b8fc48=??
Resetting default scope

STACK_TEXT:
ffffee8b`0f1d59a8 fffff801`5824ac53     : 00000000`00000050 fffffc88`87b8fc48 00000000`00000000 ffffee8b`0f1d5c50 : nt!KeBugCheckEx
ffffee8b`0f1d59b0 fffff801`5806e7b0     : ffffee8b`0f1d5b30 00000000`00000000 ffffee8b`0f1d5cd0 00000000`00000000 : nt!MiSystemFault+0x1b2273
ffffee8b`0f1d5ab0 fffff801`5820b7d8     : ffffd683`00000000 00001f80`00000000 ad888d0b`fe80ffff ffffd683`ce414040 : nt!MmAccessFault+0x400
ffffee8b`0f1d5c50 fffff801`586df76e     : fffff801`5874f591 00000000`00001804 00000000`00000000 ffffad88`00000000 : nt!KiPageFault+0x358
ffffee8b`0f1d5de8 fffff801`5874f591     : 00000000`00001804 00000000`00000000 ffffad88`00000000 fffff801`58086632 : nt!ObpCaptureHandleInformation+0x8e
ffffee8b`0f1d5df0 fffff801`586df665     : fffff801`586df6e0 ffffd683`ce414058 ffffad88`00100000 ffffee8b`0f1d5f30 : nt!ExpSnapShotHandleTables+0x131
ffffee8b`0f1d5e80 fffff801`5874cc11     : ffffee8b`0f1d5f30 00000000`0003b438 00000000`00100000 00000000`00000000 : nt!ObGetHandleInformation+0x39
ffffee8b`0f1d5ec0 fffff801`5840918f     : ffffad88`8e1b0010 00000000`00000000 ffff8580`de731010 ffffad88`a28d86e0 : nt!ExpGetHandleInformation+0x5d
ffffee8b`0f1d5f00 fffff801`58407f17     : 00000000`00000000 00000000`00000080 00000000`00000000 00000000`00000000 : nt!ExpQuerySystemInformation+0x112f
ffffee8b`0f1d6240 fffff801`5820f4f8     : 00000000`00100000 fffff801`580127d0 ffffad88`8e1b0000 00000000`33314d43 : nt!NtQuerySystemInformation+0x37
ffffee8b`0f1d6280 fffff801`58200880     : fffff804`686468ad ffffad88`8e1b0010 00000000`01000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffffee8b`0f1d6418 fffff804`686468ad     : ffffad88`8e1b0010 00000000`01000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
ffffee8b`0f1d6420 ffffad88`8e1b0010     : 00000000`01000000 00000000`00000000 00000000`00000000 fffff801`587b7010 : EasyAntiCheat+0x468ad
ffffee8b`0f1d6428 00000000`01000000     : 00000000`00000000 00000000`00000000 fffff801`587b7010 fffff801`581f8830 : 0xffffad88`8e1b0010
ffffee8b`0f1d6430 00000000`00000000     : 00000000`00000000 fffff801`587b7010 fffff801`581f8830 ffffad88`9d3f2080 : 0x1000000


SYMBOL_NAME:  EasyAntiCheat+468ad

MODULE_NAME: EasyAntiCheat

IMAGE_NAME:  EasyAntiCheat.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  468ad

FAILURE_BUCKET_ID:  AV_R_(null)_EasyAntiCheat!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {de037a2f-1007-fb78-fc0b-814c5461dfd3}

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



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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80666c0f657, Address of the instruction which caused the BugCheck
Arg3: ffffbb81540a7920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4765

    Key  : Analysis.Elapsed.mSec
    Value: 10442

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemServiceExit

    Key  : Failure.Hash
    Value: {e3c619b5-09ee-208f-54b1-3554eb6fa478}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80666c0f657

BUGCHECK_P3: ffffbb81540a7920

BUGCHECK_P4: 0

FILE_IN_CAB:  052623-7671-01.dmp

CONTEXT:  ffffbb81540a7920 -- (.cxr 0xffffbb81540a7920)
rax=0000000000000000 rbx=0000000000000000 rcx=ffff910fc35e0080
rdx=000000007457624f rsi=0000001e603ff3d8 rdi=00000000000004d8
rip=fffff80666c0f657 rsp=ffff8085e6867480 rbp=ffff8085e6867500
 r8=0000000000000000  r9=0000000000000087 r10=0000000000000000
r11=ffff910fc35e0080 r12=0000000000000000 r13=0000000000000000
r14=00000000000004d8 r15=00000000ffffffff
iopl=0         nv up di pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050046
nt!KiSystemServiceExit+0x157:
fffff806`66c0f657 0fae55ac        ldmxcsr dword ptr [rbp-54h] ss:0018:ffff8085`e68674ac=0b001fa0
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  AMDRSServ.exe

STACK_TEXT:
ffff8085`e6867480 00007ffb`c640d0e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x157
0000001e`603ff3a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`c640d0e4


SYMBOL_NAME:  nt!KiSystemServiceExit+157

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr 0xffffbb81540a7920 ; kb

BUCKET_ID_FUNC_OFFSET:  157

FAILURE_BUCKET_ID:  AV_nt!KiSystemServiceExit

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3c619b5-09ee-208f-54b1-3554eb6fa478}

Followup:     MachineOwner
---------
 
EXCEPTION_ON_INVALID_STACK (1aa)

* Daha önce böyle bir bugcheck görmedim açıkçası. Forumda konuları açılmış ancak net bir çözüme rastlanılamamış. Neyin sebebiyet verdiğini bilmediğimiz için genel çözümler uygulayacağız, adım adım takip edin ve hepsinin sonucunu paylaşın lütfen. BIOS ve RAM'den şüpheleniyorum bu arada. Özellikle XMP ile çalıştırıyorsanız.

* BIOS hala güncel değil. En azından ihtimallerden birini elemiş olursunuz.

* Anakartınızın BIOS sayfasında RAM ve genel performans ile alakalı stabilite güncellemeleri geldiği yazıyor. Kullandığınız AM5 platformu yeni bir platform, bu yüzden kalite ve stabilite güncellemeleri alıyor hâlâ. BIOS güncellemeleri bu sebeple kritik.

Sizde F3 sürümü var.
Kod:
BiosVersion = F3
BiosReleaseDate = 09/28/2022
SystemManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B650M DS3H

* F6 sürümünü indirebilirsiniz.


* VIDEO: Gigabyte BIOS Güncelleme Rehberi



BIOS güncelledikten sonra devam edelim.

* Denetim masası > Program Ekle/Kaldır'da "AMD Chipset Software" varsa kaldırın.

* Sonra aşağıdaki linkten güncel chipset sürücünüzü indirin ve kurun.
* Windows 11 64-bit olacak.

B650 Drivers & Support


* Bu işlemlerden sonra CMD'yi yönetici olarak çalıştırıp sırayla aşağıdaki iki komutu girin
* Sonuçlarını paylaşın.

SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth


* SSD'nizin herhangi bir firmware güncellemesi var mı diye kontrol edin.
* Bu da önemli bir adım olabilir.
Rehber: Seagate Firecuda 510


* Aygıt yöneticisinde sarı ünlem işareti olan herhangi bir aygıt var mı?


* Bunlardan sonra hala mavi ekran alırsanız güncel dosyaları paylaşın.
* RAM testine doğru gidiyor olabiliriz.


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

EXCEPTION_ON_INVALID_STACK (1aa)
This BugCheck indicates that exception dispatch crossed over into an invalid
kernel stack.  This might indicate that the kernel stack pointer has become
corrupted during exception dispatch or unwind (e.g. due to stack corruption of
a frame pointer), or that a driver is executing off of a stack that is not a
legal kernel stack.
Arguments:
Arg1: 000000e02b4ff8a0, A pointer to the current stack.
Arg2: 0000000000000003, A normal kernel thread stack
Arg3: ffffe401e3890900, A pointer to the context record representing the context that was
    being unwound (or dispatched for an exception) when the invalid stack
    was encountered.
Arg4: ffffe285541b1a08, ExceptionRecord - Supplies an exception record representing the active
    exception that was being dispatched.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1702

    Key  : Analysis.Elapsed.mSec
    Value: 3297

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1aa

    Key  : Failure.Bucket
    Value: 0x1AA_nt!RtlpGetStackLimitsEx

    Key  : Failure.Hash
    Value: {a75f195a-d08e-20f7-b020-0d8ede2085b8}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  1aa

BUGCHECK_P1: e02b4ff8a0

BUGCHECK_P2: 3

BUGCHECK_P3: ffffe401e3890900

BUGCHECK_P4: ffffe285541b1a08

FILE_IN_CAB:  052923-7687-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  330475c985444e8b -- (.trap 0x330475c985444e8b)
Unable to read trap frame at 330475c9`85444e8b

STACK_TEXT:
ffffe401`e3890108 fffff807`4da7aa94     : 00000000`000001aa 000000e0`2b4ff8a0 00000000`00000003 ffffe401`e3890900 : nt!KeBugCheckEx
ffffe401`e3890110 fffff807`4da7a649     : ffffe285`541b2460 ffffe285`541b1a08 fffff807`4da3c529 fffff807`4d6ea6e0 : nt!RtlpGetStackLimitsEx+0x269884
ffffe401`e3890160 fffff807`4d8120c7     : ffffffff`ffffffff ffffe285`541b1ab0 ffffe285`541b1ab0 ffffe401`e3890900 : nt!RtlDispatchException+0x26c6b9
ffffe401`e38908d0 fffff807`4da2cab2     : 04703944`000000b2 2f761839`04753572 330475c9`85444e8b 0445b70f`4110ebc0 : nt!KiDispatchException+0x317
ffffe401`e3890fb0 fffff807`4da2ca80     : fffff807`4da410f5 ffffd28a`b1015f50 ffffd28a`00000000 ffffd28a`00000030 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffe285`541b18c8 fffff807`4da410f5     : ffffd28a`b1015f50 ffffd28a`00000000 ffffd28a`00000030 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffe285`541b18d0 fffff807`4da3c183     : 00000000`00000014 00000000`00000000 ffffe285`541b1b30 fffff807`4d8f3d59 : nt!KiExceptionDispatch+0x135
ffffe285`541b1ab0 fffff807`4da35967     : 00000000`00000000 fffff807`4d8f5a67 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x343
ffffe285`541b1c40 fffff807`4d8f5a67     : 00000000`00000000 00000000`00000000 00400000`000625e5 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffe285`541b1c50 fffff807`4d8f4ec1     : 1a000006`de1e6863 8a000008`29dad963 00000000`00000002 fffff807`4d8f4952 : nt!MiGetPage+0x257
ffffe285`541b1d70 fffff807`4d958287     : 00000000`00000004 ffffe285`541b20c9 00000000`00000000 00000000`0022efe0 : nt!MiGetPageChain+0x541
ffffe285`541b1fb0 fffff807`4d8f0893     : ffffe285`541b2260 ffffe285`541b2088 00000000`00000002 ffff8d80`00000001 : nt!MiCreateSharedZeroPages+0x87
ffffe285`541b2040 fffff807`4d8eec44     : ffffe285`541b2260 ffff9b84`dbce29c8 ffff9b84`dbce29c8 00000000`00000002 : nt!MiResolveDemandZeroFault+0x543
ffffe285`541b2130 fffff807`4d8ecff4     : ffffe285`541b2260 00000000`00000002 ffffe285`541b2238 ffffe285`00000000 : nt!MiResolveProtoPteFault+0x9d4
ffffe285`541b2200 fffff807`4d8eb2e2     : ffffd28a`c16d2780 00000000`00000004 00000000`c0000016 00000000`00000004 : nt!MiDispatchFault+0x1a4
ffffe285`541b2340 fffff807`4da3c529     : 00000000`00000000 ffffe285`541b24e0 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x152
ffffe285`541b2460 00007ff9`18600e99     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x369
000000e0`2b4ff8a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`18600e99


SYMBOL_NAME:  nt!RtlpGetStackLimitsEx+269884

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  269884

FAILURE_BUCKET_ID:  0x1AA_nt!RtlpGetStackLimitsEx

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a75f195a-d08e-20f7-b020-0d8ede2085b8}

Followup:     MachineOwner
---------
 
Son düzenleme:

Technopat Haberler

Yeni konular

Geri
Yukarı