球球大佬们帮忙分析win10蓝屏dmp!!

背景：win10系统某天系统需要更新2H22还是哪个版本失败，后面玩大作的时候会突然蓝屏，例如2k23、荒野大镖客等，以前是不会的！现在日常使用和玩英雄联盟也不会蓝屏！

蓝屏代码：WHEA_UNCORRECTABLE_ERROR (124)

尝试解决：①新买了两条内存还是蓝屏；②拔掉内存条和显卡，橡皮擦擦拭金手指重新上机，能正常玩游戏两三天，过后又会一样的蓝屏；③更新了所有驱动还是不行；④重装了四五次系统都不行，换成win11蓝屏代码变成CRITICAL PROCESS_DIED，现在已改回win10。

dmp文件解析：

Loading Dump File [C:\Users\Administrator\Desktop\021923-7406-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff806`5e400000 PsLoadedModuleList = 0xfffff806`5f02a1f0

Debug session time: Sun Feb 19 13:47:22.410 2023 (UTC + 8:00)

System Uptime: 0 days 0:58:13.188

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.........

Loading User Symbols

Loading unloaded module list

.......

Cannot read PEB32 from WOW64 TEB32 0001877f - Win32 error 0n30

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {10, ffffb4840e3ee028, ffffb483ff27d92c, ffffb483ff1bf1a0}

Probably caused by : Unknown_Image

Followup: MachineOwner

---------

 *** Memory manager detected 100223 instance(s) of page corruption, target is likely to have memory corruption.

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. Parameter 1 identifies the type of error

source that reported the error. Parameter 2 holds the address of the

WHEA_ERROR_RECORD structure that describes the error conditon.

Arguments:

Arg1: 0000000000000010, Error Source Type

Arg2: ffffb4840e3ee028

Arg3: ffffb483ff27d92c

Arg4: ffffb483ff1bf1a0

Debugging Details:

------------------

BUGCHECK_STR:  0x124_10

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

BAD_PAGES_DETECTED: 1877f

STACK_TEXT:  

ffffc60e`fb18a388 fffff806`5e9b8a1c : 00000000`00000124 00000000`00000010 ffffb484`0e3ee028 ffffb483`ff27d92c : nt!KeBugCheckEx

ffffc60e`fb18a390 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x3ec

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

Followup: MachineOwner

---------

 *** Memory manager detected 100223 instance(s) of page corruption, target is likely to have memory corruption.

2: kd> lmvm Unknown_Module

start             end                 module name

2: kd> start

*** WARNING: Unable to verify timestamp for mcupdate.dll

*** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll

*** WARNING: Unable to verify timestamp for kdcom.dll

*** ERROR: Module load completed but symbols could not be loaded for kdcom.dll

*** WARNING: Unable to verify timestamp for clipsp.sys

*** ERROR: Module load completed but symbols could not be loaded for clipsp.sys

*** WARNING: Unable to verify timestamp for qmbsecx64.sys

*** ERROR: Module load completed but symbols could not be loaded for qmbsecx64.sys

*** WARNING: Unable to verify timestamp for iaStorAC.sys

*** ERROR: Module load completed but symbols could not be loaded for iaStorAC.sys

*** WARNING: Unable to verify timestamp for WdFilter.sys

*** ERROR: Module load completed but symbols could not be loaded for WdFilter.sys

*** WARNING: Unable to verify timestamp for TSSysKit64_EV.sys

*** ERROR: Module load completed but symbols could not be loaded for TSSysKit64_EV.sys

*** WARNING: Unable to verify timestamp for nvvhci.sys

*** ERROR: Module load completed but symbols could not be loaded for nvvhci.sys

*** WARNING: Unable to verify timestamp for NvModuleTracker.sys

*** ERROR: Module load completed but symbols could not be loaded for NvModuleTracker.sys

*** WARNING: Unable to verify timestamp for orayvhid.sys

*** ERROR: Module load completed but symbols could not be loaded for orayvhid.sys

*** WARNING: Unable to verify timestamp for nvhda64v.sys

*** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for UsbHub3.sys -

*** WARNING: Unable to verify timestamp for QsDrv_x64.sys

*** ERROR: Module load completed but symbols could not be loaded for QsDrv_x64.sys

*** WARNING: Unable to verify timestamp for QMUdisk64_ev.sys

*** ERROR: Module load completed but symbols could not be loaded for QMUdisk64_ev.sys

*** WARNING: Unable to verify timestamp for HdDrv_x64.sys

球球大佬帮忙分析分析是什么原因，谢谢谢谢！！！