Every day I get crash logs such as these below.
What do you normally use to read them?
dir %LOCALAPPDATA%\CrashDumps\*
05/29/2026 04:13 PM <DIR> .
05/29/2026 04:13 PM <DIR> ..
05/29/2026 04:13 PM 709,526,427 aloha.exe.244.dmp
05/22/2026 05:12 PM 234,100,509 explorer.exe(1).4940.dmp
05/22/2026 05:12 PM 234,104,853 explorer.exe.4940.dmp
05/29/2026 11:31 PM 280,854,111 SystemSettings.exe.8232.dmp
etc.
Looking it up, there's the official Microsoft tool, WinDbg & NirSoft CrashDumpViewer for example. Just curious what you use to view crash dumps?
Because the DLL had already been ripped out of RAM, that address was no longer a valid code block since it was just dead, unallocated space. The...
CPU read the address, realized it was violating NX protection rules, threw the c0000005 Access Violation and collapsed the program.
Since this is my first crash debug attempt, I am wondering what others on this newsgroup use to debug crash logs found in %LOCALAPPDATA%\CrashDumps
Every day I get crash logs such as these below.
What do you normally use to read them?
dir %LOCALAPPDATA%\CrashDumps\*
05/29/2026 04:13 PM <DIR> .
05/29/2026 04:13 PM <DIR> ..
05/29/2026 04:13 PM 709,526,427 aloha.exe.244.dmp
05/22/2026 05:12 PM 234,100,509 explorer.exe(1).4940.dmp
05/22/2026 05:12 PM 234,104,853 explorer.exe.4940.dmp
05/29/2026 11:31 PM 280,854,111 SystemSettings.exe.8232.dmp
etc.
Looking it up, there's the official Microsoft tool, WinDbg & NirSoft CrashDumpViewer for example. Just curious what you use to view crash dumps?
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 494931:55:18 |
| Calls: | 162 |
| Files: | 568 |
| D/L today: |
14 files (349K bytes) |
| Messages: | 75,027 |