KERNEL_DATA_INPAGE_ERROR (7a) Mavi ekran hatası

Bro4ken

Hectopat
Katılım
4 Temmuz 2014
Mesajlar
2
Daha fazla  
Cinsiyet
Erkek
Merhabalar son 1 haftadır mavi ekran yemeye başladım. Gördüğüm kadarıyla Windows'un son güncellemesi KB4566782 mavi ekrana sebep oluyormuş. Güncellemeyi kaldırdım ama halen şüpheliyim. Rica etsem Minidump dosyasını inceler misiniz?

 
Son düzenleyen: Moderatör:
HD Tune Pro ile quick scan kapalı şekilde error scan yapın, CrystalDiskMark ile Yazma/Okuma testi yapıp sonuçları paylaşın.

CMD'yi yönetici olarak başlatıp chkdsk /f /r komutunu girin, Y/N seçeneğinde Y'yi seçin.

Kod:
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: ffffe58e939de0e0, 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: 6311

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-74VRRQ7

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14265

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

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

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffe58e939de0e0

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:
ffffaf06`1ea145e8 fffff804`78c726de     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffe58e`939de0e0 : nt!KeBugCheckEx
ffffaf06`1ea145f0 fffff804`78b4e1db     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x16870e
ffffaf06`1ea146a0 fffff804`78a2a230     : ffffe58e`939df080 ffffe58e`a5fcbc18 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffaf06`1ea146d0 fffff804`78a280c7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
ffffaf06`1ea14780 fffff804`78a272cf     : 00000000`0000000a 00000000`00000001 ffffaf06`1ea14970 fffff804`00000000 : nt!KiSwapThread+0x827
ffffaf06`1ea14830 fffff804`78a31e6e     : 00000000`00000000 fffff804`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffaf06`1ea148d0 fffff804`78ba966e     : ffffe58e`00000004 fffff804`00000012 fffff804`79450ac0 ffffd580`a4d03180 : nt!KeWaitForMultipleObjects+0x2be
ffffaf06`1ea149e0 fffff804`78b46745     : ffffe58e`939df080 ffffe58e`939df080 00000000`00000080 fffff804`78ba94d0 : nt!MiModifiedPageWriter+0x19e
ffffaf06`1ea14c10 fffff804`78be5598     : ffffd580`a4d03180 ffffe58e`939df080 fffff804`78b466f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffaf06`1ea14c60 00000000`00000000     : ffffaf06`1ea15000 ffffaf06`1ea0f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiWriteComplete+16870e

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  16870e

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
---------
 
Güncellemeyi kaldırınca sorun çözüldü mü? Çözülmediyse:
ASUS araçlarını, RGB araçlarını, CPUZ, Apple yazılımlarını kaldırın.
Klavye ve fare harici USB takılı olmasın.
DDU rehberini uygulayıp güncel GPU sürücünüzü yükleyin. Berkay'ın dediğini de yapın eğer SSD değilse, SSD ise Crystal olanı yapın.
 
Güncellemeyi kaldırınca sorun çözüldü mü? Çözülmediyse:
ASUS araçlarını, RGB araçlarını, CPU-Z, Apple yazılımlarını kaldırın.
Klavye ve fare harici USB takılı olmasın.
DDU rehberini uygulayıp güncel GPU sürücünüzü yükleyin. Berkay'ın dediğini de yapın eğer SSD değilse, SSD ise Crystal olanı yapın.

Şu an bir sorun yok gibi duruyor ama yukarıdaki hocamın istediği testleri yapıyorum bakalım ne olacak.
HD Tune Pro ile quick scan kapalı şekilde error scan yapın, CrystalDiskMark ile Yazma/Okuma testi yapıp sonuçları paylaşın.

CMD'yi yönetici olarak başlatıp chkdsk /f /r komutunu girin, Y/N seçeneğinde Y'yi seçin.

Kod:
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: ffffe58e939de0e0, 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: 6311

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-74VRRQ7

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14265

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

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

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffe58e939de0e0

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:
ffffaf06`1ea145e8 fffff804`78c726de     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffe58e`939de0e0 : nt!KeBugCheckEx
ffffaf06`1ea145f0 fffff804`78b4e1db     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x16870e
ffffaf06`1ea146a0 fffff804`78a2a230     : ffffe58e`939df080 ffffe58e`a5fcbc18 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffaf06`1ea146d0 fffff804`78a280c7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
ffffaf06`1ea14780 fffff804`78a272cf     : 00000000`0000000a 00000000`00000001 ffffaf06`1ea14970 fffff804`00000000 : nt!KiSwapThread+0x827
ffffaf06`1ea14830 fffff804`78a31e6e     : 00000000`00000000 fffff804`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffaf06`1ea148d0 fffff804`78ba966e     : ffffe58e`00000004 fffff804`00000012 fffff804`79450ac0 ffffd580`a4d03180 : nt!KeWaitForMultipleObjects+0x2be
ffffaf06`1ea149e0 fffff804`78b46745     : ffffe58e`939df080 ffffe58e`939df080 00000000`00000080 fffff804`78ba94d0 : nt!MiModifiedPageWriter+0x19e
ffffaf06`1ea14c10 fffff804`78be5598     : ffffd580`a4d03180 ffffe58e`939df080 fffff804`78b466f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffaf06`1ea14c60 00000000`00000000     : ffffaf06`1ea15000 ffffaf06`1ea0f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiWriteComplete+16870e

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  16870e

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
---------
Merhaba hocam tüm testleri yaptım makine 2 normal ssd 1 tane m2ssd 1 tanede normat 1tb hd var tüm testleri atıyorum
 

Dosya Ekleri

  • 1.png
    1.png
    24,7 KB · Görüntüleme: 53
  • 2.png
    2.png
    25,1 KB · Görüntüleme: 56
  • 3.png
    3.png
    24,9 KB · Görüntüleme: 52
  • 4.png
    4.png
    24,3 KB · Görüntüleme: 56
  • 11.png
    11.png
    42,4 KB · Görüntüleme: 50
  • 22.png
    22.png
    42,1 KB · Görüntüleme: 57
  • 33.png
    33.png
    75,3 KB · Görüntüleme: 61
  • 44.png
    44.png
    47,6 KB · Görüntüleme: 64
Son düzenleme:
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı