Question Multiple blue screen

Mar 31, 2022
7
0
10
0
Full dump http://www.mediafire.com/file/x237apt7262fpmn/Minidump.rar

Code:
*******************************************************************************
*                                                                             *
*                        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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa98567a02028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2906

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7599

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  033122-2218-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa98567a02028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8000`82ffd918 fffff805`6850117b     : 00000000`00000124 00000000`00000000 ffffa985`67a02028 00000000`be000000 : nt!KeBugCheckEx
ffff8000`82ffd920 fffff805`6cea10c0     : 00000000`00000000 ffff8000`82ffd9f9 ffffa985`67a02028 ffffa985`67a02028 : nt!HalBugCheckSystem+0xeb
ffff8000`82ffd960 fffff805`6863f043     : 00000000`00000000 ffff8000`82ffd9f9 ffffa985`67a02028 ffffa985`601da500 : PSHED!PshedBugCheckSystem+0x10
ffff8000`82ffd990 fffff805`68502b6d     : ffffa985`66bb0c00 ffffa985`66bb0c00 ffffa985`601da550 bfebfbff`7ffafbff : nt!WheaReportHwError+0x393
ffff8000`82ffda60 fffff805`68502fb8     : 00000000`00000009 ffffa985`00000003 fffffb04`8d0a9000 00000000`00000009 : nt!HalpMcaReportError+0xb1
ffff8000`82ffdbc0 fffff805`68502e4c     : ffffa985`5ff4f530 006c0064`00000001 00000000`00000000 00010000`0000000c : nt!HalpMceHandlerCore+0x138
ffff8000`82ffdc20 fffff805`685030f1     : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00059000 : nt!HalpMceHandler+0xe0
ffff8000`82ffdc60 fffff805`685022b6     : 00000000`00000000 00000000`00000000 ffff8000`82ffdef0 00000000`00560068 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8000`82ffdc90 fffff805`68504c6b     : ffffa985`5ff4f530 01d844c0`bc57e883 01d84497`05d53ff7 00000000`00089000 : nt!HalpHandleMachineCheck+0x62
ffff8000`82ffdcc0 fffff805`68564ed9     : 00650063`0073000a 002e0076`00720073 0055006c`006c0064 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffff8000`82ffdcf0 fffff805`684251fe     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff8000`82ffdd20 fffff805`68424e28     : 00000000`00000010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff8000`82ffde60 fffff805`8243153f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
fffffb04`8d0aee58 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup:     MachineOwner
---------
Code:
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc0018b893180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2202

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3330

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  033122-2578-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffffc0018b893180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffc001`8baac9e8 fffff803`576ab93e     : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffc001`8b893180 : nt!KeBugCheckEx
ffffc001`8baac9f0 fffff803`574db061     : 00000000`00000000 ffffc001`8ba40180 ffff0bb0`39c7b724 fffff803`5743d1f0 : nt!KeAccumulateTicks+0x1d06fe
ffffc001`8baaca60 fffff803`574d8096     : 00000000`00004238 00000000`00002778 00000000`9de27431 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffffc001`8baacac0 fffff803`574d93a2     : ffffaa07`8f8496f0 00000000`00000000 fffff803`57e2b490 00000000`00000000 : nt!KiUpdateTime+0x686
ffffc001`8baaceb0 fffff803`574d6cd2     : ffffaa07`8f8496f0 ffffd587`961377d0 ffffd587`00000000 00000000`0000000c : nt!KeClockInterruptNotify+0x272
ffffc001`8baacf40 fffff803`5748d6a0     : 00000000`9df93211 ffffd587`96137720 00000000`00000001 0000016e`4eed3ea0 : nt!HalpTimerClockInterrupt+0xe2
ffffc001`8baacf70 fffff803`5761719a     : ffffaa07`8f849770 ffffd587`96137720 00000000`00000000 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa0
ffffc001`8baacfb0 fffff803`57617767     : ffffaa07`8f849d00 00000000`00000004 00000000`00000002 ffffc001`8ba43250 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffaa07`8f8496f0 fffff803`5755ee60     : ffffaa07`8f849d00 ffffc001`8ba40180 00000000`00000000 ffffaa07`8f849d00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffaa07`8f849880 fffff803`5755eb2f     : 00000000`00000001 ffffab80`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2b0
ffffaa07`8f849920 fffff803`575252c3     : ffffaa07`8f849e20 00000000`00000000 00000000`00000000 ffffab80`00000000 : nt!MiAgeWorkingSetTail+0xef
ffffaa07`8f849950 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x503


SYMBOL_NAME:  nt!KeAccumulateTicks+1d06fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1d06fe

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc081e4b23028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2749

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7778

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  040122-5265-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc081e4b23028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8201`4b79a918 fffff801`2a70169b     : 00000000`00000124 00000000`00000000 ffffc081`e4b23028 00000000`be000000 : nt!KeBugCheckEx
ffff8201`4b79a920 fffff801`295510c0     : 00000000`00000000 ffff8201`4b79a9f9 ffffc081`e4b23028 ffffc081`e4b23028 : nt!HalBugCheckSystem+0xeb
ffff8201`4b79a960 fffff801`2a83fa33     : 00000000`00000000 ffff8201`4b79a9f9 ffffc081`e4b23028 ffffc081`dd1c9750 : PSHED!PshedBugCheckSystem+0x10
ffff8201`4b79a990 fffff801`2a70308d     : ffffc081`e397c900 ffffc081`e397c900 ffffc081`dd1c97a0 bfebfbff`7ffafbff : nt!WheaReportHwError+0x393
ffff8201`4b79aa60 fffff801`2a7034d8     : 00000000`0000000b ffffc081`00000003 ffffa80b`428c9000 00000000`0000000b : nt!HalpMcaReportError+0xb1
ffff8201`4b79abc0 fffff801`2a70336c     : ffffc081`dcf406d0 00000000`00000001 00000000`00000000 00000000`0000000c : nt!HalpMceHandlerCore+0x138
ffff8201`4b79ac20 fffff801`2a703611     : 00000000`00000010 00000000`00000001 00000000`00000000 01d7d186`5b183ac8 : nt!HalpMceHandler+0xe0
ffff8201`4b79ac60 fffff801`2a7027d6     : 00000000`00000000 00000000`00000000 ffff8201`4b79aef0 00000000`00000020 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8201`4b79ac90 fffff801`2a70518b     : ffffc081`dcf406d0 00010000`0000c52d 00000000`00500060 00010000`00000d49 : nt!HalpHandleMachineCheck+0x62
ffff8201`4b79acc0 fffff801`2a765769     : 01d844c0`5b2e620e 01d75a02`fe17c7ad 00000000`00065000 00000000`00064f68 : nt!HalHandleMcheck+0x3b
ffff8201`4b79acf0 fffff801`2a6265fe     : 006c006c`0064002e 00010000`0000c531 00000000`00500060 00010000`00000d49 : nt!KiHandleMcheck+0x9
ffff8201`4b79ad20 fffff801`2a626228     : 00000000`00000010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff8201`4b79ae60 fffff801`5075153f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
ffffa80b`428cee58 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup:     MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        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: ffff9280edd64b30
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1421

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3161

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  033122-2906-01.dmp

BUGCHECK_CODE:  9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffff9280edd64b30

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

STACK_TEXT:
ffff9280`edd64af8 fffff802`04102c05     : 00000000`0000009c 00000000`80000001 ffff9280`edd64b30 00000000`00000000 : nt!KeBugCheckEx
ffff9280`edd64b00 fffff802`04103144     : 00000000`00000010 ffff9280`edd64e70 00000000`00000000 00000000`00000010 : nt!HalpMcaReportError+0x149
ffff9280`edd64c60 fffff802`041022b6     : 00000000`00000000 00000000`80000001 ffff9280`edd64ef0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0x11c
ffff9280`edd64c90 fffff802`04104c6b     : ffffa582`bdd4ef30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
ffff9280`edd64cc0 fffff802`04164ed9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffff9280`edd64cf0 fffff802`040251fe     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffff9280`edd64d20 fffff802`04024e28     : 00000000`00000010 00000000`00000000 00000000`2a31d957 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff9280`edd64e60 fffff802`03f15146     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
fffffa85`98765ab0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x406


SYMBOL_NAME:  nt!HalpMcaReportError+149

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  149

FAILURE_BUCKET_ID:  0x9C_SPURIOUS_GenuineIntel_nt!HalpMcaReportError

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a9a2544d-92f1-c788-380e-cd2d56034c4a}

Followup:     MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8a806bed2180, The PRCB address of the hung processor.
Arg4: 000000000000000d, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2359

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2410

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  033122-2406-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffff8a806bed2180

BUGCHECK_P4: d

FAULTING_PROCESSOR: d

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Taskmgr.exe

STACK_TEXT:
fffff807`59cd39e8 fffff807`5beab93e     : 00000000`00000101 00000000`0000000c 00000000`00000000 ffff8a80`6bed2180 : nt!KeBugCheckEx
fffff807`59cd39f0 fffff807`5bcdb061     : 00000000`00000000 fffff807`59a65180 ffffb47b`65431207 fffff807`5bc3d1f0 : nt!KeAccumulateTicks+0x1d06fe
fffff807`59cd3a60 fffff807`5bcd8096     : 00000000`00003130 00000000`00001d51 00000000`754771c9 00000000`00000000 : nt!KiUpdateRunTime+0x61
fffff807`59cd3ac0 fffff807`5bcd93a2     : fffff606`45e96460 00000000`00000000 fffff807`5c62b490 00000000`00000000 : nt!KiUpdateTime+0x686
fffff807`59cd3eb0 fffff807`5bcd6cd2     : fffff606`45e96460 fffff807`5c6f7d60 fffff807`00000000 00000000`0000000c : nt!KeClockInterruptNotify+0x272
fffff807`59cd3f40 fffff807`5bc8d6a0     : 00000000`755e2f0c fffff807`5c6f7cb0 00000000`00000001 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff807`59cd3f70 fffff807`5be1719a     : fffff606`45e964e0 fffff807`5c6f7cb0 000000a5`b98c48d9 ffffffff`ffffffff : nt!KiCallInterruptServiceRoutine+0xa0
fffff807`59cd3fb0 fffff807`5be17767     : 00000000`0df2d510 00000000`00000001 00000000`00000002 fffff807`59a68250 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff606`45e96460 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+1d06fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1d06fe

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
 
Mar 31, 2022
7
0
10
0
You can see the problem in dump files.

The specification:
  • Intel i9 11900K
  • MSI Z590 Gaming Carbon Wi-Fi
  • MSI RTX 3050 Gaming X
  • Corsair Vengeance RGB Pro (2x16) 32 GB 3600 MHz
 

USAFRet

Titan
Moderator
Mar 16, 2013
156,078
11,667
176,090
24,257
You can see the problem in dump files.

The specification:
  • Intel i9 11900K
  • MSI Z590 Gaming Carbon Wi-Fi
  • MSI RTX 3050 Gaming X
  • Corsair Vengeance RGB Pro (2x16) 32 GB 3600 MHz
Unlikely anyone is going to just read through those, without some backstory.

What were you doing, what are the temperatures of the system, etc, etc.

The unstated and usually VERY important part...the PSU in this?
 
Reactions: Niydayoltu
Mar 31, 2022
7
0
10
0
Unlikely anyone is going to just read through those, without some backstory.

What were you doing, what are the temperatures of the system, etc, etc.

The unstated and usually VERY important part...the PSU in this?
What were you doing? Nothing, just opening the computer.

What are the temperatures of the system? The temperatures are not high

the PSU in this? MSI 850W
 
Mar 31, 2022
7
0
10
0
You have 2 PC with problems? Talk about bad luck.

its probably hardware of some sort

2 whea errors
1 Machine Check exception
2 Clock Watchdog Timeout

you got the full set. They all likely to be hardware

I would run this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

Do you have newest bios?

what storage devices do you have?
I have newest BIOS and ran that test, the CPU passed.

I will share the storage devices soon.
 
Nov 4, 2021
12
2
15
0
I have newest BIOS and ran that test, the CPU passed.

I will share the storage devices soon.

Go into bios and disable INTEL TURBO BOOST ADAPTIVE TECHNOLOGY. I had the same problem as you when I upgraded all my components in my system. Asus turbo mode and intel turbo boost adaptive technology where the main culprits. I disabled those in the bios and have never gotten another bsod since. Hope this helps 👍
 
Reactions: Niydayoltu
first one was just the cpu reporting a unknown error on processor 0 cache bank 0
Processor Version 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz
Current Speed 3500MHz
Product MPG Z590 GAMING CARBON WIFI (MS-7D06)
BIOS Version 1.60
BIOS Starting Address Segment f000
BIOS Release Date 01/14/2022

found the problem: will take a minute to write it up.
you have 5 copies of overclocking software running, each copy takes a wack at overclocking the cpu and tweaking the cpu voltages until they get out of range and cause this bugcheck.

you should download autoruns from here: https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

then find the drivers and remove each one by deleting its entry. then reboot
(generally, you should not overclock but if you do you should only use one version.)
kind of a stupid setup program that does not look for other copies of itself already installed.

------------
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Thu Jun 18 04:55:42 2020
C:\Program Files (x86)\MSI\MSI Center\Super Charger\NTIOLib_X64.sys Sun Jul 9 19:11:47 2017
C:\Program Files (x86)\MSI\MSI Center\Mystic Light\Lib\NTIOLib_X64.sys Sun Jul 9 19:13:57 2017
C:\Program Files (x86)\MSI\MSI Center\Lib\SYS\NTIOLib_X64.sys Wed Nov 3 22:08:28 2021
C:\Program Files (x86)\MSI\MSI Center\Lib\NTIOLib_X64.sys Sun Jul 9 18:54:30 2017
 
Last edited:
Reactions: Niydayoltu
Mar 31, 2022
7
0
10
0
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Thu Jun 18 04:55:42 2020
C:\Program Files (x86)\MSI\MSI Center\Super Charger\NTIOLib_X64.sys Sun Jul 9 19:11:47 2017
C:\Program Files (x86)\MSI\MSI Center\Mystic Light\Lib\NTIOLib_X64.sys Sun Jul 9 19:13:57 2017
C:\Program Files (x86)\MSI\MSI Center\Lib\SYS\NTIOLib_X64.sys Wed Nov 3 22:08:28 2021
C:\Program Files (x86)\MSI\MSI Center\Lib\NTIOLib_X64.sys Sun Jul 9 18:54:30 2017
What should I do? Remove them?
 
What should I do? Remove them?
use autoruns to and delete each entry. if you later need one , you can reinstall. the setup assumes you removed the old version,
this would not have been a problem but the setup has changed the installation directory over the years. When windows sees the driver load and collides with a driver of the same name it loads it again but at a offset and you get several different versions of the same driver loaded. Causes a lot of problems
 

ASK THE COMMUNITY

TRENDING THREADS