• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1270 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS V3.3 crash on Windows 2000

Patrick Ruf
Genius 5015 points


We have two PC's with Windows2000 and Code Composer Studio V3.3 installed.
The Versions are as follows:

- Windows 2000 SP4, 5.00.2195
- CCS V3.3 Platinum, V3.3.82.13

Until 24.09.2009 CCS V3.3 worked fine. But when we had to use it last Friday (05.02.2010) CCS V3.3 crashed shortly after the splash screen appeared with the following message:

The Visual Studio shows the following message:

 

There was a similar post addressing probably the same problem. There they ask to rename "cwsense.dll". I have done this but without success.

We did not make any changes to CCS V3.3. I have also tried to uninstall and install again. First without SR12 (--> same problem) and then with SR12. In vaine so far.

Attached is a dump file from CCS V3.3.

Any ideas what happend?

ccapp20100203131112.zip
  • 0
    TI__Guru**** 473961 points

    Perhaps you can try to rename cwdll32.dll to see if that helps. After you did the reinstall, did you get the crash immediately after startup? Or after your reopened your projects?

  • 0 in reply to Ki
    Genius 5015 points

    In all cases I could not even open a project. The crash always happend shortly after the splash screen. This was also the case after reinstall CCS V3.3.

     I will try to rename cwdll32.dll.

  • 0 in reply to Ki
    Genius 5015 points

    Result of renaming cwdll32.dll: CCS V3.3 crash just after starting. Message: cwdll32.dll was not found in the path specified. 

  • 0 in reply to Patrick Ruf
    TI__Guru**** 473961 points

    Ok, I think that dll connot be renamed as it is an essential one.... best to rename it back.

  • 0 in reply to Ki
    TI__Genius 16510 points

    I had a look at the crash dump file and don't see anything particularly odd. The exception is occuring in cwdll32.dll, but this doesn't really help much.

    I did notice an antivirus DLL is loaded which not too many users would have:

    6fa00000 6fa35000   sophos_detoured T (no symbols)          
        Loaded symbol image file: sophos_detoured.dll
        Image path: C:\Programme\Sophos\Sophos Anti-Virus\sophos_detoured.dll
        Image name: sophos_detoured.dll
        Timestamp:        Wed Jul 29 04:18:36 2009 (4A7005DC)
        CheckSum:         0003D336
        ImageSize:        00035000
        File version:     1.0.0.4030
        Product version:  7.6.11.0
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    On the chance there has been an update to the antivirus program that was only recently picked up and that is somehow interacting with CCS, could you temporarly disable the antivirus software to see if this helps?

  • 0 in reply to AndyW
    Genius 5015 points

    I have first tried to just disable the antivirus scanning --> No success.

    Then I have deinstalled antivirus (Sophos) completely --> Success !! :-)

    So the first step is done. Thanks for that.

    What I have seen right now is that the "sophos_detoured.dll" is a buffer overflow protection system. I will further investigate this...

  • 0 in reply to Patrick Ruf
    Genius 5015 points

    With Sophos Anti Virus there is the following solution to that problem:

    Remove Sophos_detoured.dll from AppInit_DLLs in:

    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows

    This will infact stop the buffer overflow protection of Sophos: (from the Sophos Knowledgebase)


    The registry string value is space-separated and contains a list of libraries to load when Windows applications are launched. If Sophos_detoured.dll is not in the list, the buffer overflow protection system will not load. When an application is launched, Sophos_detoured.dll is loaded inside of the new process. If this application should not be protected, Sophos_detoured will unload.