G4400 - GT730 "Kernel Data Inpage Error" Hatası

İşletim sistemi
Windows 10
Tarihe göre sırala Puana göre sırala
Sorununuz da HDD kaynaklı görünüyor.

Komut ekranını çalıştırıp chkdsk /f /r komutunu uygulamayı deneyip sistemi yeniden başlatabilirsiniz ama disk mavi ekran verdirdiğine göre ciddi sıkıntıları olması muhtemel. Dolayısıyla kesin çözüm tüm verilerinizi yedekleyip bir SSD'ye geçmeniz olacaktır.

Yine de HD Tune üzerinden "Health" sekmesinin ekran görüntüsünü atarsanız iyi olur.

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: ffffe154012e9b50, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 000020024a71c880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffa8025d36a848, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5874

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 36836

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffffe154012e9b50

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 20024a71c880

BUGCHECK_P4: ffffa8025d36a848

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

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:  svchost.exe

TRAP_FRAME:  ffff860d7650fb40 -- (.trap 0xffff860d7650fb40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa8025d3682b0 rbx=0000000000000000 rcx=ffffa8025d36a840
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806423c3701 rsp=ffff860d7650fcd0 rbp=ffffa8025d114313
r8=0000000000000000  r9=000000000016197c r10=fffff806424443c0
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Ntfs!NtfsLookupNtfsMcbEntryWithSyncFlag+0x221:
fffff806`423c3701 48397908        cmp     qword ptr [rcx+8],rdi ds:ffffa802`5d36a848=????????????????
Resetting default scope

STACK_TEXT:
ffff860d`7650f788 fffff806`3ba1c464     : 00000000`0000007a ffffe154`012e9b50 ffffffff`c000009c 00002002`4a71c880 : nt!KeBugCheckEx
ffff860d`7650f790 fffff806`3b8946fd     : 00000000`00000002 ffff860d`00000000 ffff860d`7650f948 fffff806`00000000 : nt!MiWaitForInPageComplete+0x188434
ffff860d`7650f8a0 fffff806`3b8587fb     : 00000000`c0033333 00000000`00000000 ffffa802`5d36a848 ffffa802`5d36a848 : nt!MiIssueHardFault+0x1ad
ffff860d`7650f9a0 fffff806`3b9d041e     : 00000000`0023ee05 ffffe100`da5ebff0 00000000`00008000 ffff8e80`03ddfd30 : nt!MmAccessFault+0x40b
ffff860d`7650fb40 fffff806`423c3701     : 00000000`00000006 ffffa802`5d114313 00000000`00000000 ffffa802`5d1142b0 : nt!KiPageFault+0x35e
ffff860d`7650fcd0 fffff806`423c2775     : 00000000`00000000 00000000`00000000 ffff860d`76510078 ffff860d`76510050 : Ntfs!NtfsLookupNtfsMcbEntryWithSyncFlag+0x221
ffff860d`7650fd60 fffff806`423c23fe     : ffffce0f`4e8d8938 ffffa802`5d114170 00000001`00000000 00000000`00000006 : Ntfs!NtfsLookupRealAllocationInternal+0xf5
ffff860d`7650ff00 fffff806`423c1bde     : ffffce0f`4e8d8938 ffffa802`5d114170 00000000`00000006 ffff860d`76510078 : Ntfs!NtfsLookupAllocation+0x62
ffff860d`7650ffb0 fffff806`423c12d5     : ffffce0f`4e8d8938 ffffce0f`4e2a49a0 ffff860d`765101d0 ffffce0f`4e2a49a0 : Ntfs!NtfsPrepareSimpleBuffers+0x19e
ffff860d`76510120 fffff806`423c0116     : ffff860d`765101d0 ffff860d`76510290 ffffce0f`4e8d8938 00000000`00006400 : Ntfs!NtfsPrepareBuffers+0xc5
ffff860d`76510190 fffff806`423c6e58     : ffff860d`76510630 00000000`00008000 00000000`00000001 ffffce0f`4e2a49a0 : Ntfs!NtfsNonCachedIo+0x2e6
ffff860d`76510440 fffff806`423c641c     : ffff860d`76510640 ffffce0f`4e2a49a0 ffff860d`76510640 ffffce0f`4e8d8938 : Ntfs!NtfsCommonRead+0x828
ffff860d`76510600 fffff806`3b899eb9     : ffffce0f`4eecf010 ffffce0f`4e2a49a0 ffffce0f`4e2a4e60 ffffffff`ffffff00 : Ntfs!NtfsFsdRead+0x20c
ffff860d`765106c0 fffff806`3e5355de     : 00000000`00000000 ffff860d`765107a0 ffffce0f`4e2a49a0 ffff860d`765107b0 : nt!IofCallDriver+0x59
ffff860d`76510700 fffff806`3e533f16     : ffff860d`765107a0 fffff806`3b85fcf8 ffff860d`76510901 ffffa802`5c8bbee8 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15e
ffff860d`76510780 fffff806`3b899eb9     : ffffce0f`4e2a49a0 fffff806`3b92c37b 00000001`00000000 00000000`00000005 : FLTMGR!FltpDispatch+0xb6
ffff860d`765107e0 fffff806`3b92bf63     : 00000000`00000005 ffffce0f`4e2a49a0 ffffce0f`4bff0220 ffffce0f`4bff02e0 : nt!IofCallDriver+0x59
ffff860d`76510820 fffff806`3b893e59     : ffffce0f`4bff01d0 00000000`00000000 ffffce0f`4bff0230 ffffce0f`4bff01f0 : nt!IoPageReadEx+0x1d3
ffff860d`76510890 fffff806`3b8949d9     : 00000000`00000003 ffff860d`76510970 ffff860d`76510ad8 fffff806`3b85a746 : nt!MiIssueHardFaultIo+0xc1
ffff860d`765108e0 fffff806`3b8587fb     : 00000000`c0033333 00000000`00000001 00007ffe`2c78787b fffff806`3be0f8de : nt!MiIssueHardFault+0x489
ffff860d`765109e0 fffff806`3b9d041e     : ffffce0f`49f4e080 00000000`00000000 00007ffe`2c796a30 00000000`00000000 : nt!MmAccessFault+0x40b
ffff860d`76510b80 00007ffe`2c78787b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000b3`8737fa10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`2c78787b


SYMBOL_NAME:  nt!MiWaitForInPageComplete+188434

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.900

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  188434

FAILURE_BUCKET_ID:  0x7a_c000009c_nt!MiWaitForInPageComplete

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3b678a62-8102-4c37-98ae-ed57bc2668aa}

Followup:     MachineOwner
---------
 
Son düzenleme:
Artı 0 Eksi
yika38 dedi:
Sorununuz da HDD kaynaklı görünüyor.

Komut ekranını çalıştırıp chkdsk /f /r komutunu uygulamayı deneyip sistemi yeniden başlatabilirsiniz ama disk mavi ekran verdirdiğine göre ciddi sıkıntıları olması muhtemel. Dolayısıyla kesin çözüm tüm verilerinizi yedekleyip bir SSD'ye geçmeniz olacaktır.

Yine de HD Tune üzerinden "Health" sekmesinin ekran görüntüsünü atarsanız iyi olur.

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: ffffe154012e9b50, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 000020024a71c880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffa8025d36a848, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5874

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 36836

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffffe154012e9b50

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 20024a71c880

BUGCHECK_P4: ffffa8025d36a848

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

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:  svchost.exe

TRAP_FRAME:  ffff860d7650fb40 -- (.trap 0xffff860d7650fb40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa8025d3682b0 rbx=0000000000000000 rcx=ffffa8025d36a840
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806423c3701 rsp=ffff860d7650fcd0 rbp=ffffa8025d114313
r8=0000000000000000  r9=000000000016197c r10=fffff806424443c0
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Ntfs!NtfsLookupNtfsMcbEntryWithSyncFlag+0x221:
fffff806`423c3701 48397908        cmp     qword ptr [rcx+8],rdi ds:ffffa802`5d36a848=????????????????
Resetting default scope

STACK_TEXT:
ffff860d`7650f788 fffff806`3ba1c464     : 00000000`0000007a ffffe154`012e9b50 ffffffff`c000009c 00002002`4a71c880 : nt!KeBugCheckEx
ffff860d`7650f790 fffff806`3b8946fd     : 00000000`00000002 ffff860d`00000000 ffff860d`7650f948 fffff806`00000000 : nt!MiWaitForInPageComplete+0x188434
ffff860d`7650f8a0 fffff806`3b8587fb     : 00000000`c0033333 00000000`00000000 ffffa802`5d36a848 ffffa802`5d36a848 : nt!MiIssueHardFault+0x1ad
ffff860d`7650f9a0 fffff806`3b9d041e     : 00000000`0023ee05 ffffe100`da5ebff0 00000000`00008000 ffff8e80`03ddfd30 : nt!MmAccessFault+0x40b
ffff860d`7650fb40 fffff806`423c3701     : 00000000`00000006 ffffa802`5d114313 00000000`00000000 ffffa802`5d1142b0 : nt!KiPageFault+0x35e
ffff860d`7650fcd0 fffff806`423c2775     : 00000000`00000000 00000000`00000000 ffff860d`76510078 ffff860d`76510050 : Ntfs!NtfsLookupNtfsMcbEntryWithSyncFlag+0x221
ffff860d`7650fd60 fffff806`423c23fe     : ffffce0f`4e8d8938 ffffa802`5d114170 00000001`00000000 00000000`00000006 : Ntfs!NtfsLookupRealAllocationInternal+0xf5
ffff860d`7650ff00 fffff806`423c1bde     : ffffce0f`4e8d8938 ffffa802`5d114170 00000000`00000006 ffff860d`76510078 : Ntfs!NtfsLookupAllocation+0x62
ffff860d`7650ffb0 fffff806`423c12d5     : ffffce0f`4e8d8938 ffffce0f`4e2a49a0 ffff860d`765101d0 ffffce0f`4e2a49a0 : Ntfs!NtfsPrepareSimpleBuffers+0x19e
ffff860d`76510120 fffff806`423c0116     : ffff860d`765101d0 ffff860d`76510290 ffffce0f`4e8d8938 00000000`00006400 : Ntfs!NtfsPrepareBuffers+0xc5
ffff860d`76510190 fffff806`423c6e58     : ffff860d`76510630 00000000`00008000 00000000`00000001 ffffce0f`4e2a49a0 : Ntfs!NtfsNonCachedIo+0x2e6
ffff860d`76510440 fffff806`423c641c     : ffff860d`76510640 ffffce0f`4e2a49a0 ffff860d`76510640 ffffce0f`4e8d8938 : Ntfs!NtfsCommonRead+0x828
ffff860d`76510600 fffff806`3b899eb9     : ffffce0f`4eecf010 ffffce0f`4e2a49a0 ffffce0f`4e2a4e60 ffffffff`ffffff00 : Ntfs!NtfsFsdRead+0x20c
ffff860d`765106c0 fffff806`3e5355de     : 00000000`00000000 ffff860d`765107a0 ffffce0f`4e2a49a0 ffff860d`765107b0 : nt!IofCallDriver+0x59
ffff860d`76510700 fffff806`3e533f16     : ffff860d`765107a0 fffff806`3b85fcf8 ffff860d`76510901 ffffa802`5c8bbee8 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15e
ffff860d`76510780 fffff806`3b899eb9     : ffffce0f`4e2a49a0 fffff806`3b92c37b 00000001`00000000 00000000`00000005 : FLTMGR!FltpDispatch+0xb6
ffff860d`765107e0 fffff806`3b92bf63     : 00000000`00000005 ffffce0f`4e2a49a0 ffffce0f`4bff0220 ffffce0f`4bff02e0 : nt!IofCallDriver+0x59
ffff860d`76510820 fffff806`3b893e59     : ffffce0f`4bff01d0 00000000`00000000 ffffce0f`4bff0230 ffffce0f`4bff01f0 : nt!IoPageReadEx+0x1d3
ffff860d`76510890 fffff806`3b8949d9     : 00000000`00000003 ffff860d`76510970 ffff860d`76510ad8 fffff806`3b85a746 : nt!MiIssueHardFaultIo+0xc1
ffff860d`765108e0 fffff806`3b8587fb     : 00000000`c0033333 00000000`00000001 00007ffe`2c78787b fffff806`3be0f8de : nt!MiIssueHardFault+0x489
ffff860d`765109e0 fffff806`3b9d041e     : ffffce0f`49f4e080 00000000`00000000 00007ffe`2c796a30 00000000`00000000 : nt!MmAccessFault+0x40b
ffff860d`76510b80 00007ffe`2c78787b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000b3`8737fa10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`2c78787b


SYMBOL_NAME:  nt!MiWaitForInPageComplete+188434

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.900

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  188434

FAILURE_BUCKET_ID:  0x7a_c000009c_nt!MiWaitForInPageComplete

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3b678a62-8102-4c37-98ae-ed57bc2668aa}

Followup:     MachineOwner
---------
Genişletmek için tıkla...
hddtest.PNG

Yanıtınızı geç gördüğüm için çok özür dilerim.
 
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

felix.voir
  • Soru
Kernel data inpage error hatası
Mesaj
1
Görüntüleme
531
Recep Baltaş
Recep Baltaş
B
  • Soru
Kernel Data Inpage Error mavi ekran hatası
Mesaj
1
Görüntüleme
1.022
181951
181951
felix.voir
  • Soru
Kernel data inpage error mavi ekran hatası
Mesaj
5
Görüntüleme
1.455
283156
2
Arodesli
  • Soru
"KERNEL DATA INPAGE ERROR" mavi ekran hatası
2
Mesaj
18
Görüntüleme
2.570
Murat5038
Murat5038
homageforsatan
  • Soru
KERNEL DATA INPAGE ERROR mavi ekran hatası
Mesaj
2
Görüntüleme
1.272
Assecreed
A

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı