RX 580 sistem mavi ekran hatası

Merhabalar,
R5 1600 AF.
RX580 8 GB.
16 GB 2x8 3000MHz RAM sistemim var. Yaklaşık 1 haftadır "MEMORY_MANAGEMENT" kodu ile mavi ekran hatası alıyorum. En son hata aldığımda SSD diskimin sağlığı da düştü ve sistem dosyaları hasar gördü. Tekrardan temiz kurulum yapmak zorunda kaldım. Bellekleri test ettim fakat sıkıntı çıkmadı. Memtest86 ile de test etmiştim. Her hata sonrası WattMan hatası da cabası. Bazen de durduk yere ekran kartının sürücüsü siliniyor. DDU ile temizleyip tekrar kuruyorum, bazen de oyun esnasında siyah ekranda kalıyor, sesleri duyuyorum ama birkaç saniye sonra onlar da gidiyor reset atmak zorunda kalıyorum. Reset atınca da driver silinmiş oluyor.

Minidump;

[CODE title="Dump"]
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\M S\Desktop\122221-14203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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 = 0xfffff805`7e800000 PsLoadedModuleList = 0xfffff805`7f42a270
Debug session time: Wed Dec 22 03:24:09.233 2021 (UTC + 3:00)
System Uptime: 0 days 4:49:25.903
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`7ebf71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffa48d`122a1680=000000000000001a
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
the pagefile offset. Parameter 3 contains the page CRC value.
Parameter 4 contains the expected CRC value.
Arg2: 00000000000069b5
Arg3: 00000000b0531dc2
Arg4: 0000000015c9f86c

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3218

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 52389

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

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

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

Key : Memory.System.Errors.PageHashErrors
Value: 1

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: 122221-14203-01.dmp

BUGCHECK_CODE: 1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 69b5

BUGCHECK_P3: b0531dc2

BUGCHECK_P4: 15c9f86c

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT:
ffffa48d`122a1678 fffff805`7ed586fd : 00000000`0000001a 00000000`0000003f 00000000`000069b5 00000000`b0531dc2 : nt!KeBugCheckEx
ffffa48d`122a1680 fffff805`7ea5d971 : ffffab0e`15cd98e0 ffffffff`ffffffff 00000000`00000000 fffff300`ecb874c8 : nt!MiValidatePagefilePageHash+0x331
ffffa48d`122a1760 fffff805`7ea5bb05 : ffffa48d`0000a000 ffffa48d`122a1800 ffffa48d`122a18f0 fffff805`00000000 : nt!MiWaitForInPageComplete+0x351
ffffa48d`122a1850 fffff805`7ea9f3f8 : 00000000`c0033333 00000000`00000001 000001d9`70e9984e 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffa48d`122a1960 fffff805`7ec0535e : ffffab0e`168cb000 00000000`00000010 ffffa48d`122a1b80 ffffab0e`00000000 : nt!MmAccessFault+0x468
ffffa48d`122a1b00 00007ffd`9b01ca51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000aa`508ff060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`9b01ca51


SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: PAGE_HASH_ERRORS_0x1a_3f

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

Followup: MachineOwner[/CODE]