While the Windows' own crash window is up, I try to use process explorer to get a crash dump but it does not give me a stack trace or enough debugging information to help me find out what caused the crash. In fact, opening it in Visual Studio gives this fancy useless error message:
Is there any way to get Windows minidump info after a crash?
Is there any way to get Windows minidump info after a crash?
Sometimes, particularly when using 64-bit builds of Q/G/ZDoom, if it crashes it does not invoke the crash logger, which means you are pretty much on your own trying to get a valid crash dump.
While the Windows' own crash window is up, I try to use process explorer to get a crash dump but it does not give me a stack trace or enough debugging information to help me find out what caused the crash. In fact, opening it in Visual Studio gives this fancy useless error message: I know WerFault.exe does store the crash dumps somewhere, but I have had no luck in finding them. I am using Windows 10, if it's of any interest to anyone. Does anyone know where this information might be?
While the Windows' own crash window is up, I try to use process explorer to get a crash dump but it does not give me a stack trace or enough debugging information to help me find out what caused the crash. In fact, opening it in Visual Studio gives this fancy useless error message: I know WerFault.exe does store the crash dumps somewhere, but I have had no luck in finding them. I am using Windows 10, if it's of any interest to anyone. Does anyone know where this information might be?
Re: Is there any way to get Windows minidump info after a cr
Well um...there are two applications which you should try: HijackThis and File Monitor. My right-hand man Zsole recommended these for me in the good ol'days, and 95% of the cases, they work. Not sure if they operate correctly under Windows 10, but they're still better than nothing...