Çözüldü Windows 8.1 Kernal Data Inpage Error hatası

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

Eloves

Femtopat
Katılım
11 Eylül 2020
Mesajlar
30
Arkadaşlar, bilgisayarım uzun süre açık kalınca ve AFK kalınca kapanıyor anlamadığım bir şekilde. Valorant oyununu açtığımda da aynı hatayı alıyorum. Sebebi nedir bilen biri var mı?
 
Son düzenleyen: Moderatör:
Çözüm
Disk bozuk olabilecek 48 sektör bulmuş. Uzun format atabilirsin belki giderler gitmezlerse Low Level Format atman gerekebilir diske ya da farklı bir disk ile sistemi deneyebilirsin.
Faceit kaldırınız. Valorant anti-cheat kaldırınız. ESET güncelleyin ya da kaldırınız. HD Tune 5.75 ile Health sekmesinin fotoğrafını paylaşın.
DDU ile ekran kartı sürücüsünü silip güncelini yükleyin. DDU ile Sürücü Kaldırma Rehberi - Technopat Sosyal
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: ffffc00170c5cba0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00002000940fb8c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80197ad8000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

ERROR_CODE: (NTSTATUS) 0xc0000185 - G/  ayg

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

TRAP_FRAME:  ffffd001d94d3180 -- (.trap 0xffffd001d94d3180)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000a68a9882 rbx=0000000000000000 rcx=00000000bc7d58e0
rdx=000000007bfcdabf rsi=0000000000000000 rdi=0000000000000000
rip=fffff80193ac63f1 rsp=ffffd001d94d3310 rbp=000000007d01c112
r8=fffff80197ad7fcc  r9=000000000f835103 r10=0000000000006644
r11=000000006ff51df3 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cng!SymCryptSha1AppendBlocksAsm+0x251:
fffff801`93ac63f1 458b5834        mov     r11d,dword ptr [r8+34h] ds:fffff801`97ad8000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff802cfcfc092 to fffff802cfd544c0

STACK_TEXT:
ffffd001`d94d2ec8 fffff802`cfcfc092 : 00000000`0000007a ffffc001`70c5cba0 ffffffff`c0000185 00002000`940fb8c0 : nt!KeBugCheckEx
ffffd001`d94d2ed0 fffff802`cfde61a0 : 00000000`00000002 ffffd001`d94d3038 fffff802`cff5bec0 ffffd001`00000000 : nt!MiWaitForInPageComplete+0x722
ffffd001`d94d2fc0 fffff802`cfc5f492 : 00000000`c0033333 ffffc001`70c5cba0 ffffd001`d94d3180 fffff801`97ad8000 : nt!MiIssueHardFault+0x330
ffffd001`d94d3080 fffff802`cfd61b9d : 00000000`bdb76d39 00000000`00000000 00650044`005c0000 00650063`00690076 : nt!MmAccessFault+0x6f2
ffffd001`d94d3180 fffff801`93ac63f1 : 0f835103`ff483bc7 89740570`00006644 03f5ff48`488d3ddd 488d0571`897c2438 : nt!KiPageFault+0x31d
ffffd001`d94d3310 fffff801`93ac5c18 : ffffe000`5a397d60 00000000`00000000 00001e7b`ee6929a3 fffff802`cfd5c795 : cng!SymCryptSha1AppendBlocksAsm+0x251
ffffd001`d94d33a0 fffff801`93ac1c91 : ffffe000`5bc0c7d0 fffff801`97a00198 00000000`00163268 00000000`00000000 : cng!SymCryptSha1Append+0x50
ffffd001`d94d33d0 fffff801`93ac2181 : 00000000`00000000 ffffe000`5bc0c7a0 00000000`0e417f74 00000000`00163268 : cng!MSCryptHashData+0x91
ffffd001`d94d3470 fffff801`949cf108 : fffff801`97a000e8 ffffe000`5bc0c7a0 ffffe000`5bc0c7a0 00000000`00163400 : cng!BCryptHashData+0x71
ffffd001`d94d34c0 fffff801`97a000e8 : ffffe000`5bc0c7a0 ffffe000`5bc0c7a0 00000000`00163400 00000000`00000000 : FACEIT+0x9b6108
ffffd001`d94d34c8 ffffe000`5bc0c7a0 : ffffe000`5bc0c7a0 00000000`00163400 00000000`00000000 ffffd001`00000000 : 0xfffff801`97a000e8
ffffd001`d94d34d0 ffffe000`5bc0c7a0 : 00000000`00163400 00000000`00000000 ffffd001`00000000 00000000`00000000 : 0xffffe000`5bc0c7a0
ffffd001`d94d34d8 00000000`00163400 : 00000000`00000000 ffffd001`00000000 00000000`00000000 00000000`00200202 : 0xffffe000`5bc0c7a0
ffffd001`d94d34e0 00000000`00000000 : ffffd001`00000000 00000000`00000000 00000000`00200202 00000000`00000000 : 0x163400


STACK_COMMAND:  kb

FOLLOWUP_IP:
cng!SymCryptSha1AppendBlocksAsm+251
fffff801`93ac63f1 458b5834        mov     r11d,dword ptr [r8+34h]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  cng!SymCryptSha1AppendBlocksAsm+251

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d728a5e

IMAGE_VERSION:  6.3.9600.19481

BUCKET_ID_FUNC_OFFSET:  251

FAILURE_BUCKET_ID:  0x7a_c0000185_cng!SymCryptSha1AppendBlocksAsm

BUCKET_ID:  0x7a_c0000185_cng!SymCryptSha1AppendBlocksAsm

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_c0000185_cng!symcryptsha1appendblocksasm

FAILURE_ID_HASH:  {c8269d97-778c-3a20-4494-8af063760a47}

Followup: MachineOwner
---------
UltraISO kullanıyorsan kaldırın.
 
Son düzenleme:
.
 

Dosya Ekleri

  • 13-Eylül-2020_16-07.png
    13-Eylül-2020_16-07.png
    19,4 KB · Görüntüleme: 50
Disk bozuk olabilecek 48 sektör bulmuş. Uzun format atabilirsin belki giderler gitmezlerse Low Level Format atman gerekebilir diske ya da farklı bir disk ile sistemi deneyebilirsin.
 
Çözüm
O yüzden kaldırıp tekrar test edin hala alırsanız başka disk ile deneyebilirsiniz. Ve diskiniz daha bozulmamış sadece bozuk olabilecek sektörler bulmuş. Disk bu sektörleri okursa bu sayı azalacaktır.
 

Yeni konular

Geri
Yukarı