machine check exception造成蓝屏

      dump文件
https://1drv.ms/u/s!Ag_FhimUVq78kdZ9UkTKVqNooFQh4A?e=9E2cua



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


Loading Dump File [C:\Users\jose\Desktop\082122-9390-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`56200000 PsLoadedModuleList = 0xfffff801`56e2a250
Debug session time: Sun Aug 21 21:19:08.327 2022 (UTC + 8:00)
System Uptime: 0 days 0:06:09.094
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`565f88c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9481`2c71bad0=000000000000009c
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - BugCheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors (If Param 1 is < 0x80000000)
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    AMD64 Processors (If Param 1 is > 0x80000000)
        1 - Failure Type
           VALUES:
                0x80000001: Spurious MCE
                    2 - Address of MCA_EXCEPTION structure
                0x80000002: Rendezvous failure
                    2 - Address of MCA_EXCEPTION structure
           END_VALUES
Arguments:
Arg1: 0000000080000001
Arg2: ffff94812c71bb10
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2827

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17502

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9c

    Key  : Bugcheck.Code.Register
    Value: 0x9c

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  082122-9390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffff94812c71bb10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  DrvMgr.exe

STACK_TEXT: 
ffff9481`2c71bac8 fffff801`566b5c29     : 00000000`0000009c 00000000`80000001 ffff9481`2c71bb10 00000000`00000000 : nt!KeBugCheckEx
ffff9481`2c71bad0 fffff801`566b6084     : 00000000`0000000c ffff9481`2c71be50 00000000`00000000 00000000`0000000c : nt!HalpMcaReportError+0x149
ffff9481`2c71bc40 fffff801`566b529b     : 00000000`00000000 00000000`80000001 ffff9481`2c71bed0 48000006`98858b49 : nt!HalpMceHandlerWithRendezvous+0x11c
ffff9481`2c71bc70 fffff801`566b7ae5     : ffffab0e`378f61d0 c50349d2`33a3a03f 4d000009`00858949 c7490000`09089d89 : nt!HalpHandleMachineCheck+0x5f
ffff9481`2c71bca0 fffff801`5670d529     : f1e83e89`45cd8b49 28badb33`4500003c 04b08d8d`48000000 8b49dd6a`8d440000 : nt!HalHandleMcheck+0x35
ffff9481`2c71bcd0 fffff801`566079fa     : f0ad8b4c`ea75ef2b 411974d2`8500000b 068a41ff`ffffffbb cf034901`88f7034d : nt!KiHandleMcheck+0x9
ffff9481`2c71bd00 fffff801`566076b7     : ffffbcbe`00000000 fffff801`566075ec ffffbcbe`00c00800 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9481`2c71be40 ffffbc92`52508362     : ffffa48b`3b1d3a80 ffffbcbe`00830a80 ffffbcbe`00840930 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffa48b`3b1d37e0 ffffbc92`52507f31     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`5d9c09fc : win32kfull!_FindWindowEx+0x392
ffffa48b`3b1d38b0 ffffbc92`529659e0     : 00000000`00000000 00000000`00000000 00000000`06e8e2a0 00000000`06e8e2b0 : win32kfull!NtUserFindWindowEx+0x351
ffffa48b`3b1d3950 fffff801`5660a2b5     : 00000000`00000000 00000000`074bfd50 ffffab0e`00000102 ffffab0e`650367e0 : win32k!NtUserFindWindowEx+0x20
ffffa48b`3b1d3990 00007fff`db550cd4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`06e8e268 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`db550cd4


SYMBOL_NAME:  win32kfull!_FindWindowEx+392

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.19041.1193

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  392

FAILURE_BUCKET_ID:  0x9C_SPURIOUS_GenuineIntel_win32kfull!_FindWindowEx

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e5148de0-7127-59c9-877d-6eb04ecb663c}

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - BugCheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors (If Param 1 is < 0x80000000)
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    AMD64 Processors (If Param 1 is > 0x80000000)
        1 - Failure Type
           VALUES:
                0x80000001: Spurious MCE
                    2 - Address of MCA_EXCEPTION structure
                0x80000002: Rendezvous failure
                    2 - Address of MCA_EXCEPTION structure
           END_VALUES
Arguments:
Arg1: 0000000080000001
Arg2: ffff94812c71bb10
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2311

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2469

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9c

    Key  : Bugcheck.Code.Register
    Value: 0x9c

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  082122-9390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffff94812c71bb10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  DrvMgr.exe

STACK_TEXT: 
ffff9481`2c71bac8 fffff801`566b5c29     : 00000000`0000009c 00000000`80000001 ffff9481`2c71bb10 00000000`00000000 : nt!KeBugCheckEx
ffff9481`2c71bad0 fffff801`566b6084     : 00000000`0000000c ffff9481`2c71be50 00000000`00000000 00000000`0000000c : nt!HalpMcaReportError+0x149
ffff9481`2c71bc40 fffff801`566b529b     : 00000000`00000000 00000000`80000001 ffff9481`2c71bed0 48000006`98858b49 : nt!HalpMceHandlerWithRendezvous+0x11c
ffff9481`2c71bc70 fffff801`566b7ae5     : ffffab0e`378f61d0 c50349d2`33a3a03f 4d000009`00858949 c7490000`09089d89 : nt!HalpHandleMachineCheck+0x5f
ffff9481`2c71bca0 fffff801`5670d529     : f1e83e89`45cd8b49 28badb33`4500003c 04b08d8d`48000000 8b49dd6a`8d440000 : nt!HalHandleMcheck+0x35
ffff9481`2c71bcd0 fffff801`566079fa     : f0ad8b4c`ea75ef2b 411974d2`8500000b 068a41ff`ffffffbb cf034901`88f7034d : nt!KiHandleMcheck+0x9
ffff9481`2c71bd00 fffff801`566076b7     : ffffbcbe`00000000 fffff801`566075ec ffffbcbe`00c00800 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9481`2c71be40 ffffbc92`52508362     : ffffa48b`3b1d3a80 ffffbcbe`00830a80 ffffbcbe`00840930 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffa48b`3b1d37e0 ffffbc92`52507f31     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`5d9c09fc : win32kfull!_FindWindowEx+0x392
ffffa48b`3b1d38b0 ffffbc92`529659e0     : 00000000`00000000 00000000`00000000 00000000`06e8e2a0 00000000`06e8e2b0 : win32kfull!NtUserFindWindowEx+0x351
ffffa48b`3b1d3950 fffff801`5660a2b5     : 00000000`00000000 00000000`074bfd50 ffffab0e`00000102 ffffab0e`650367e0 : win32k!NtUserFindWindowEx+0x20
ffffa48b`3b1d3990 00007fff`db550cd4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`06e8e268 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`db550cd4


SYMBOL_NAME:  win32kfull!_FindWindowEx+392

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.19041.1193

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  392<365>
FAILURE_BUCKET_ID:  0x9C_SPURIOUS_GenuineIntel_win32kfull!_FindWindowEx

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e5148de0-7127-59c9-877d-6eb04ecb663c}

Followup:     MachineOwner
---------      你好,frankjose1，感谢联系本站！建议卸载一下360驱动大师，然后如何在Windows中执行干净启动(microsoft.com)看下是否恢复正常。