• Hi,

    in my dashboard I see this error under "Most common crashes":


    it happened over 4000 times.

    I am confused what this means. Isn't the file (it's content) the dump?

    Visual Studio:

    Microsoft Visual Studio
    Unable to start program 'C:\...\triagedump.dmp'.
    Failed to launch minidump. The minidump file is corrupt.

    Does this mean the dump went wrong and the file is useless? But why does it show up in my crash list then?


    Wednesday, April 2, 2014 10:37 PM

All replies

  • Hello,

    Yes that is very strange. The error indicates that key memory locations that are normally captured and required for analysis of the dump file are missing. The statement "missing_teb" indicates that the Thread Environment Block is not represented in the dump. I'm not sure why this would occur. Try opening the dump in WinDbg and see if you get the same error.

    Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)


    I hope this helps,


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Thursday, April 3, 2014 1:02 AM
  • Hi,

    I opened it in WinDbg. I got this:

    Executable search path is: 
    Windows 8 Version 9600 MP (4 procs) Free ARM (NT) Thumb-2
    Product: WinNt, suite: SingleUserTS
    Machine Name:
    Debug session time: Sat Feb 22 22:31:16.000 2014 (UTC + 2:00)
    System Uptime: not available
    Process Uptime: 0 days 0:00:16.000
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (a60.ad0): Access violation - code c0000005 (first/second chance not available)
    6205b86e 686d     ldr         r5,[r5,#4]                      00000004=????????
    0:008> .ecxr
     r0=00000000  r1=00000005  r2=00e9a570  r3=0211f550  r4=00000000  r5=00000000
     r6=00ec5f18  r7=0211f550  r8=0211f4dc  r9=04dae578 r10=0211f3f0 r11=04dae500
    r12=6205b751  sp=04dae4c0  lr=6205b84f  pc=6205b86e psr=80000030 N---- Thumb
    6205b86e 686d     ldr         r5,[r5,#4]                      00000004=????????
    I have no idea what it says but I suppose it doesn't say that the file is corrupt? So is this a bug in VS?

    Thursday, April 3, 2014 12:10 PM