Moderators: Hacker, petermad, Stefan2, white
You should get an dialog from TC where you can copy the report, no?
You should get an dialog automatically from TC if an crash occurs, from there you can copy the report.
post by *ghisler(Author)
You could also create a crash dump with procdump, this would allow me to see in the stack trace which module is crashing:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. Send me the dump from c:\dumps.
It depends on how big it is (zipped).
If it's smaller than 25MB, please send it to my GMail address: cghisler at gmail dot com.
Otherwise please upload it somewhere (e.g. Google Drive, OneDrive, Dropbox),
share it (everyone who has the link), and send me the link to the same e-mail address.
To analyze the dump yourself , please get windbg from here:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg
Usage:
1. Create new directory c:\Symbols
2. Run Windbg
3. File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line (including the ! at the start):
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste the result to the email body.
Moderator message
