RX 5600XT EVO sistem açılırken mavi ekran göstermeyip kapanıyor

İşletim sistemi
Windows 10

RdAhmet

Decapat
Katılım
15 Kasım 2021
Mesajlar
197
Daha fazla  
Cinsiyet
Erkek
RAM
2x GSKILL 8GB Ripjaws V Siyah 3200MHz CL16 DDR4 Single Kit Ram
SSD veya HDD modeli
Kioxia 500GB Exceria Serisi NVMe M.2 SSD
Ekran kartı
Asus TUF RX 5600XT EVO
Anakart
Asus Prime B450M-K
İşlemci
Ryzen 5 3600
Son 10 gün içerisinde 5 tane mavi ekran yemişim. Arada bir bilgisayar böyle kafasına göre mavi ekran veriyor. Rica etsem yardımcı olabilir misiniz?

Minidump dosyaları
 
BIOS güncelleyin.


Tüm sürücülerinizi güncelleyin.


sfc/scannow komutunu kullanın.

SteelSeries ile alakalı sürücüleri kaldırın.

Minidump dosyasını analiz ederek sorunu buldum: Samsung'un NVMe sürücüsü!

Özellikle ilk rapora bakarsanız zaten secnvme.sys dosyasını görebilirsiniz.

Çözüm: NVMe sürücüsünün sorun yaratıyor, sürücüyü güncelleyin.

Samsung Magician & SSD Tools & Software Update | Samsung Semiconductor Global

Sorun devam ederse sürücüyü kaldırın.

Sorununuz çözülmüş olmalı bu adımları yaptıktan sonra lütfen bildirin.

Kod:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.
Arg2: 000000000000000a
Arg3: 0000000000004255, Incorrect checksum
Arg4: 000000000000b537, Previous disk read's checksum

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3109

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7246

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa0

    Key  : Bugcheck.Code.Register
    Value: 0xa0

    Key  : Dump.Attributes.AsUlong
    Value: 9

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  042923-10296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: 10e

BUGCHECK_P2: a

BUGCHECK_P3: 4255

BUGCHECK_P4: b537

ERROR_CODE: (NTSTATUS) 0xa - Ortam ge ersiz.

IMAGE_NAME:  stornvme.sys

MODULE_NAME: stornvme

FAULTING_MODULE: fffff8003f3c0000 stornvme

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
ffffc58c`c867d648 fffff800`3cfa6dd2     : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`00004255 : nt!KeBugCheckEx
ffffc58c`c867d650 fffff800`3cfb4a31     : 00000000`00000001 ffff830f`2f99bb90 00000001`71d04000 ffff830f`4cafd000 : nt!PopHiberChecksumHiberFileData+0xfb72
ffffc58c`c867d6b0 fffff800`3cfa63ab     : 00000000`00000000 ffff9908`6d135f38 00000000`00000001 00000000`00000001 : nt!PopRequestRead+0x7d
ffffc58c`c867d720 fffff800`3cf96371     : 00003f17`deef4e26 ffff9908`6d135f38 ffffc58c`c867d940 00000000`00000000 : nt!PopRestoreHiberContext+0xfe63
ffffc58c`c867d7b0 fffff800`3cf9608a     : fffff800`3d250560 ffffc58c`c867d930 fffff800`3d250560 00000000`00000100 : nt!PopHandleNextState+0x241
ffffc58c`c867d800 fffff800`3cf95e07     : 00000000`00000100 fffff800`3d250560 0000002c`d5cb4ad9 00000000`00989680 : nt!PopIssueNextState+0x1a
ffffc58c`c867d830 fffff800`3cf99499     : 00000000`00000015 ffffc58c`c867db40 00000000`00000000 fffff800`3cf9921f : nt!PopInvokeSystemStateHandler+0x33b
ffffc58c`c867da30 fffff800`3cf98e3a     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
ffffc58c`c867daf0 fffff800`3cf98b25     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MmDuplicateMemory+0x2be
ffffc58c`c867db80 fffff800`3c9265f5     : ffff830f`3fe09000 ffff830f`3fe09040 fffff800`3cf989f0 00000000`00000000 : nt!PopTransitionToSleep+0x135
ffffc58c`c867dc10 fffff800`3ca04848     : ffffd281`9e336180 ffff830f`3fe09040 fffff800`3c9265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffc58c`c867dc60 00000000`00000000     : ffffc58c`c867e000 ffffc58c`c8678000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


IMAGE_VERSION:  10.0.19041.2728

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0xa0_10e_0xa_HIBERSTACK_INIT_FAILED_IMAGE_stornvme.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5bbb5214-9d0b-5c7e-b2af-cfd7d39c2848}

Followup:     MachineOwner
---------
 
Hocam öncelikle yardımınız için teşekkürler. Önceden de tüm sürücülerim güncel iken mavi ekran yiyordum. Bilgisayara çok kez format attım, kaç kere format attığımı hatırlayamıyorum bile o kadar fazla. Bir de tek sorun bu sisteme hiç Samsung SSD takmamış olmam :D
 
Hocam öncelikle yardımınız için teşekkürler. Önceden de tüm sürücülerim güncel iken mavi ekran yiyordum. Bilgisayara çok kez format attım, kaç kere format attığımı hatırlayamıyorum bile o kadar fazla. Bir de tek sorun bu sisteme hiç Samsung SSD takmamış olmam :D

Şimdi şöyle hocam NVMe SSD olarak ne kullanıyorsanız onun sürücüsünü indirin. Samsung sanmıştım diye referans olarak verdim örneğin; Kingston kullanıyorsan onun sürücüsünü güncelle. Ayrıca önceki mavi ekranlarını bilemem ben gördüğüm dump dosyasına göre çözüm sunuyorum.
 
Daha yeni bilgisayarı açarken yine mavi ekran yedim. Sanırım ekran kartında veya RAM'lerde sorun var.

Minidump:



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


Loading Dump File [C:\Users\Arda\Desktop\050323-11781-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`66800000 PsLoadedModuleList = 0xfffff805`6742a2d0
Debug session time: Wed May 3 19:27:44.331 2023 (UTC + 3:00)
System Uptime: 1 days 19:24:38.779
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`66bfbc10 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8200`564c95e0=00000000000000be
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff0060babf268, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffff8200564c97d0, (reserved)
Arg4: 000000000000000a, (reserved)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5264

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 13406

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0xbe

Key : Bugcheck.Code.Register
Value: 0xbe

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


FILE_IN_CAB: 050323-11781-01.dmp

BUGCHECK_CODE: be

BUGCHECK_P1: fffff0060babf268

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: ffff8200564c97d0

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: LogonUI.exe

TRAP_FRAME: ffff8200564c97d0 -- (.trap 0xffff8200564c97d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=8000000000000013
rdx=3fffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80566d56d0a rsp=ffff8200564c9960 rbp=ffff8200564c9a49
r8=fffff00001b1a5b0 r9=fffff80567450c80 r10=ffff948000000000
r11=ffff8200564c9bf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiBuildForkPte+0x62e:
fffff805`66d56d0a f0490fba6d183f lock bts qword ptr [r13+18h],3Fh ds:00000000`00000018=????????????????
Resetting default scope

STACK_TEXT:
ffff8200`564c95d8 fffff805`66c69ee4 : 00000000`000000be fffff006`0babf268 8a000000`00200121 ffff8200`564c97d0 : nt!KeBugCheckEx
ffff8200`564c95e0 fffff805`66a6e89f : 8a000000`00200121 00000000`00000003 ffff8200`564c9850 00000000`00000000 : nt!MiRaisedIrqlFault+0x163c6c
ffff8200`564c9630 fffff805`66c0b6d8 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff805`66b209cc : nt!MmAccessFault+0x4ef
ffff8200`564c97d0 fffff805`66d56d0a : 00000203`e3fb7025 ffff8200`00000000 ffff9a89`94348220 ffffc60e`f4c1f700 : nt!KiPageFault+0x358
ffff8200`564c9960 fffff805`66d57bf3 : ffffc60f`08a5e080 ffffc60e`f4c1f0c0 ffff94bf`fc0e9228 fffff000`0980a8a0 : nt!MiBuildForkPte+0x62e
ffff8200`564c9a90 fffff805`670dbb31 : ffffc60f`08a5e080 ffff8200`564c9d99 ffffc60e`f4c1f0c0 ffffc60e`f4c1f0c0 : nt!MiCloneVads+0x4ab
ffff8200`564c9d20 fffff805`6702aec7 : 00000000`00000000 ffff8200`00000000 00000000`00000000 00000000`00000000 : nt!MiCloneProcessAddressSpace+0x261
ffff8200`564c9e00 fffff805`66e979b7 : 00000000`00002ab1 ffff8200`564cab80 00000000`00000000 00000000`00000000 : nt!MmInitializeProcessAddressSpace+0x13c413
ffff8200`564c9ff0 fffff805`66fca3d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateProcess+0x1d13
ffff8200`564ca760 fffff805`67109875 : ffff6816`74df95ea ffff6816`74df944a 00000000`00000000 00000000`00000000 : nt!PspCreateProcess+0x242
ffff8200`564caa30 fffff805`66c0f3f8 : 00000000`00000000 00000000`00000000 00000000`77566d4d ffff8200`564caae8 : nt!NtCreateProcessEx+0x85
ffff8200`564caa90 00007ff8`23d2da04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a5`9887f338 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`23d2da04


SYMBOL_NAME: nt!MiRaisedIrqlFault+163c6c

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.2846

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 163c6c

FAILURE_BUCKET_ID: AV_nt!MiRaisedIrqlFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5}

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

Geri
Yukarı