3 ms·
The most useful tool I've seen from here is BlueScreenView (https://www.nirsoft.net/utils/blue_screen_view.html https://www.nirsoft.net/utils/blue_screen_view.h
by da_chicken 8y ago
The most useful tool I've seen from here is BlueScreenView (https://www.nirsoft.net/utils/blue_screen_view.html https://www.nirsoft.net/utils/blue_screen_view.html).
Blue screens on Windows aren't remotely as common as people think they are, but this tool will look at your dump file and can tell you very quickly what caused the error (typically, which driver). Back in the day this helped to identify a problem from the network driver that was affecting a certain subset of our workstations and allowed us to determine just how widespread the scope of the problem was. Turned out the image maintainer had used the wrong network driver.
We could have used WinDbg to do this, but at the time you had to install the whole damn Windows SDK to get it. This was a single executable and a library (I think).
- sbr464 8y agoFor me, there was one that would transfer/edit the autocomplete files in Outlook, when formatting or transferring to a new computer, or fixing Exchange migration issues. Previously with IT client work (2002-2015 before cloud email took over) it was a godsend.
- da_chicken 8y agoN2KEdit. Yeah, that's a good one, too. Another case of an automated feature becoming too smart for it's own good.
- dkrikun 8y agowinlister for me. It is like process explorer for windows. When you develop something window related and you have no idea where is a window -- winlister can tell you whether it is hidden, or maybe have left-top out of the monitor
- kylia 8y agoBlueScreenView is probably one of the most used tools in my kit. From years of doing helpdesk I must have used this tens of times a week.