3 ms·
What I found annoying is the output does not seem helpful at all. Even if you are tech savvy or an IT manager, does the memory dump information help you diagnos
by francisofascii 2y ago
What I found annoying is the output does not seem helpful at all. Even if you are tech savvy or an IT manager, does the memory dump information help you diagnose the problem? Did the Microsoft programmers at least benefit from it?
- kevingadd 2y agoIf you load a minidump or full memory dump from a BSOD into WinDbg, the !analyze command can often tell you exactly what went wrong, i.e. the type of failure and which driver is responsible.
- ofrzeta 2y agoJohn Vert on that "I believe Mark Lucovsky wrote the original code that dumped a bunch of text to the screen. This was a bugcode and a stack dump, resulting in a bunch of useless hex numbers which product support would occasionally dutifully transcribe from the customers and include in the bug report." https://www.quora.com/Who-designed-the-original-Windows-Blue-Screen-of-Death https://www.quora.com/Who-designed-the-original-Windows-Blue...