A user was running the Analyze BSOD minidumps script as System instead of SIP service start, and it was successful the first time and then stopped working. It was recommended to delete some data in HKLM and to empty the data index unless it was changed. The user also wanted the script to write to an index and device events, and was informed that these were not mutually exclusive.
Read the entire ‘Troubleshooting Analyze BSOD Minidumps Script Issues’ thread below:
I’m trying out the new "Analyze BSOD minidumps" script. I changed the trigger to run as System instead of SIP service start (org policy reasons). It ran once successfully. Since then, it will not run anymore. What did I break?
HKLM:\SOFTWARE\Avacee\SIP\Scripts\BSODit tracks which blue screens have been processed
Ah, okay. Deleted them out. Output failed first time but went through again second time. Good deal. I can make that work.
You might also want to empty the data index that the script writes to (unless you also changed that)
Ah never mind. Seems like the checkbox is disabled by default.
Yea I left it off. It would be great if I could get it to go into both an index and the device events.
they aren’t mutually exclusive
Continue reading and comment on the thread ‘Troubleshooting Analyze BSOD Minidumps ControlUp Script Issues’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers