A user inquired about seeing the ControlUp Agent starting before a BSOD on their machines. Another user suggested that the BSOD could have happened while the agent was not connected, and the details were only captured once the agent was started. The ControlUp agent is designed to capture BSOD details after the machine boots up from the blue screen.
Read the entire ‘Exploring the Cause of BSOD with ControlUp Agent’ thread below:
So I have a question. We started to track the BSOD my company is having with Control Up. What I did notice is that in almost all cases we see, We see the Control Up Agent start a minute or two before the BSOD. Anyone experience this before? Now I will say we have Control Up running on almost 5,000 Pc’s and we only see the BSOD on about 20 PC’s a day.
the bsod could have happened while the machine was not connected/agent not started yet so it only uploaded the data once the agent was started. That could at least partially explain thyis
the ControlUp agent captures the BSOD details after the machine boots up from the blue screen, so this is the expected behaviour
Continue reading and comment on the thread ‘Exploring the Cause of BSOD with ControlUp Agent’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops