win10蓝屏，0x80_4f4454_genuineintel_noerrrec_image_genuineintel.sys是哪里出问题了

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


Loading Dump File [C:\Users\cyf\Desktop\092822-68687-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 18362 MP (48 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`35000000 PsLoadedModuleList = 0xfffff807`35445ed0
Debug session time: Wed Sep 28 15:00:26.558 2022 (UTC + 8:00)
System Uptime: 0 days 2:56:00.686
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`351c44c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffab81`b3a917a0=0000000000000080
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction.  The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454, 'TDO'
Arg2: 0000000000000000, Status Byte
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: Record                                        ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1421

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14646

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x80

    Key  : Bugcheck.Code.Register
    Value: 0x80

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


FILE_IN_CAB:  092822-68687-01.dmp

BUGCHECK_CODE:  80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffab81`b3a91798 fffff807`34fa4421     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffab81`b3a917a0 fffff807`31eb6920     : fffff807`34fcb6e0 00000000`00000000 ffffcc03`0b1d98f8 00000000`00000000 : hal!HalBugCheckSystem+0x81
ffffab81`b3a917e0 fffff807`3533f902     : fffff807`34fcb6e0 ffffab81`b3a91869 00000000`00000000 ffffcc03`0b1d98f8 : PSHED!PshedBugCheckSystem+0x10
ffffab81`b3a91810 fffff807`34fa72b0     : 00000000`00000001 00000000`00000020 00000000`00000000 fffff807`3558b680 : nt!WheaReportHwError+0x382
ffffab81`b3a918d0 fffff807`352a40bc     : 00000000`00000001 00000000`00000000 ffffab81`b3a80180 fffff807`352b5310 : hal!HalHandleNMI+0x110
ffffab81`b3a91900 fffff807`351cfa82     : ffffab81`b3a80180 ffffab81`b3a91b10 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x13c
ffffab81`b3a91950 fffff807`351cf852     : ffffab81`b3a80180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffab81`b3a91a90 fffff807`35033cc7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
fffffa04`a8c4efe0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeResumeClockTimerFromIdle+0x77


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}

Followup:     MachineOwner
---------      Hi,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好于福成，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
        https://1drv.ms/u/s!Ao7p0JW7qG-vgzxDDU_YNc26fXyX?e=66G0vm您看下这个链接是否可用，谢谢！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        你好于福成，感谢分享minidump文件。minidump文件指示GenuineIntel.sys。通常，如果您对CPU进行超频或硬件出现故障，则会导致该错误。创建系统还原点，然后尝试按照以下步骤解决此问题：1-如果您对处理器进行了超频，我建议您将其重置为基本时钟。2-仅从制造商的网站将BIOS更新到最新版本。3-检查所有冷却系统（如风扇）是否正常工作。4-如果您更改了BIOS上的任何配置，我建议您将其重置为默认值。5-你可以用Prime95测试CPU：https://www-tenforums-com.translate.goog/tutori.如果您需要进一步的帮助，请告诉我并让我更新。______________________________________________________________________标准免责声明：有非Microsoft网站的链接。这些页面似乎提供了准确、安全的信息。请
        好的，
        Youaremostwelcome.Gladtohelp
        不用客气。乐意效劳