Skip to main content
Configure Windows alerts to identify unexpected restarts and blue screens on managed devices. Before creating a rule, check the log, the identifier and the source of the event on a representative device.
The source names in the table are identification references. To configure Source, copy the Provider Name value from the XML of the actual event, since the same identifier can exist in different sources. Events 41 and 6008 do not prove a blue screen on their own.

Configure the alerts

  1. Check the collection. Verify that the required events reach the Event log. If any are missing, add their Event ID to the FlexxAgent configuration and check the next collection cycle.
  2. Create the rule. Go to Monitor → Alert settings and create an alert with a name, Event ID and Source. Use Search text when you need to filter a fragment of the event message.
  3. Separate the causes. Configure unexpected restart detection and bugcheck detection with identifiable criteria. If you use message text, check that it matches the Windows language of the device.
  4. Enable the notification. Enable the alert and configure the email recipients or the associated webhook. Check that the notification identifies the device and the triggered rule.
  5. Check the result. Match the Windows event with the alert record and the notification received. Review the timing after the device’s communication is restored.

Interpret the results

The event information may allow you to identify the bugcheck code, but its absence does not by itself rule out a failure of that type. When there is not enough evidence to pinpoint the cause, keep the unexpected restart classification. Repeated events may keep the same alert active per device. The configured repetition determines subsequent notifications; it does not necessarily mean a separate alert or ticket for each occurrence.

Related information