none
Random errors with the clr.dll 4.0.30319.1 after update to .NET Framework 4.0 RRS feed

  • Question

  • Hello,

    After updating to .NET Framework 4.0 we have got some random crashes in our production environmnent.

    We get a error in clr.dll but having problem to finding the root error. Do you have some tips and tricks?

    The event logg looks like this:

     

    Event Type: Error

    Event Source: .NET Runtime 4.0 Error Reporting

    Event Category: None

    Event ID: 1000

    Date: 10/8/2010

    Time: 12:45:08 AM

    User: N/A

    Computer: [The Computer]

    Description:

    Faulting application [TheApplication.exe], version 1.0.28.78, stamp 4c934361, faulting module clr.dll, version 4.0.30319.1, stamp 4ba1d9ef, debug? 0, fault address 0x00003e54.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: 41 00 70 00 70 00 6c 00   A.p.p.l.

    0008: 69 00 63 00 61 00 74 00   i.c.a.t.

    0010: 69 00 6f 00 6e 00 20 00   i.o.n. .

    0018: 46 00 61 00 69 00 6c 00   F.a.i.l.

    0020: 75 00 72 00 65 00 20 00   u.r.e. .

    0028: 20 00 62 00 72 00 61 00    .b.r.a.

    0030: 74 00 2e 00 63 00 6c 00   t...c.l.

    0038: 69 00 65 00 6e 00 74 00   i.e.n.t.

    0040: 2e 00 65 00 78 00 65 00   ..e.x.e.

    0048: 20 00 31 00 2e 00 30 00    .1...0.

    0050: 2e 00 32 00 38 00 2e 00   ..2.8...

    0058: 37 00 38 00 20 00 34 00   7.8. .4.

    0060: 63 00 39 00 33 00 34 00   c.9.3.4.

    0068: 33 00 36 00 31 00 20 00   3.6.1. .

    0070: 69 00 6e 00 20 00 63 00   i.n. .c.

    0078: 6c 00 72 00 2e 00 64 00   l.r...d.

    0080: 6c 00 6c 00 20 00 34 00   l.l. .4.

    0088: 2e 00 30 00 2e 00 33 00   ..0...3.

    0090: 30 00 33 00 31 00 39 00   0.3.1.9.

    0098: 2e 00 31 00 20 00 34 00   ..1. .4.

    00a0: 62 00 61 00 31 00 64 00   b.a.1.d.

    00a8: 39 00 65 00 66 00 20 00   9.e.f. .

    00b0: 66 00 44 00 65 00 62 00   f.D.e.b.

    00b8: 75 00 67 00 20 00 30 00   u.g. .0.

    00c0: 20 00 61 00 74 00 20 00    .a.t. .

    00c8: 6f 00 66 00 66 00 73 00   o.f.f.s.

    00d0: 65 00 74 00 20 00 30 00   e.t. .0.

    00d8: 30 00 30 00 30 00 33 00   0.0.0.3.

    00e0: 65 00 35 00 34 00 0d 00   e.5.4...

    00e8: 0a 00                     ..      


     

     

    Friday, October 8, 2010 8:01 AM

Answers

  • It seems that your app is raising an exception because of a missing reference. Unfortunately, you have to read the unfrendly error dialog looking for the exception message. You can also create an account to your corporation and use the microsoft error report for free. You will be able to login and collect the crash reports. This way will be easier to find what exactly caused the exception...

     

    Good Luck


    ...
    • Marked as answer by SamAgain Wednesday, October 20, 2010 10:15 AM
    Tuesday, October 12, 2010 3:03 PM
  • Thanks a lot for taking yourself some time to look on the error.

    This error have not happend again since we did reboot the affected production computers.

    I will create a login so I can collect the error reports in a easier way in the future.

     

    Thanks again!

     

    • Marked as answer by SamAgain Wednesday, October 20, 2010 10:15 AM
    Tuesday, October 12, 2010 5:07 PM

All replies

  • It seems that your app is raising an exception because of a missing reference. Unfortunately, you have to read the unfrendly error dialog looking for the exception message. You can also create an account to your corporation and use the microsoft error report for free. You will be able to login and collect the crash reports. This way will be easier to find what exactly caused the exception...

     

    Good Luck


    ...
    • Marked as answer by SamAgain Wednesday, October 20, 2010 10:15 AM
    Tuesday, October 12, 2010 3:03 PM
  • Thanks a lot for taking yourself some time to look on the error.

    This error have not happend again since we did reboot the affected production computers.

    I will create a login so I can collect the error reports in a easier way in the future.

     

    Thanks again!

     

    • Marked as answer by SamAgain Wednesday, October 20, 2010 10:15 AM
    Tuesday, October 12, 2010 5:07 PM