Tip : BlueScreen Monitoring

Samuel MONIER
Samuel MONIER Member, Cerified Business Partner Posts: 18 ✭✭✭
edited May 14 in Remote Monitoring

Hello everyone,

I think that tip can be very relevant for all the technicians who want to be more proactive.

Let's see how you can monitor all crash on computers, with bluescreen. Don't wait for customer call, let's apply that thershold to detect BSOD just when it happens.

Here is the threshold :

2024-05-15 00_44_31-Atera - RMM software _ PSA & Remote Access for MSPs.png

That's in French as you see, but nothing difficult here.
Just add a threshold on System source, critical event, with ID 1001.
And that's all !

I think it's really an interesting element to monitor, which allows you to anticipate serious problems when crashes become recurrent.

For us, since we implemented it, we are very satisfied with the result ! So I'm happy to share that with you.

Have fun with ATERA !

Comments

  • BEKAHENI
    BEKAHENI Member Posts: 15 ✭✭

    So simple, so brilliant :)

  • BEKAHENI
    BEKAHENI Member Posts: 15 ✭✭
    edited May 15

    Do we have Tip of the day /week / month !! on this forum ??

  • mjones
    mjones Member Posts: 185 ✭✭✭✭

    Adding this to my thresholds right now!

  • mjones
    mjones Member Posts: 185 ✭✭✭✭

    Settings in English:

    image.png

  • Samuel MONIER
    Samuel MONIER Member, Cerified Business Partner Posts: 18 ✭✭✭

    @mjones I'll try to post another tips.
    And for all will trying that threshold, please confirm that it works for you !
    And share yours ;)

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭
    image.png

    image.png

    image.png

    image.png

    Here are a few more

  • AlanC
    AlanC Member Posts: 1 ✭

    Hi Samuel

    Thank you - I have been amazed as to how many BSOD have been detected

    I have been using WinDbg to analyse them - are there any other suggestions as I notice BSOD becoming more common with Win 11

  • Samuel MONIER
    Samuel MONIER Member, Cerified Business Partner Posts: 18 ✭✭✭

    Hi @AlanC

    I'm happy that my tip let you have a good experience with ATERA.

    Most of time BSOD occured because of bad drivers.
    WinDbg will help you to check wich drivers cause the issue.
    But sometime you only have ntokrln.exe in failure, and it doesn't help…
    In that case we check memory and cpu by testing it.

    BSOD causes are sometime very hard to find. Good luck !!
    But now, you have warnings when it occure, instead of users who call to complain 😉

Topics