经常蓝屏，使用windbg检查为probably caused by : unknown_image ( page_not_zero ) ，请问是因为什么？

      Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\林\Desktop\072522-15343-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff802`10e00000 PsLoadedModuleList = 0xfffff802`11a2a230 Debug session time: Mon Jul 25 17:48:42.389 2022 (UTC + 8:00) System Uptime: 0 days 4:08:14.199 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck A, {0, 2, 0, fffff80211027c82}  Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )  Followup: MachineOwner ---------   *** Memory manager detected 86567 instance(s) of page corruption, target is likely to have memory corruption.  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield :     bit 0 : value 0 = read operation, 1 = write operation     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80211027c82, address which referenced memory  Debugging Details: ------------------   READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd  0000000000000000   CURRENT_IRQL:  2  FAULTING_IP:  nt!KeSetEvent+92 fffff802`11027c82 498b4500        mov     rax,qword ptr [r13]  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  BUGCHECK_STR:  0xA  PROCESS_NAME:  WeChat.exe  BAD_PAGES_DETECTED: 15227  LAST_CONTROL_TRANSFER:  from fffff8021120a569 to fffff802111f8590  STACK_TEXT:   fffffe8c`0b25e7a8 fffff802`1120a569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffe8c`0b25e7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69   STACK_COMMAND:  kb  SYMBOL_NAME:  PAGE_NOT_ZERO  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 86567 instance(s) of page corruption, target is likely to have memory corruption.  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield :     bit 0 : value 0 = read operation, 1 = write operation     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80211027c82, address which referenced memory  Debugging Details: ------------------   READ_ADDRESS:  0000000000000000   CURRENT_IRQL:  2  FAULTING_IP:  nt!KeSetEvent+92 fffff802`11027c82 498b4500        mov     rax,qword ptr [r13]  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  BUGCHECK_STR:  0xA  PROCESS_NAME:  WeChat.exe  BAD_PAGES_DETECTED: 15227  LAST_CONTROL_TRANSFER:  from fffff8021120a569 to fffff802111f8590  STACK_TEXT:   fffffe8c`0b25e7a8 fffff802`1120a569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffe8c`0b25e7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69   STACK_COMMAND:  kb  SYMBOL_NAME:  PAGE_NOT_ZERO  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 86567 instance(s) of page corruption, target is likely to have memory corruption.  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield :     bit 0 : value 0 = read operation, 1 = write operation     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80211027c82, address which referenced memory  Debugging Details: ------------------   READ_ADDRESS:  0000000000000000   CURRENT_IRQL:  2  FAULTING_IP:  nt!KeSetEvent+92 fffff802`11027c82 498b4500        mov     rax,qword ptr [r13]  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  BUGCHECK_STR:  0xA  PROCESS_NAME:  WeChat.exe  BAD_PAGES_DETECTED: 15227  LAST_CONTROL_TRANSFER:  from fffff8021120a569 to fffff802111f8590  STACK_TEXT:   fffffe8c`0b25e7a8 fffff802`1120a569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffe8c`0b25e7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69   STACK_COMMAND:  kb  SYMBOL_NAME:  PAGE_NOT_ZERO  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 86567 instance(s) of page corruption, target is likely to have memory corruption.      Hi鹏吴IamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
        hiDaveIamverygladtoreceiveyourreplyPleaseusethelinkbelowtodownloadthe.DMPIuploadedThanksforcheckingitforme.https://share.weiyun.com/8kuKqxYU此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        Hi鹏吴,Iamsorry,thatwebsiteisalsonotallowingmetologin,itwantsmetologinandscanaQRCodewithasmartphone,andwillnotacceptmydetails.___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        hiplzcheckthishttps://1drv.ms/u/s!Aiqxkt5n1qLFiDOl24vZfRfUz5jq?e=4vYOMN此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        Hi鹏吴,Thankyou,Iwasabletoaccessthatlink.Yourminidumpfilesindicatesmemory(RAM)corruptionandthechipsetdevicedriverasthecauseofthecrashes.1GotothesupportpageforyourPCorMotherboardonthemanufacturerswebsite,thenfromthere,downloadandinstalltheversionofChipsetdriverstheyrecommendandwhilethere,checkforanyBIOSupdatethatmayneedtobeinstalled2Waittoseeifyoursystemstabilizes,ifnot,thebestoptionistodownloadthewidelyavailablefreeutilityMemTest86,thenrunafull4passscanwiththattotestyourRAMforphysicalerrors___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。