Re: What do you use to read your Windows crash logs?
malxau <[email protected]> Sat, 30 May 2026 04:39:55 -0000 (UTC)
| Newsgroups | alt.comp.os.windows-10,alt.comp.os.windows-11,alt.comp.microsoft.windows |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
In alt.comp.microsoft.windows Maria Sophia <[email protected]> wrote: > 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 I still use WinDbg classic, not WinDbgX. But for a first attempt, that was a great analysis. I think to be "strictly correct" you'd want to check the exception record/context record (.exr/.cxr) to see which address was accessed, but it's 99%+ likely that it's unloaded code. In the spirit of "IRC is for people with mutual interests", this is my intro to WinDbg: http://www.malsmith.net/blog/patching-closed-software/ - M