I'm reaching out for assistance with a frustrating issue we've been experiencing. Recently, we learned from one of our clients about a problem where several of their computers become unresponsive, either during logins or while in regular use, requiring a power cycle to function again. Initially, we thought this was isolated to one client, but after investigations, we found that this was affecting many more PCs than anticipated. We've analyzed event logs, and up to 20 out of 40 machines were forcibly rebooted for unclear reasons.
Compiling evidence from our ~400 endpoints, it turns out over 200 computers have been power cycled in the past month, with 117 just in the last week. So far, the feedback from users suggests similar experiences—they find their computers unresponsive when they arrive in the morning or during logins. While there is clearly a larger issue at play, I doubt every affected computer has the same root cause since end users can behave unpredictably. The machines vary widely in age, specs, and operating systems (Windows 10/11, different builds). Notably, we noticed that most instances of Event ID 41 happened after Windows updates on June 15th. I'd appreciate any guidance or insight, as I'm feeling stuck with this problem!
2 Answers
It sounds like you might want to dig into the commonalities between these crashing systems. Given that they're all running Ninja, Huntress, ControlD, and RoboShadow agent, see if there's any correlation there. Sometimes system management tools can introduce their own quirks, especially after updates. Maybe check if there's a recent issue with any of these applications or their compatibility with the latest Windows updates.
You might consider isolating the machines that experience this issue and reviewing their recent update history, especially around that June 15th mark. If it seems tied to the updates, delaying those updates or rolling them back could reveal the culprit. Also, checking for BIOS updates might help. Old hardware specs can react differently to newer Windows builds, particularly after major updates.
Really good idea about the BIOS updates! Sometimes, they can be a game-changer when it comes to compatibility issues. Better to be safe and rule that out.
That's a solid point! Running software like that can sometimes lead to unexpected behaviors, especially if there's been a recent update. I wonder if other users have seen issues linked to specific versions of those tools?