Çözüldü Windows 11 mavi ekran hataları

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

TRaceurh

Picopat
Katılım
13 Temmuz 2022
Mesajlar
6
Daha fazla  
Cinsiyet
Erkek
RAM
G SKILL 16GB 3200 MHZ
SSD veya HDD modeli
SAMSUNG SSD 860 EVO M.2 500GB
Ekran kartı
ASUS ROG rx 580
Anakart
B450 AORUS pro
İşlemci
AMD ryzen 7 2700x
Merhaba. Windows 11 kullanıcısıydım normal kullanırken sıkıntı vermeyen bilgisayarım oyun açtığımda FPS düşmesi yaşayarak anlık donmalar takibinde mavi ekran hatası alıyordu ağırlıklı olarak MEMORY_MANAGEMENT hatasıyla karşılaşıyordum. Windows 10'a geri yükleme yaptım bir süre sonra hataları almaya devam etmeye başladım. Memtest86 testinde hata bulunamadı ekran kartımı 10 saat teste tabii tuttum donma hata ile karşılaşmadım. CMD ile SFC /scannow kodlarını denedim hata devam ediyor. İşin içinden çıkamıyorum her seferinde farklı bir hata almaya başladım. XMP'yi kapatıp açtım ama hala devam etmekte. Rica etsem yardımcı olabilir misiniz?

Minidump: mini.rar
 
Son düzenleyen: Moderatör:
Merhaba, paylaştığınız dosyada hiçbir şey yok. Lütfen minidump dosyalarını doğru şekilde yükleyip paylaşınız.
 
Analizimi yaptım ve sorunun kaynağı Samsung 860 Evo SSD diskiniz gibi. Diskin yuvaya oturduğundan eminseniz ve Samsung Magician ile de sağlık kontrolü yaptıysanız en iyisi diski garantiye yollayın derim. Sonucu bekliyor olacağım. :)

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffad8b4d6b40e0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3515

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 33902

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x7a

    Key  : Bugcheck.Code.Register
    Value: 0x7a

    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:  071322-6937-01.dmp

BUGCHECK_CODE:  7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffad8b4d6b40e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffffc06`b7db15e8 fffff807`7cc527e8     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffad8b`4d6b40e0 : nt!KeBugCheckEx
fffffc06`b7db15f0 fffff807`7cb572eb     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x193258
fffffc06`b7db16a0 fffff807`7ca39d20     : ffffad8b`4d6b5080 ffffad8b`5433e088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
fffffc06`b7db16d0 fffff807`7ca37bb7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
fffffc06`b7db1780 fffff807`7ca36dbf     : 00000000`00000005 00000000`0000000c fffffc06`b7db1970 00000000`00000000 : nt!KiSwapThread+0x827
fffffc06`b7db1830 fffff807`7ca439de     : 00000000`00000000 fffff807`00000000 00000000`02000100 00000000`00000000 : nt!KiCommitThreadWait+0x14f
fffffc06`b7db18d0 fffff807`7cbbd07e     : ffffad8b`00000004 fffff807`00000012 fffff807`7d450b00 ffff8000`1179f180 : nt!KeWaitForMultipleObjects+0x2be
fffffc06`b7db19e0 fffff807`7cb4edc5     : ffffad8b`4d6b5080 ffffad8b`4d6b5080 00000000`00000080 fffff807`7cbbcee0 : nt!MiModifiedPageWriter+0x19e
fffffc06`b7db1c10 fffff807`7cbffbe8     : ffff8000`11580180 ffffad8b`4d6b5080 fffff807`7cb4ed70 000001f5`000000f9 : nt!PspSystemThreadStartup+0x55
fffffc06`b7db1c60 00000000`00000000     : fffffc06`b7db2000 fffffc06`b7dac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiWriteComplete+193258

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.1826

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  193258

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWriteComplete

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

3: kd> !blackboxpnp
    PnpActivityId      : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime    : 133021780869741984
    PnpEventInformation: 3
    PnpEventInProgress : 1
    PnpProblemCode     : 24
    PnpVetoType        : 0
    DeviceId           : SCSI\Disk&Ven_Samsung&Prod_SSD_860_EVO_M.2\5&2e701078&0&030000
    VetoString         :
 
Analizimi yaptım ve sorunun kaynağı Samsung 860 EVO SSD diskiniz gibi. Diskin yuvaya oturduğundan eminseniz ve Samsung Magician ile de sağlık kontrolü yaptıysanız en iyisi diski garantiye yollayın derim. Sonucu bekliyor olacağım. :)

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffad8b4d6b40e0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 3515

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 33902

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x7a

 Key : Bugcheck.Code.Register
 Value: 0x7a

 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: 071322-6937-01.dmp

BUGCHECK_CODE: 7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffad8b4d6b40e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffc06`b7db15e8 fffff807`7cc527e8 : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffad8b`4d6b40e0 : nt!KeBugCheckEx
fffffc06`b7db15f0 fffff807`7cb572eb : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x193258
fffffc06`b7db16a0 fffff807`7ca39d20 : ffffad8b`4d6b5080 ffffad8b`5433e088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
fffffc06`b7db16d0 fffff807`7ca37bb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
fffffc06`b7db1780 fffff807`7ca36dbf : 00000000`00000005 00000000`0000000c fffffc06`b7db1970 00000000`00000000 : nt!KiSwapThread+0x827
fffffc06`b7db1830 fffff807`7ca439de : 00000000`00000000 fffff807`00000000 00000000`02000100 00000000`00000000 : nt!KiCommitThreadWait+0x14f
fffffc06`b7db18d0 fffff807`7cbbd07e : ffffad8b`00000004 fffff807`00000012 fffff807`7d450b00 ffff8000`1179f180 : nt!KeWaitForMultipleObjects+0x2be
fffffc06`b7db19e0 fffff807`7cb4edc5 : ffffad8b`4d6b5080 ffffad8b`4d6b5080 00000000`00000080 fffff807`7cbbcee0 : nt!MiModifiedPageWriter+0x19e
fffffc06`b7db1c10 fffff807`7cbffbe8 : ffff8000`11580180 ffffad8b`4d6b5080 fffff807`7cb4ed70 000001f5`000000f9 : nt!PspSystemThreadStartup+0x55
fffffc06`b7db1c60 00000000`00000000 : fffffc06`b7db2000 fffffc06`b7dac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!MiWriteComplete+193258

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.1826

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 193258

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWriteComplete

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

3: kd> !blackboxpnp
 PnpActivityId : {00000000-0000-0000-0000-000000000000}
 PnpActivityTime : 133021780869741984
 PnpEventInformation: 3
 PnpEventInProgress : 1
 PnpProblemCode : 24
 PnpVetoType : 0
 DeviceId : SCSI\Disk&Ven_Samsung&Prod_SSD_860_EVO_M.2\5&2e701078&0&030000
 VetoString :
Genele olarak good gösteriyor
 

Dosya Ekleri

  • ssd.png
    ssd.png
    23 KB · Görüntüleme: 31
Yine de hata ondan kaynaklı görünmekte. İmkanınız varsa gönderin derim.

Dediğiniz gibi SSD'yi çıkardım taktım sorun devam etti. Ama hata kodları bu sefer voltaj kesilmesiyle alakalıydı. CPU clock ratio Auto'ya almış manuele aldım sorunum çözüldü, teşekkür ederim.
 
Son düzenleyen: Moderatör:

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı