Çözüldü Seagate 1 TB HDD KERNEL_DATA_INPAGE_ERROR hatası

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

utkuaydin12

Megapat
Katılım
11 Aralık 2016
Mesajlar
232
Daha fazla  
Cinsiyet
Erkek
Merhabalar, son 2 aydır 1.5 yıldır kullandığım hard diskim ile fazlaca sorun yaşamaya başladım.
Ne zaman Hard Diskimde olan bir oyuna girmeye çalışsam ya oyunda, ya yükleme ekranında, ya da oyun kapanırken mavi ekran ve bu hatayı alıyorum. Bazenleri diskteki oyun dosyaları siliniyordu.
Ayrıca diske indirme yaparken de Windows kısa aralıklar ile donuyor, fare hareket etmiyor. Uzun donarsa ya bilgisayar kapanıyordu ya da mavi ekran alıyordum. Mavi ekran alınca da minidump oluşmuyordu, hep hatayı aldığım için
beklemiyordum da.

Bugün bekledim ve oluştu.
Minidump
Minidump'ı inceleyebilirseniz sevinirim, diskteki hata kesinse garantiye göndereceğim.

Hard Disk Sentinel:
1619900209783.png
Crystal Disk Info: (Okuma hatası oranı yüksek geldi ondan da şüpheleniyorum)
1619900499337.png
Konuyu hazırlarken HD Tune ile sağlık taraması yapıyordum fakat o sırada yine aynı hata ile mavi ekran aldım.
Windows bellek tanılama da yapmıştım, sorun bulmadı.
 
Çözüm
Bora Dere
Gerek dosyanın, gerek konuda yazdıklarınızın her yeri HDD sorunu kokuyor. Sisteminizden çıkarın diski, sorun çözülmeli.

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: ffffb38fd28c00e0, 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 partmgr.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5389

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25206

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

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

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

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


BUGCHECK_CODE:  7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffb38fd28c00e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

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: 
fffffd06`789414f8 fffff806`1e637a63     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffb38f`d28c00e0 : nt!KeBugCheckEx
fffffd06`78941500 fffff806`1e5300eb     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x156d13
fffffd06`789415b0 fffff806`1e452b4d     : ffffb38f`d28c2080 ffffb38f`dc01c088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
fffffd06`789415e0 fffff806`1e477502     : fffff806`1e360f00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x19d
fffffd06`789416a0 fffff806`1e40656d     : ffff9b01`df19d180 ffffb38f`d28c00e0 ffff9b01`df19d101 fffff806`21c3572b : nt!KiExitDispatcher+0x282
fffffd06`78941700 fffff806`1e476d5f     : fffffd06`78941800 ffffb38f`dc01c010 ffffb38f`d283ed01 ffffb38f`00000001 : nt!KeInsertQueueApc+0x14d
fffffd06`789417a0 fffff806`1e475f77     : 00000000`00000000 00000000`00000001 fffff806`1e360f10 fffff806`1e35d8f8 : nt!IopfCompleteRequest+0xdcf
fffffd06`789418b0 fffff806`20fcb778     : 00000000`00000000 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 : nt!IofCompleteRequest+0x17
fffffd06`789418e0 00000000`00000000     : 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 fffff806`20fc1540 : partmgr+0xb778


SYMBOL_NAME:  partmgr+b778

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b778

FAILURE_BUCKET_ID:  0x7a_c000000e_partmgr!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b4acaf9d-6a81-b42b-3866-20c206a01a65}

Followup:     MachineOwner
---------
Tarihe göre sırala Puana göre sırala
Gerek dosyanın, gerek konuda yazdıklarınızın her yeri HDD sorunu kokuyor. Sisteminizden çıkarın diski, sorun çözülmeli.

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: ffffb38fd28c00e0, 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 partmgr.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5389

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25206

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

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

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

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


BUGCHECK_CODE:  7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffb38fd28c00e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

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: 
fffffd06`789414f8 fffff806`1e637a63     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffb38f`d28c00e0 : nt!KeBugCheckEx
fffffd06`78941500 fffff806`1e5300eb     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x156d13
fffffd06`789415b0 fffff806`1e452b4d     : ffffb38f`d28c2080 ffffb38f`dc01c088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
fffffd06`789415e0 fffff806`1e477502     : fffff806`1e360f00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x19d
fffffd06`789416a0 fffff806`1e40656d     : ffff9b01`df19d180 ffffb38f`d28c00e0 ffff9b01`df19d101 fffff806`21c3572b : nt!KiExitDispatcher+0x282
fffffd06`78941700 fffff806`1e476d5f     : fffffd06`78941800 ffffb38f`dc01c010 ffffb38f`d283ed01 ffffb38f`00000001 : nt!KeInsertQueueApc+0x14d
fffffd06`789417a0 fffff806`1e475f77     : 00000000`00000000 00000000`00000001 fffff806`1e360f10 fffff806`1e35d8f8 : nt!IopfCompleteRequest+0xdcf
fffffd06`789418b0 fffff806`20fcb778     : 00000000`00000000 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 : nt!IofCompleteRequest+0x17
fffffd06`789418e0 00000000`00000000     : 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 fffff806`20fc1540 : partmgr+0xb778


SYMBOL_NAME:  partmgr+b778

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b778

FAILURE_BUCKET_ID:  0x7a_c000000e_partmgr!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b4acaf9d-6a81-b42b-3866-20c206a01a65}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
Çözüm
Bora Dere dedi:
Gerek dosyanın, gerek konuda yazdıklarınızın her yeri HDD sorunu kokuyor. Sisteminizden çıkarın diski, sorun çözülmeli.

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: ffffb38fd28c00e0, 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 partmgr.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5389

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25206

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

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

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

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


BUGCHECK_CODE:  7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffb38fd28c00e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

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:
fffffd06`789414f8 fffff806`1e637a63     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffb38f`d28c00e0 : nt!KeBugCheckEx
fffffd06`78941500 fffff806`1e5300eb     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x156d13
fffffd06`789415b0 fffff806`1e452b4d     : ffffb38f`d28c2080 ffffb38f`dc01c088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
fffffd06`789415e0 fffff806`1e477502     : fffff806`1e360f00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x19d
fffffd06`789416a0 fffff806`1e40656d     : ffff9b01`df19d180 ffffb38f`d28c00e0 ffff9b01`df19d101 fffff806`21c3572b : nt!KiExitDispatcher+0x282
fffffd06`78941700 fffff806`1e476d5f     : fffffd06`78941800 ffffb38f`dc01c010 ffffb38f`d283ed01 ffffb38f`00000001 : nt!KeInsertQueueApc+0x14d
fffffd06`789417a0 fffff806`1e475f77     : 00000000`00000000 00000000`00000001 fffff806`1e360f10 fffff806`1e35d8f8 : nt!IopfCompleteRequest+0xdcf
fffffd06`789418b0 fffff806`20fcb778     : 00000000`00000000 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 : nt!IofCompleteRequest+0x17
fffffd06`789418e0 00000000`00000000     : 00000000`00000000 00000001`6311b23e fffff806`1e4eaa64 fffff806`20fc1540 : partmgr+0xb778


SYMBOL_NAME:  partmgr+b778

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b778

FAILURE_BUCKET_ID:  0x7a_c000000e_partmgr!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b4acaf9d-6a81-b42b-3866-20c206a01a65}

Followup:     MachineOwner
---------
Genişletmek için tıkla...
Garantiye göndereceğim büyük ihtimal, cevabınız için sağ olun.
Garanti HDD'yi karşılar mı? Açıkçası ben kronik sorunlu olarak bilinen Adata SU650 kullanıyorum, onunla bu kadar sorun yaşamadım.
İtopya'dan hazır olarak almıştım bilgisayarımı.
 
Artı 0 Eksi
Garantilik pek bir işim olmadı şimdilik, kesin bir cevap veremeyeceğim. Fakat mantıken ürünün garantisi devam ediyorsa ve elinizde olmayan sebeplerden ötürü bir sorun gerçekleştiyse ilgilenmeleri gerekir.
 
Artı 0 Eksi
Uyarı! Bu konu 5 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.

Benzer konular

R
  • Soru
HDD bozuk olduğu için "KERNEL_DATA_INPAGE_ERROR mavi ekran hatası
Mesaj
6
Görüntüleme
178
GFYT
GFYT
caganataly
  • Soru
KERNEL_DATA_INPAGE_ERROR hatası
2
Mesaj
11
Görüntüleme
331
turko35408
turko35408
D0lunay380
  • Soru
"KERNEL_DATA_INPAGE_ERROR" hatası
Mesaj
4
Görüntüleme
338
D0lunay380
D0lunay380
Reidon
  • Soru
KERNEL_DATA_INPAGE_ERROR hatası
Mesaj
1
Görüntüleme
103
GFYT
GFYT
AX400
  • Soru
KERNEL_DATA_INPAGE_ERROR hatası
Mesaj
1
Görüntüleme
245
181951
181951

Bu konuyu görüntüleyen kullanıcılar

Toplam: 2 (üye: 0, misafir: 2)

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı