Çözüldü R5 3500 sistemde "KERNEL_DATA_INPAGE_ERROR" mavi ekran hatası

Merhaba, 1 ay önce sıfır topladığım sistemime Windows 10 kurmuştum fakat çeşitli mavi ekran hatalarıyla karşılaşıyordum ve Windows 11 geçmeyi düşündüm ve kurdum. Fakat hataların devamı bitmek bilmedi bir türlü SFC,DISM gibi komutları kullandım taramaları gerceklestırdım fakat bır problem göremedım ve ardından ara ara KERNEL_DATA_INPAGE_ERROR hatası almaya başladım. Bu konuda bilgisi olan arkadaşlar yardımcı olabilir mi acaba? Minidump dosyalarımı paylaşmak istiyorum fakat minidump klasörü içerisinde dmp uzantılı tek bır dosya var sanırım şu an burada paylaşmam doğru değil. Tekrar mavi ekran hatası alırsam bu dosyaların adeti artacak mı ve o zaman dosyaları sizlerle paylaşabilir miyim? Komut sistemiyle ve Memtest gibi yardımcı programlarla RAM testlerımı yaptım problem gözükmüyor ve SSD testlerımıde HD Tune ile gerçekleştirdim ve yime komut sistemıylede diskime onarım yaptım buralarda da bir problem gözükmüyor. Minidump doslayarında sıkıştırma yapamıyorum normal bir şekilde paylaşsam problem olur mu ? Şunuda ekliyim genelde oyuna girdiğimde alıyorum mavı ekran onun dısında bostayken cok cok nadır yasıyorum fakat oyunlarda 2 dakıka sonra ozellıkle ağır oyunlarda cok fazla yasıyorum
[CODE title="Disk hataları var sanırım fakat farklı hata var mı anlayamıyorum bakmanız için buraya bırakıyorum şimdiden teşekkür ederim"]*******************************************************************************
* *
* 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffde0841e561a0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2968

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12838

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 031322-4265-01.dmp

BUGCHECK_CODE: 7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffde0841e561a0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

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: System

STACK_TEXT:
ffffdc81`1ac995a8 fffff805`1be5ba63 : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffde08`41e561a0 : nt!KeBugCheckEx
ffffdc81`1ac995b0 fffff805`1bc62b2b : 00000000`00100000 00000000`c000000e 00000000`00000000 ffffde08`41e561d0 : nt!MiWriteComplete+0x24b193
ffffdc81`1ac99650 fffff805`1bd1ce36 : ffffde08`41e44080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffdc81`1ac99680 fffff805`1bcb1c26 : ffffde08`41e44080 00000000`00000000 ffffde08`41e48c90 00000000`00000000 : nt!KiDeliverApc+0x1b6
ffffdc81`1ac99740 fffff805`1bcb3549 : 00000000`00000003 00000000`00000001 ffffdc81`1ac99958 fffff805`00000000 : nt!KiSwapThread+0x936
ffffdc81`1ac99820 fffff805`1bd32e71 : 00000000`00000000 00000000`00000000 ffffde08`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x159
ffffdc81`1ac998c0 fffff805`1bdcafe7 : ffffde08`00000000 fffff805`00000012 fffff805`1c654ec0 00000000`00000100 : nt!KeWaitForMultipleObjects+0x2b1
ffffdc81`1ac999c0 fffff805`1bc5a8b5 : ffffde08`41e44080 ffffde08`41e44080 00000000`00000080 fffff805`1bdcae40 : nt!MiModifiedPageWriter+0x1a7
ffffdc81`1ac99bf0 fffff805`1be1a574 : ffff8001`3aa98180 ffffde08`41e44080 fffff805`1bc5a860 0e2f0e2e`0e2d0e2c : nt!PspSystemThreadStartup+0x55
ffffdc81`1ac99c40 00000000`00000000 : ffffdc81`1ac9a000 ffffdc81`1ac94000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!MiWriteComplete+24b193

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22000.556

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 24b193

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWriteComplete

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

5: 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffde0841e561a0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, 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: 2406

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3977

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 031322-4265-01.dmp

BUGCHECK_CODE: 7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffde0841e561a0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

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: System

STACK_TEXT:
ffffdc81`1ac995a8 fffff805`1be5ba63 : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffde08`41e561a0 : nt!KeBugCheckEx
ffffdc81`1ac995b0 fffff805`1bc62b2b : 00000000`00100000 00000000`c000000e 00000000`00000000 ffffde08`41e561d0 : nt!MiWriteComplete+0x24b193
ffffdc81`1ac99650 fffff805`1bd1ce36 : ffffde08`41e44080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffdc81`1ac99680 fffff805`1bcb1c26 : ffffde08`41e44080 00000000`00000000 ffffde08`41e48c90 00000000`00000000 : nt!KiDeliverApc+0x1b6
ffffdc81`1ac99740 fffff805`1bcb3549 : 00000000`00000003 00000000`00000001 ffffdc81`1ac99958 fffff805`00000000 : nt!KiSwapThread+0x936
ffffdc81`1ac99820 fffff805`1bd32e71 : 00000000`00000000 00000000`00000000 ffffde08`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x159
ffffdc81`1ac998c0 fffff805`1bdcafe7 : ffffde08`00000000 fffff805`00000012 fffff805`1c654ec0 00000000`00000100 : nt!KeWaitForMultipleObjects+0x2b1
ffffdc81`1ac999c0 fffff805`1bc5a8b5 : ffffde08`41e44080 ffffde08`41e44080 00000000`00000080 fffff805`1bdcae40 : nt!MiModifiedPageWriter+0x1a7
ffffdc81`1ac99bf0 fffff805`1be1a574 : ffff8001`3aa98180 ffffde08`41e44080 fffff805`1bc5a860 0e2f0e2e`0e2d0e2c : nt!PspSystemThreadStartup+0x55
ffffdc81`1ac99c40 00000000`00000000 : ffffdc81`1ac9a000 ffffdc81`1ac94000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!MiWriteComplete+24b193

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22000.556

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 24b193

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWriteComplete

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

[/CODE]