KERNEL_DATA_INPAGE_ERROR hatası

ddraigo1

Kilopat
Katılım
9 Haziran 2017
Mesajlar
56
Daha fazla  
Cinsiyet
Erkek
Merhaba, son günlerde bilgisayarımı yeniden başlattığım zaman KERNEL_DATA_INPAGE_ERROR hatası alıyorum, minidump dosyalarımı paylaştım, memtest86 ile test yaptım herhangi bir error vermedi, sistem özelliklerimi aşağıya bırakıyorum, bilgisayarı toplayalı 2 ay civarında oldu ve virüs olduğunu düşünmüyorum çünkü dikkatli kullanıyorum ve avast var, şimdiden teşekkür ederim.

Bu da HDtune programı ile yaptığım error scan testi.
resim_2021-12-08_043359.png
 
Son düzenleme:
Vanguard Anti-Cheat yazılımını kaldırıp dener misiniz rica etsem?


Bir de DDU yazılımı ile temizledikten sonra sisteminizle uyumlu en güncel ekran kartı sürücüsünü Sürücüleri Yükle | NVIDIA üzerinden indirerek kurun.

DDU : DDU ile Sürücü Kaldırma Rehberi

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: ffff90809e38a600, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000010, error status (normally i/o status code)
Arg3: 00000003f1e528c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80365a50000, 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: 2780

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10275

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

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

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

    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


FILE_IN_CAB:  120821-8421-01.dmp

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffff90809e38a600

BUGCHECK_P2: ffffffffc0000010

BUGCHECK_P3: 3f1e528c0

BUGCHECK_P4: fffff80365a50000

ERROR_CODE: (NTSTATUS) 0xc0000010 - Belirtilen istek, hedef ayg t i in ge erli bir i lem de il.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffd30e5fde9040 -- (.trap 0xffffd30e5fde9040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffffffe5200 rbx=0000000000000000 rcx=ffffe7037cc3e770
rdx=00000000000006b8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8036354b64c rsp=ffffd30e5fde91d0 rbp=fffff80365a50000
 r8=0000000000000000  r9=ffffd30e5fde9290 r10=fffff80365a50000
r11=ffff9bfff7600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
cng!SymCryptSha256AppendBlocks_shani+0x64:
fffff803`6354b64c f3410f6f0a      movdqu  xmm1,xmmword ptr [r10] ds:fffff803`65a50000=????????????????????????????????
Resetting default scope

STACK_TEXT: 
ffffd30e`5fde8c98 fffff803`5ee5ddf9     : 00000000`0000007a ffff9080`9e38a600 ffffffff`c0000010 00000003`f1e528c0 : nt!KeBugCheckEx
ffffd30e`5fde8ca0 fffff803`5ee5bb05     : ffffd30e`00008000 ffffd30e`5fde8e00 ffffd30e`5fde8e30 fffff803`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffd30e`5fde8d90 fffff803`5ee9f3f8     : 00000000`c0033333 00000000`00000000 fffff803`65a50000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffd30e`5fde8ea0 fffff803`5f00545e     : fffff803`00000160 fffff803`5effd985 00000000`000188cb fffff803`5eff8e11 : nt!MmAccessFault+0x468
ffffd30e`5fde9040 fffff803`6354b64c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
ffffd30e`5fde91d0 fffff803`634ffe46     : fffff803`640726d2 ffffd30e`5fde93b0 fffff803`65a50000 00000000`0001ae00 : cng!SymCryptSha256AppendBlocks_shani+0x64
ffffd30e`5fde9250 fffff803`634ffaad     : 00000000`00000000 00000000`00000000 00000000`0001ae00 ffffe703`7067f870 : cng!SymCryptSha256Append+0xa6
ffffd30e`5fde9290 fffff803`634ff9b7     : 00000000`00000000 00000000`00000000 fffff803`634fe320 fffff803`634fd86a : cng!MSCryptHashDataInternal+0xc9
ffffd30e`5fde92c0 fffff803`634f5b82     : 00000000`00040286 00000000`00000000 ffffe703`79ed8988 0000ffff`f803634f : cng!MSCryptHashData+0x87
ffffd30e`5fde9360 fffff803`64c2830e     : 00000000`00000000 fffff803`65a50000 00000000`0001ae00 ffffe703`70df3060 : cng!BCryptHashData+0x82
ffffd30e`5fde93b0 00000000`00000000     : fffff803`65a50000 00000000`0001ae00 ffffe703`70df3060 00000000`00000000 : FACEIT+0xc2830e


SYMBOL_NAME:  cng!SymCryptSha256AppendBlocks_shani+64

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1387

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  64

FAILURE_BUCKET_ID:  0x7a_c0000010_cng!SymCryptSha256AppendBlocks_shani

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {49fc6d69-99ba-18f7-9f52-5fc0cc17accb}

Followup:     MachineOwner

Kod:
Unloaded modules:
fffff803`70170000 fffff803`7017f000   dump_storpor
fffff803`701b0000 fffff803`701dd000   dump_stornvm
fffff803`70000000 fffff803`7001e000   dump_dumpfve
fffff803`70be0000 fffff803`70bfc000   dam.sys
fffff803`71510000 fffff803`71d1a000   vgk.sys
fffff803`65530000 fffff803`65541000   hwpolicy.sys
 
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.

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

Technopat Haberler

Geri
Yukarı