Debug Windows Error Reporting and CLR intergration RRS feed

  • Question

  • Windows Error Reporting (WER) monitors and collects information on crashes and hangs on Windows platforms newer that Windows XP. 

    When creating reports, WER generates some parameters to bucket-ize the failures. Since the OS doesn’t know anything about managed applications, CLR integrates WER and adds these parameters to create correct buckets:

    Problem signature:

      Problem Event Name:                        CLR20r3

      Problem Signature 01:                       aatrend.exe

      Problem Signature 02:                       716.175.0.0

      Problem Signature 03:                       526a9725

      Problem Signature 04:                       System.Windows.Forms

      Problem Signature 05:                       4.0.30319.17929

      Problem Signature 06:                       4ffa5c0e

      Problem Signature 07:                       93a

      Problem Signature 08:                       142

      Problem Signature 09:                       System.ObjectDisposedException

      OS Version:                                          6.1.7601.

      Locale ID:                                             4105

      Additional Information 1:                  0a9e

      Additional Information 2:                  0a9e372d3b4ad19135b953a78882e789

      Additional Information 3:                  0a9e

      Additional Information 4:                  0a9e372d3b4ad19135b953a78882e789

    Is there anyway to see Why it crashed or is there a fix?

    • Moved by Stanly Fan Wednesday, May 2, 2018 7:47 AM
    Tuesday, May 1, 2018 1:00 PM

All replies

  • Hi Wickid123,

    This forum is discussing and asking questions about the Windows Form and ClickOnce, it will be more appropriate to ask your question at Microsoft Community

    Thank you for your understanding.



    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 2, 2018 7:47 AM
  • Which Windows version and build?

    Are you having BSOD?

    Have you seen a bugchecks?

    Wednesday, May 2, 2018 7:54 AM