Exchange servers BSOD after E2019 CU11 and E2016 CU22

%3CLINGO-SUB%20id%3D%22lingo-sub-3025825%22%20slang%3D%22en-US%22%3EExchange%20servers%20BSOD%20after%20E2019%20CU11%20and%20E2016%20CU22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3025825%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20applying%20CU11%20to%20Exchange%202019%20servers%20and%20CU22%20to%20E2016%20servers%20several%20of%20them%20are%20BSOD%20rebooting%20caused%20by%20ActiveMonitoring%2C%20Identity%3A%20ServiceHealthActiveManagerForceReboot.%20Event%20ID%209009%20(a%20Warning%20only).%20No%20real%20clues%20anywhere%20why.%3C%2FP%3E%3CP%3E2%20x%20E2019%20(on%20Windows%20Server%202019)%20in%20one%20DAG%2C%202%20x%20E2016%20(on%20Windows%20Server%202021R2)%20in%20another%20DAG.%20Part%20way%20through%20Hybrid%20migration%20to%20O365.%20All%20serve%3C%2FP%3E%3CP%3EAll%20running%20as%20VMs%20on%20Nutanix%20AHV.%3C%2FP%3E%3CP%3ESeems%20some%20sort%20of%20Throttling%20is%20active%2C%20but%20cannot%20identify%20or%20quantify.%20Plenty%20of%20resources%20for%20all%20VMs.%3C%2FP%3E%3CP%3EAnyone%20else%20having%20these%20BSOD%3F%3C%2FP%3E%3CP%3ERay%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3025825%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Visitor

Since applying CU11 to Exchange 2019 servers and CU22 to E2016 servers several of them are BSOD rebooting caused by ActiveMonitoring, Identity: ServiceHealthActiveManagerForceReboot. Event ID 9009 (a Warning only). No real clues anywhere why.

2 x E2019 (on Windows Server 2019) in one DAG, 2 x E2016 (on Windows Server 2021R2) in another DAG. Part way through Hybrid migration to O365. All serve

All running as VMs on Nutanix AHV.

Seems some sort of Throttling is active, but cannot identify or quantify. Plenty of resources for all VMs.

Anyone else having these BSOD?

Ray

 

 

0 Replies