Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Katılım
13 Aralık 2023
Mesajlar
6.413
Makaleler
16
Çözümler
113
Beğeniler
8.812
Yer
LTAF
  • Anakart: M5A97 R2.0
  • İşlemci: FX 6300
  • Ekran Kartı: GTX 750 Ti
  • İşletim Sistemi: Windows 10

Sistem özellikleri yukarıda, sistem arkadaşıma ait. Kernel hatası almış gibi görünüyor hata kodu olarak. @bicy hocam bir bakarsan mutlu olurum, minidump dosyalarını aşağı bıraktım.

 
Çözüm
[CODE highlight="11"]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: ffffab8776a91e18, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000009a829860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80747521000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
[/CODE]

KERNEL_DATA_INPAGE_ERROR disk hatasıdır genellikle. Bknz;

[CODE title="Dosyadan"]DISK_HARDWARE_ERROR: There was error with disk hardware
[/CODE]

2.ARG değeri bizim NTStatus kodumuz. Kendisine buradan ulaşabiliriz: [MS-ERREF]: NTSTATUS Values

0xC000000E
STATUS_NO_SUCH_DEVICE
A device that does not exist was specified.

Varolmayan bir aygıt belirtildi hatası muhtemelen diskin o an sistemde görünmediğini ve bu yüzden mavi ekrana düştüğünü gösteriyor. Diskin iletişiminde sorun var ve bu çok ihtimalli. Diskin kendisi veya kablolar sebebiyle de olabiliyor.

[CODE highlight="7"]0: kd> !irp
Irp is active with 12 stacks 4 is current (= 0xffffd78c1c270bc8)
Mdl=ffffd78c2b699330: No System Buffer: Thread ffffd78c1ecd7080: Irp stack trace.
cmd flg cl Device File Completion-Context
18 e0 ffffd78c1356b060 00000000 fffff80177a31010-00000000 Success Error Cancel
\Driver\disk partmgr!PmIoCompletion
Args: 00001000 00000000 bd5fd000 00000000
[IRP_MJ_WRITE(4), N/A(3)]
18 e0 ffffd78c135188d0 00000000 fffff80177a31f30-00000000 Success Error Cancel
\Driver\partmgr partmgr!PartitionIoCompletion
Args: 39f9894de9 00000000 bd5fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
18 e0 ffffd78c134ea8d0 00000000 fffff80177b21160-ffffd78c13506a40 Success Error Cancel
\Driver\partmgr volmgr!VmpReadWriteCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c135068f0 00000000 fffff801787062c0-ffffd78c135ad181 Success Error Cancel
\Driver\volmgr fvevol!FvePassThroughCompletionRdpLevel2
Args: 00001000 00000000 39f9894ddf 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c135ad030 00000000 fffff801788d5200-00000000 Success Error Cancel
\Driver\fvevol iorate!IoRateReadWriteCompletion
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c13557af0 00000000 fffff80178820060-ffffd78c22fd1ea0 Success Error Cancel
\Driver\iorate volsnap!VspWriteContextCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e1 ffffd78c135bb080 00000000 fffff80177e23790-fffff60eb8fefd50 Success Error Cancel pending
Name paged out Ntfs!NtfsMasterIrpSyncCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
0 e0 ffffd78c135c3030 ffffd78c134a7bf0 fffff80177324520-ffffd78c33e419a0 Success Error Cancel
Name paged out FLTMGR!FltpPassThroughCompletion
Args: 00001000 00000000 0001a000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
0 1 ffffd78c13562d70 ffffd78c134a7bf0 00000000-00000000 pending
Name paged out
Args: 00001000 00000000 0001a000 00000000[/CODE]

Diskini kontrol etsin.
[CODE highlight="11"]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: ffffab8776a91e18, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000009a829860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80747521000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
[/CODE]

KERNEL_DATA_INPAGE_ERROR disk hatasıdır genellikle. Bknz;

[CODE title="Dosyadan"]DISK_HARDWARE_ERROR: There was error with disk hardware
[/CODE]

2.ARG değeri bizim NTStatus kodumuz. Kendisine buradan ulaşabiliriz: [MS-ERREF]: NTSTATUS Values

0xC000000E
STATUS_NO_SUCH_DEVICE
A device that does not exist was specified.

Varolmayan bir aygıt belirtildi hatası muhtemelen diskin o an sistemde görünmediğini ve bu yüzden mavi ekrana düştüğünü gösteriyor. Diskin iletişiminde sorun var ve bu çok ihtimalli. Diskin kendisi veya kablolar sebebiyle de olabiliyor.

[CODE highlight="7"]0: kd> !irp
Irp is active with 12 stacks 4 is current (= 0xffffd78c1c270bc8)
Mdl=ffffd78c2b699330: No System Buffer: Thread ffffd78c1ecd7080: Irp stack trace.
cmd flg cl Device File Completion-Context
18 e0 ffffd78c1356b060 00000000 fffff80177a31010-00000000 Success Error Cancel
\Driver\disk partmgr!PmIoCompletion
Args: 00001000 00000000 bd5fd000 00000000
[IRP_MJ_WRITE(4), N/A(3)]
18 e0 ffffd78c135188d0 00000000 fffff80177a31f30-00000000 Success Error Cancel
\Driver\partmgr partmgr!PartitionIoCompletion
Args: 39f9894de9 00000000 bd5fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
18 e0 ffffd78c134ea8d0 00000000 fffff80177b21160-ffffd78c13506a40 Success Error Cancel
\Driver\partmgr volmgr!VmpReadWriteCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c135068f0 00000000 fffff801787062c0-ffffd78c135ad181 Success Error Cancel
\Driver\volmgr fvevol!FvePassThroughCompletionRdpLevel2
Args: 00001000 00000000 39f9894ddf 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c135ad030 00000000 fffff801788d5200-00000000 Success Error Cancel
\Driver\fvevol iorate!IoRateReadWriteCompletion
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e0 ffffd78c13557af0 00000000 fffff80178820060-ffffd78c22fd1ea0 Success Error Cancel
\Driver\iorate volsnap!VspWriteContextCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
8 e1 ffffd78c135bb080 00000000 fffff80177e23790-fffff60eb8fefd50 Success Error Cancel pending
Name paged out Ntfs!NtfsMasterIrpSyncCompletionRoutine
Args: 00001000 00000000 ba2fd000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
0 e0 ffffd78c135c3030 ffffd78c134a7bf0 fffff80177324520-ffffd78c33e419a0 Success Error Cancel
Name paged out FLTMGR!FltpPassThroughCompletion
Args: 00001000 00000000 0001a000 00000000
[IRP_MJ_WRITE(4), N/A(0)]
0 1 ffffd78c13562d70 ffffd78c134a7bf0 00000000-00000000 pending
Name paged out
Args: 00001000 00000000 0001a000 00000000[/CODE]

Diskini kontrol etsin.
 
Çözüm
Disk kablolamalarına dikkat edebilirsin. Eskiden bende de olmuştu SATA kablosunda sıkıntı var mış. Çıkar biraz temizle tekrar dene olmazsa başka bir disk ile deneyebilirsin. Bu da tam çözüm olacak büyük ihtimalle.
 
Varolmayan bir aygıt belirtildi hatası muhtemelen diskin o an sistemde görünmediğini ve bu yüzden mavi ekrana düştüğünü gösteriyor. Diskin iletişiminde sorun var ve bu çok ihtimalli. Diskin kendisi veya kablolar sebebiyle de olabiliyor.


Diskini kontrol etsin.
Tamamdır, söyleyeceğim kendisine. Disk kablolarında zaten bir sorun var mış galiba, başka bir sata kablosuyla temizleyip deneyecek. Sonucu bildireceğim, teşekkürler hocam cansın. <3