<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><category>pcsoft.us.windev</category><copyright>Copyright 2026, PC SOFT</copyright><lastBuildDate>11 Dec 2015 16:05:10 Z</lastBuildDate><pubDate>11 Dec 2015 15:22:58 Z</pubDate><description>I have an application named INTERAXION which causes several times the operating system to crash our running executable. Our application resides on a windows server 2008 R2 machine. We have recorded the following errors in the windows event viewer :&#13;
&#13;
General:&#13;
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time stamp: 0x4d886029&#13;
Faulting module name: WD160VM.DLL, version: 16.0.150.6, time stamp: 0x4deced51&#13;
Exception code: 0xc0000005&#13;
Fault offset: 0x00007846&#13;
Faulting process id: 0x92c&#13;
Faulting application start time: 0x01d12e7adc45c4ba&#13;
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE&#13;
Faulting module path: C:\INTERAXION\APS\EXE\WD160VM.DLL&#13;
Report Id: ecaa0656-9a77-11e5-85d3-005056b17feb&#13;
&#13;
Details:&#13;
INTERAXION.EXE &#13;
   20.0.0.65517 &#13;
   4d886029 &#13;
   WD160VM.DLL &#13;
   16.0.150.6 &#13;
   4deced51 &#13;
   c0000005 &#13;
   00007846 &#13;
   92c &#13;
   01d12e7adc45c4ba &#13;
   C:\INTERAXION\APS\EXE\INTERAXION.EXE &#13;
   C:\INTERAXION\APS\EXE\WD160VM.DLL &#13;
   ecaa0656-9a77-11e5-85d3-005056b17feb &#13;
&#13;
We have also recorded the following errors (which occur more often):&#13;
&#13;
General:&#13;
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time stamp: 0x4d886029&#13;
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb1072&#13;
Exception code: 0xc0000005&#13;
Fault offset: 0x0002dfe4&#13;
Faulting process id: 0xb48&#13;
Faulting application start time: 0x01d130c0562dc278&#13;
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE&#13;
Faulting module path: C:\Windows\SysWOW64\ntdll.dll&#13;
Report Id: 3bca7889-9cb7-11e5-a2db-005056b17feb&#13;
&#13;
Details:&#13;
INTERAXION.EXE &#13;
   20.0.0.65517 &#13;
   4d886029 &#13;
   ntdll.dll &#13;
   6.1.7601.18229 &#13;
   51fb1072 &#13;
   c0000005 &#13;
   0002dfe4 &#13;
   b48 &#13;
   01d130c0562dc278 &#13;
   C:\INTERAXION\APS\EXE\INTERAXION.EXE &#13;
   C:\Windows\SysWOW64\ntdll.dll &#13;
   3bca7889-9cb7-11e5-a2db-005056b17feb &#13;
&#13;
I contacted Microsoft and this is what they answered:&#13;
&#13;
Please find the result of the analysis below:&#13;
2 process crash dump was collected by our diagnostics.&#13;
&#13;
dump 1: &#13;
we have an exception when freeing from the heap , calling module WD160VM:&#13;
10 0471ed80 765b98cd ntdll!RtlFreeHeap+0x142&#13;
11 0471edcc 25f5632e msvcrt!free+0xcd&#13;
12 0471edd4 00000000 WD160VM+0xf632e&#13;
&#13;
Usually we crash in ntdll freeheap because the address specified by the module is invalid or the heap block is corrupt.&#13;
This time, it looks the application tries to free an address, which is NOT EVEN A HEAP address, but an address from the module:&#13;
0:023&gt; kP&#13;
00 0471ed60 77052aa5 ntdll!RtlpFreeHeap(&#13;
                                            void * pBlock = 0x2604ffc8)+0xcd &#13;
03 0471edd4 00000000 WD160VM+0xf632e&#13;
&#13;
0:023&gt; !address 0x2604ffc8&#13;
&#13;
Usage:                  Image&#13;
Base Address:           25e60000&#13;
End Address:            2607e000&#13;
Region Size:            0021e000 (   2.117 MB)&#13;
State:                  &lt;info not present at the target&gt;&#13;
Protect:                &lt;info not present at the target&gt;&#13;
Type:                   &lt;info not present at the target&gt;&#13;
Allocation Base:        &lt;info not present at the target&gt;&#13;
Allocation Protect:     &lt;info not present at the target&gt;&#13;
Image Path:             C:\INTERAXION\APS\EXE\WD160VM.DLL&#13;
Module Name:            WD160VM&#13;
Loaded Image Name:      WD160VM.DLL&#13;
Mapped Image Name:      &#13;
More info:              lmv m WD160VM&#13;
More info:              !lmi WD160VM&#13;
More info:              ln 0x2604ffc8&#13;
More info:              !dh 0x25e60000&#13;
&#13;
Action: contact the vendor of WD160VM.DLL.&#13;
&#13;
dump2: &#13;
It shows a different problem, it seems we try to execute from the 0 address, which is invalid. Again, this looks to be caused by WD160VM, app vendor should look at it.&#13;
&#13;
0f 030cef50 25fd651b 0x0&#13;
10 030cf144 25fddd16 WD160VM+0x17651b&#13;
11 030cf148 03c62488 WD160VM+0x17dd16&#13;
&#13;
&#13;
Does anybody have a clue what would cause WD160VM.DLL to crash our INTERAXION.EXE ??</description><ttl>30</ttl><generator>WEBDEV</generator><language>en_US</language><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55448-problem-with-wd160vm-dll-while-executing-program/read.awp</link><title>Problem with WD160VM.dll while executing program</title><managingEditor>moderateur@pcsoft.fr (El moderador)</managingEditor><webMaster>webmaster@pcsoft.fr (El webmaster)</webMaster><item><author>fromweb</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55448-problem-with-wd160vm-dll-while-executing-program-55451/read.awp</comments><pubDate>11 Dec 2015 16:05:10 Z</pubDate><description>Hi&#13;
&#13;
from what I understand, your "interaxion" was created with windev 16 and &#13;
has a bug. The WD160VM dll is the virtual machi…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55448-problem-with-wd160vm-dll-while-executing-program-55451/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55448-problem-with-wd160vm-dll-while-executing-program-55451/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55448-problem-with-wd160vm-dll-while-executing-program/read.awp">Problem with WD160VM.dll while executing program</source><title>Re: Problem with WD160VM.dll while executing program</title></item></channel></rss>
