Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
3
Erster Beitrag:
vor 1 Woche, 3 Tagen
Letzter Beitrag:
vor 4 Tagen, 22 Stunden
Beteiligte Autoren:
steve erts, Fabrice Harari

No specific crash of wd220vm.dll (solved)

Startbeitrag von steve erts am 14.11.2017 05:39

Hi,

I have a program that is using a Dot Net Assembly. Everything is working well with the exception that I'm getting periodic application crashes of referencing wd220vm.dll. It doesn't seem there is anything wrong with the code and 90% of time it works fine but the rest of the time I get a crash with following error. Any ideas?

Problem Event Name: APPCRASH
Application Name: Tourcube.exe
Application Version: 2.7.8.65517
Application Timestamp: 5965eda9
Fault Module Name: wd220vm.dll
Fault Module Version: 22.0.316.0
Fault Module Timestamp: 595ce20b
Exception Code: c0000005
Exception Offset: 0003cbc5
OS Version: 6.3.9600.2.0.0.16.7
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: 5f25
Additional Information 4: 5f2531ae070278f893fa99352dadd49e

Thanks

Steve

Antworten:

Re: No specific crash of wd220vm.dll

Hi Steve,

so, yo have a random error (or what looks like one)... Here is a list of possible causes for this kind of problem (I'm sure there are more, but that should give you a few leads to explore):

http://fabriceharari.com/UK/Page_ArticlesList.awp?ActiveMenuItem=8

Best regards

von Fabrice Harari - am 14.11.2017 11:46

Re: No specific crash of wd220vm.dll

Hi Fabrice,

Thank you for the tips. It turns out that the issue had to do with multi-threading and having Dot New Delegate callback used from multiple places using the same global variable as global procedure. Once I moved the variables and procedures and made the local to the windows that used them the problem evaporated. It not the most efficient use of code, but the work is finished now and I was able to move to the next things which serves me well at this point.

Interestingly, PC SOFT support also provided me with a method to trap what these non specific errors might mean. I haven;t tried, but does seem interesting and worth noting.

Note: I've replaced the > and < with ] and [ below
--------------------------------------------------------------------------------------------------------
In order to investigate such a random problem, the best option is to create a dump on site. The easiest way to get a dump on the users machine is to add the following to your project init code :

[BLOC dbgActivateSystemDump enable (or not) the generation of system dump to transmit some problems to the Technical Support.]

dbgInfo(dbgActivateSystemDump)
dbgInfo(dbgDirectorySystemDump,fExeDir())
[FIN]

The MICROSOFT Windbg utility can be used too:

1) Install MICROSOFT Windbg utility from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx or from

http://windbg.dumpanalysis.org/

2) RUN c:\Program Files\Debugging Tools for Windows (x86)\windbg.exe

3) Key F6

4) Select the process

5) Wait for the hook

6) Create the dump:

.dump /ma

( the dot is mandatory )

von steve erts - am 19.11.2017 18:38
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.