BSOD Windows Server 2022

Question

Buongiorno, da diversi giorni ho una schermata blu ricorrente all'avvio del computer (dopo circa 2 ore di lavoro).

Il computer è un HP ML30 G10 Plus, Ram originali HP, monodisco SATA (WD RED S500), non sono state apportate modifiche HW rilevanti.

Il Sistema operativo è un Windows Server 2022, ho già aggiornato firmware, bios, driver.

Ho anche sostituito la macchina con una identica ripreparata e il problema persiste.

Il Memory.dmp ottenuto è il seguente:

---

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

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 20348 MP (4 procs) Free x64
Product: Server, suite: TerminalServer <20000>
Edition build lab: 20348.859.amd64fre.fe_release_svc_prod2.220707-1832
Machine Name:
Kernel base = 0xfffff805`2ae00000 PsLoadedModuleList = 0xfffff805`2ba33a70
Debug session time: Wed Sep 28 15:38:12.943 2022 (UTC + 2:00)
System Uptime: 0 days 1:54:29.944
Loading Kernel Symbols
...............................................................
Page 1064d4 not present in the dump file. Type ".hh dbgerr004" for details
................................................................
..................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b3`2432f018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`2b218470 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffe701`4a73bae0=000000000000009c
3: 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: ffffe7014a73bb10
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3304

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9c

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x9c

    Key  : Bugcheck.Code.Register
    Value: 0x9c

    Key  : Dump.Attributes.AsUlong
    Value: 1000

    Key  : WER.OS.Branch
    Value: fe_release_svc_prod2

    Key  : WER.OS.Timestamp
    Value: 2022-07-07T18:32:00Z

    Key  : WER.OS.Version
    Value: 10.0.20348.859

FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE:  9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffffe7014a73bb10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  chrome.exe

STACK_TEXT:  
ffffe701`4a73bad8 fffff805`2b2f9399     : 00000000`0000009c 00000000`80000001 ffffe701`4a73bb10 00000000`00000000 : nt!KeBugCheckEx
ffffe701`4a73bae0 fffff805`2b2f98cc     : 00000000`00000004 ffffe701`4a73be50 00000000`00000000 00000000`00000004 : nt!HalpMcaReportError+0x149
ffffe701`4a73bc40 fffff805`2b2f8ac6     : 00000000`00000000 00000000`80000001 ffffe701`4a73bed0 02004c24`44c74824 : nt!HalpMceHandlerWithRendezvous+0x11c
ffffe701`4a73bc70 fffff805`2b2fb3eb     : ffffd107`7d1397b0 41012024`44c6c58b 3de8cf8b`4930c883 3d1274c0`85fffffb : nt!HalpHandleMachineCheck+0x62
ffffe701`4a73bca0 fffff805`2b356d29     : 20245c88`31cd833f 8b49d48b`49c58b44 c085ffff`fb12e8cf 74c00000`343d1974 : nt!HalHandleMcheck+0x3b
ffffe701`4a73bcd0 fffff805`2b2280be     : c68349c7`ff0d75c0 0aeb9372`03ff8304 017c880f`c085d88b 44f63345`ff330000 : nt!KiHandleMcheck+0x9
ffffe701`4a73bd00 fffff805`2b227ce8     : 00000000`00000000 00000000`00000000 00004cc0`003e0000 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffffe701`4a73be40 00007fff`4d60e702     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
000000b3`24bfac50 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`4d60e702

SYMBOL_NAME:  nt!HalpMcaReportError+149

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  149

FAILURE_BUCKET_ID:  0x9C_SPURIOUS_GenuineIntel_nt!HalpMcaReportError

OS_VERSION:  10.0.20348.859

BUILDLAB_STR:  fe_release_svc_prod2

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Grazie a chiunque riesca ad aiutarmi

Answer 1

prego, buona giornata ed alla prossima nella MS community :-)

Elvis

Answer 2

ok procedo grazie per la info

Answer 3

ciao Massimiliano,

benvenuto in community, sono Alvise

Essendo una domanda inerente Windows Server ti suggerisco di chiedere supporto nel forum dedicato ai professionisti IT, dove sapranno aiutarti meglio

https://social.technet.microsoft.com/Forums/win...

dai un occhiata anche qui

https://learn.microsoft.com/en-us/windows-hardw...

Elvis