In order to identify the cause of a BSOD, the computer must be configured to write a memory dump file to disk. This dump file can subsequently be analyzed in WinDbg. In some cases, WinDbg is able to point to a driver as the likely root cause of the blue screen. In other cases, kernel memory may be too corrupted for that to be possible. Analyzing those second type of dumps requires expert-level know-how.
uberAgent does not analyze memory dumps, therefore it cannot suggest which driver might have caused a blue screen. Instead, uberAgent helps identify common issues that warrant further troubleshooting.
To analyze blue screens with uberAgent:
Go to the Stop Errors (Blue Screen & Power Loss) dashboard
Use the Stop errors grouped table to identify types of stop errors that happen often enough to warrant troubleshooting
Click the row in the Stop errors grouped table that you are interested in
The table Stop error detail lists all related stop errors along with timestamps, hosts, parameters and additional information
Pick one of the machines from the Stop error detail table and analyze the memory dump with WinDbg
... View more