| Issue | Solution | |-------|----------| | "Symbol file not loaded" | Use .symfix then .reload /f | | WinDbg crashes on start | Run as Administrator and disable Hyper-V’s debugger passthrough | | Dumps are missing | Check pagefile size – Must be ≥ RAM for complete dumps | | Network debugging fails | Disable Windows Firewall for the debug port and ensure no NAT | | Server Core – no GUI | Use remote debugging from a client machine with WinDbg -remote tcp:server=Server2019,port=5000 |

This is the "magic command." It is the first command you should run on any crash dump.

!poolused 2 # Show pool usage by tag !poolfind <tag> # Find allocations for a specific tag

Look for a tag with massive allocations. Then find the driver responsible:

Since Server 2019 may not have the Microsoft Store, you can install WinDbg using PowerShell:

: Dump analysis shows UNKNOWN for driver name Solution : Run !devnode 0 1 to list all loaded drivers and find matching address range.