KERNEL_DATA_INPAGE_ERROR mavi ekran hatası

Tarihe göre sırala Puana göre sırala
  • Kaspersky ürününü güncelleyin, güncelse gözlem amaçlı bir süre kaldırın.
  • Malwarebytes'ı da kaldırın. Gözlemleme işi bittikten sonra ise yalnızca 1 tanesini kurun.
  • MSI Afterburner'ı kaldırın.
  • HDTune Pro ile quick scan kapalı olacak şekilde error scan yapın, ayrıca health kısmının da görselini test sonucuyla birlikte ekleyin konuya.
  • Gigabyte F60 serisini düzeltemedi bir türlü BIOS olarak, yükleyip yükleyip geri çekiyorlar. Sizde de beta olan sürüm yüklü. Umarım kısa zamanda kararlı bir sürüm yayınlanır. Siteyi takipte kalın, kararlı sürüm geldiğinde mutlaka geçiş yapın.

    B450M S2H (Rev. 1.x) | Motherboards | GIGABYTE

    GIGABYTE Oyun LAN ve Bant Genişliği Yönetimi, PCIe Jen3 x4 M.2, 7 renk RGB LED Şeritler ve Anti-Kükürt Direnç Tasarımı ile AMD B450 Ultra Durable Anakart Supports AMD Ryzen™ 5000 series / Ryzen™ 5000 G-Series/ 3rd Gen Ryzen™/ 2nd Gen Ryzen™/ 1st Gen Ryzen™/ 2nd Gen Ryzen™ with Radeon™ Vega...
    www.gigabyte.com.tr

Kod: 
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa8072.18004\121320-9031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`51800000 PsLoadedModuleList = 0xfffff800`5242a2b0
Debug session time: Sun Dec 13 01:25:15.319 2020 (UTC + 3:00)
System Uptime: 0 days 13:45:48.960
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`51bf5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffea0e`17b83cf0=000000000000007a
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffd68200db02c0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 0000000101e048c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff800ba658000, 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 cng.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4358

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 43478

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffffd68200db02c0

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 101e048c0

BUGCHECK_P4: fffff800ba658000

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

TRAP_FRAME:  ffffea0e17b84090 -- (.trap 0xffffea0e17b84090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffff7236800 rbx=0000000000000000 rcx=ffff898d9684a840
rdx=00000000001e5c68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8005674a13f rsp=ffffea0e17b84220 rbp=fffff800b92001cc
r8=0000000000000034  r9=ffffea0e17b842e0 r10=fffff800ba657fcc
r11=ffffea0e17b84298 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cng+0x5a13f:
fffff800`5674a13f f3410f6f6a30    movdqu  xmm5,xmmword ptr [r10+30h] ds:fffff800`ba657ffc=????????????????????????????????
Resetting default scope

STACK_TEXT:
ffffea0e`17b83ce8 fffff800`51ab6e29     : 00000000`0000007a ffffd682`00db02c0 ffffffff`c000009c 00000001`01e048c0 : nt!KeBugCheckEx
ffffea0e`17b83cf0 fffff800`51ab4b35     : ffffea0e`00001000 ffffea0e`17b83e00 ffffea0e`17b83e80 fffff800`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffea0e`17b83de0 fffff800`51a0c9c8     : 00000000`c0033333 00000000`00000000 fffff800`ba658000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffea0e`17b83ef0 fffff800`51c0395e     : 00000000`08dc9834 00000000`00000000 ffff7788`b4bd30e3 ffff898d`90201ac0 : nt!MmAccessFault+0x468
ffffea0e`17b84090 fffff800`5674a13f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
ffffea0e`17b84220 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cng+0x5a13f


SYMBOL_NAME:  cng+5a13f

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  5a13f

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a73615ce-7842-13bc-61f5-986b1377fefb}

Followup:     MachineOwner
---------

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa8072.36918\121220-9062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`81800000 PsLoadedModuleList = 0xfffff802`8242a2b0
Debug session time: Sat Dec 12 11:11:34.373 2020 (UTC + 3:00)
System Uptime: 1 days 16:43:47.315
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`81bf5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffcf09`b9bd9cf0=000000000000007a
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffff81092c22eb58, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 00000003b180e8c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff802e556b000, 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: 4124

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 32491

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffff81092c22eb58

BUGCHECK_P2: ffffffffc000009c

BUGCHECK_P3: 3b180e8c0

BUGCHECK_P4: fffff802e556b000

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

TRAP_FRAME:  ffffcf09b9bda090 -- (.trap 0xffffcf09b9bda090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffff7236800 rbx=0000000000000000 rcx=ffffdb0b08bff580
rdx=00000000001e17a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80283b4a13f rsp=ffffcf09b9bda220 rbp=fffff802e40001cc
r8=0000000000000034  r9=ffffcf09b9bda2e0 r10=fffff802e556afcc
r11=ffffcf09b9bda298 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cng!SymCryptSha256AppendBlocks_shani+0x87:
fffff802`83b4a13f f3410f6f6a30    movdqu  xmm5,xmmword ptr [r10+30h] ds:fffff802`e556affc=????????????????????????????????
Resetting default scope

STACK_TEXT:
ffffcf09`b9bd9ce8 fffff802`81ab6e29     : 00000000`0000007a ffff8109`2c22eb58 ffffffff`c000009c 00000003`b180e8c0 : nt!KeBugCheckEx
ffffcf09`b9bd9cf0 fffff802`81ab4b35     : ffffcf09`00001000 ffffcf09`b9bd9e00 ffffcf09`b9bd9e80 fffff802`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffcf09`b9bd9de0 fffff802`81a0c9c8     : 00000000`c0033333 00000000`00000000 fffff802`e556b000 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffcf09`b9bd9ef0 fffff802`81c0395e     : 00000000`08dc9834 00000000`00000000 ffff72dd`90df7604 fffff802`8244ef40 : nt!MmAccessFault+0x468
ffffcf09`b9bda090 fffff802`83b4a13f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
ffffcf09`b9bda220 fffff802`83affce6     : fffff802`8461db5b ffffcf09`b9bda400 fffff802`e4000000 ffffdb0b`08bff470 : cng!SymCryptSha256AppendBlocks_shani+0x87
ffffcf09`b9bda2a0 fffff802`83aff94d     : 00000000`00000000 00000000`00000000 00000000`08dc9870 ffffdb0b`082c5d50 : cng!SymCryptSha256Append+0xa6
ffffcf09`b9bda2e0 fffff802`83aff857     : 00000000`00000000 00000000`00000000 fffff802`83afe1c0 fffff802`83afd70a : cng!MSCryptHashDataInternal+0xc9
ffffcf09`b9bda310 fffff802`83af5a22     : fffff802`e4000184 ffffdb0b`08bff470 ffffdb0b`08bff470 fffff802`e4000190 : cng!MSCryptHashData+0x87
ffffcf09`b9bda3b0 fffff802`85146c74     : fffff802`e40000e0 fffff802`e4000000 ffffdb0b`08bff470 00000000`c000a000 : cng!BCryptHashData+0x82
ffffcf09`b9bda400 fffff802`e40000e0     : fffff802`e4000000 ffffdb0b`08bff470 00000000`c000a000 00000000`00000000 : FACEIT+0xb46c74
ffffcf09`b9bda408 fffff802`e4000000     : ffffdb0b`08bff470 00000000`c000a000 00000000`00000000 00000000`00000000 : 0xfffff802`e40000e0
ffffcf09`b9bda410 ffffdb0b`08bff470     : 00000000`c000a000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff802`e4000000
ffffcf09`b9bda418 00000000`c000a000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00040206 : 0xffffdb0b`08bff470
ffffcf09`b9bda420 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00040206 000017b8`08dc9a00 : 0xc000a000


SYMBOL_NAME:  cng!SymCryptSha256AppendBlocks_shani+87

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  87

FAILURE_BUCKET_ID:  0x7a_c000009c_cng!SymCryptSha256AppendBlocks_shani

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6228935-4669-dc79-3473-bce966ea434c}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

Hocam uzun bir süredir beklemekteyim, test kaç dakika sürmekte?
 
Artı 0 Eksi
ViooYa dedi:
HD Tune'dan bahsediyorsanız, disk boyutunuza bağlı. Sabırlı olun, sabrın sonu selamettir diğer işlemleri de eksiksiz uygulayın.
Genişletmek için tıkla...

Hocam test bu şekilde, health kısmı ise bomboş.
 

Dosya Ekleri

  • 2.png
    12,3 KB · Görüntüleme: 32
Artı 0 Eksi

Dediklerinizin hepsini uyguladım. BIOS sürümünü bir öncekine getirmeli miyim?
 
Artı 0 Eksi
Moscow dedi:
dostlar yukarıdaki hatayı almaktayım. Minidump dosyası aşağıdadır.
Yeni klasör.rar — Yandex.Disk (yadi.sk)

Windows 10 kullanmaktayım.
Genişletmek için tıkla...

Başlıktaki hatanın aynısını dün aldım.
Asıl sorunun HDD'den dolayı olduğunu düşünüyorum. Çünkü kasamda eski bir HDD kullanıyordum, çıkardım ve bir daha hatayı almadım.
Ek olarak: BIOS'u beta sürümü olsa da son sürümüne güncelledim ve yeni gelen chipset güncellemesi vardı, onu da yaptım.
Sorunumu tam olarak hangisi çözdü emin değilim ama HDD'yi çıkardığım için çözüldüğünü düşünüyorum.
 
Artı 0 Eksi

Hocam birkaç ay önce 500GB bir HDD aldım, HDD'ye bağlı PCI-e kablosunu çıkartıp denesem HDD için bir sıkıntı yaratır mı?
 
Artı 0 Eksi
Moscow dedi:
Hocam birkaç ay önce 500GB bir HDD aldım, HDD'ye bağlı PCI-e kablosunu çıkartıp denesem HDD için bir sıkıntı yaratır mı?
Genişletmek için tıkla...
Ben de dediğiniz gibi yaptım, HDD şu an hala kasaya montajlı ama kablolarını söktüm.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
"KERNEL_DATA_INPAGE_ERROR" mavi ekran hatası
Mesaj
1
Görüntüleme
159
turko35408
K
  • Soru
"KERNEL_DATA_INPAGE_ERROR" mavi ekran hatası
Mesaj
3
Görüntüleme
263
GFYT
  • Soru
KERNEL_DATA_INPAGE_ERROR mavi ekran hatası
Mesaj
9
Görüntüleme
238
181951
  • Soru
Mavi ekran hatası KERNEL_DATA_INPAGE_ERROR
Mesaj
1
Görüntüleme
569
BlackShot
  • Soru
KERNEL_DATA_INPAGE_ERROR mavi ekran hatası
Mesaj
1
Görüntüleme
249
Yavuz_Çetin
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…