Symptoms

SPB has encountered Bugcheck code 03402127 on xx/xx/xxxx xx:xx:xx.B 12/09/19 11:44:37 BugCheck 3e9 DynStrings:0x00000000 (0x0000000000000000, 0x0000000003402127, 0xfffff881449dc460, 0x0000000000000000)C:\dumps\crash.dmp120919-47159-01 [SAS_CTLR_SPC_RESP_HW_EVENT_ACK_FAILED <SAS>]B 12/09/19 11:53:51 DGSSP 76008106 The Storage Processor rebooted unexpectedly @ 11:38:42 on 12/09/2019: BugCheck 0, {0000000000000000, 0000000003402127, fffff881449dc460, 0000000000000000}, Failing Instruction: 0xfffff88002912308 in saspmc.sys loaded @ 0xfffff880026b8000 [SAS_CTLR_SPC_RESP_HW_EVENT_ACK_FAILED <SAS>] 

Cause

SPB has encountered Bugcheck code 0x00000000 (SAS_CTLR_SPC_RESP_HW_EVENT_ACK_FAILED) on 12/09/2019 11:43:55.BE1 experienced fatal SAS controller error.- In an attempt to recover the SAS controller, the SASPMC driver issues a device reset which seems to have not completed successfully.- The only way to recover then is to panic the SP which causes a hard reset of the SAS controller; This is how the SASPMC driver works (FAD).

Resolution

A single instance of this panic is not significant (considering the quantity of transactions that occur). It is recommended to replace the Base Module [which contains SAS BE0/BE1 ports].

Support Cases