none
Windows 10 with Problem clr.dll RRS feed

  • Question

  • Hi,

    my PC is a new one. Fresh installed. Fully updated.

    My software is ADDISON for tax offices. They told me, it is a framework problem. Not really the problem of ADDISON.

    Within Windows 10, program and features I can deinstall and install some options for net framework. But the app stucks in the same way as before.

    Here is a error output. Can anyone give me some help?

    Event
    xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
     <Provider
    Name="Application Error" />
     <EventID
    Qualifiers="0">1000</EventID>
     <Level>2</Level>
     <Task>100</Task>
     <Keywords>0x80000000000000</Keywords>
     <TimeCreated
    SystemTime="2019-11-11T10:33:00.784060200Z" />
     <EventRecordID>1740</EventRecordID>
     <Channel>Application</Channel>
     <Computer>PC06.steuerbuero.int</Computer>
     <Security
    />
     </System>
    - <EventData>
     <Data>Addison.exe</Data>
     <Data>10.4.3.0</Data>
     <Data>5da57cd1</Data>
     <Data>clr.dll</Data>
     <Data>4.8.4042.0</Data>
     <Data>5d7a9e00</Data>
     <Data>c0000005</Data>
     <Data>004d4a3a</Data>
     <Data>1ca0</Data>
     <Data>01d5986c08b329f2</Data>
     <Data>K:\ZMIS\Addison.exe</Data>
     <Data>C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll</Data>
     <Data>aa22ca5f-8cd9-4e9d-be89-084dce47a19f</Data>
     <Data
    />
     <Data
    />
     </EventData>
     </Event>
    Event
    xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
     <Provider
    Name="Windows Error
    Reporting" />
     <EventID
    Qualifiers="0">1001</EventID>
     <Level>4</Level>
     <Task>0</Task>
     <Keywords>0x80000000000000</Keywords>
     <TimeCreated
    SystemTime="2019-11-11T12:17:21.654446600Z" />
     <EventRecordID>1744</EventRecordID>
     <Channel>Application</Channel>
     <Computer>PC06.steuerbuero.int</Computer>
     <Security
    />
     </System>
    - <EventData>
     <Data>2002392595054985651</Data>
     <Data>1</Data>
     <Data>APPCRASH</Data>
     <Data>Nicht verfügbar</Data>
     <Data>0</Data>
     <Data>Addison.exe</Data>
     <Data>10.4.3.0</Data>
     <Data>5da57cd1</Data>
     <Data>clr.dll</Data>
     <Data>4.8.4042.0</Data>
     <Data>5d7a9e00</Data>
     <Data>c0000005</Data>
     <Data>004d4a3a</Data>
     <Data
    />
     <Data
    />
     <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A3E.tmp.dmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB4FA.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB51B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB519.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB529.tmp.txt</Data>
     <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Addison.exe_16a77e88f546fe8133547fc479aa5f916d10c_efe04020_cf90e9f6-d187-4382-87b6-2954835ae5d3</Data>
     <Data
    />
     <Data>0</Data>
     <Data>3afd60b9-12ba-406b-b2f1-4a0fd0ea7c30</Data>
     <Data>268435456</Data>
     <Data>851732b24aeb27c4fbc9ed74c12001b3</Data>
     <Data>0</Data>
     </EventData>
     </Event>
    • Edited by KrischeuH Wednesday, November 20, 2019 9:01 AM
    Wednesday, November 20, 2019 8:58 AM

All replies

  • Only the author can debug this, we can't really make sense on the event log without debug symbols or source code, sorry.

    A crashing bug in CLR would got fixed rather quickly because a wide range of .Net program would be crashing, not just the one you are using. A more likely cause is that the author has written buggy interop code and doesn't realize it. In rare cases some code injected from third party (e.g. antivirus, video codec, shell namespace extensions) would also crash a program without the author being aware, but again, this kind of issue would not be isolated to a single program.

    You can also ask what OS and .Net versions they have test to work with their program. Even if there were a bug in the latest version of .Net, when they started selling the product it must be usable on some combination of Windows and .Net versions. If you can reproduce your issue on the version combination they initially supported, then the bug is from the Author of the program, not Microsoft. 



    Visual C++ MVP

    • Proposed as answer by EckiS Wednesday, November 20, 2019 2:56 PM
    Wednesday, November 20, 2019 2:51 PM
  • SOLVED

    I tested thousand things.

    Solution was to install a fresh windows 10.

    One thing ...

    First installation was Win10 V1903.

    Second one, Windows 10 V1606, than installation of the framework V4.7.x

    At least, update to Windows V1903. Automativally Update to Framework 4.8.2

    Everything is working

    Tuesday, December 3, 2019 10:39 AM
  • Hi KrischeuH,

    I’m glad to hear that you resolve this issue.

    Please click "Mark as answer" to the appropriate answer, so that it will help other members to find the solution quickly if they face a similar issue.

    Thank you for sharing your solutions and experience here.

    Best Regards,

    Xingyu Zhao


    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, December 4, 2019 6:10 AM
    Moderator