|
FOROS PROFESIONALES
WINDEV, WEBDEV y WINDEV Mobile |
| | | | | |
| Problem with WD160VM.dll while executing program |
| Iniciado por ioakeimidis, 11,dic. 2015 15:22 - 1 respuesta |
| |
| | | |
|
| |
| Publicado el 11,diciembre 2015 - 15:22 |
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 :
General:
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time stamp: 0x4d886029
Faulting module name: WD160VM.DLL, version: 16.0.150.6, time stamp: 0x4deced51
Exception code: 0xc0000005
Fault offset: 0x00007846
Faulting process id: 0x92c
Faulting application start time: 0x01d12e7adc45c4ba
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE
Faulting module path: C:\INTERAXION\APS\EXE\WD160VM.DLL
Report Id: ecaa0656-9a77-11e5-85d3-005056b17feb
Details:
INTERAXION.EXE
20.0.0.65517
4d886029
WD160VM.DLL
16.0.150.6
4deced51
c0000005
00007846
92c
01d12e7adc45c4ba
C:\INTERAXION\APS\EXE\INTERAXION.EXE
C:\INTERAXION\APS\EXE\WD160VM.DLL
ecaa0656-9a77-11e5-85d3-005056b17feb
We have also recorded the following errors (which occur more often):
General:
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time stamp: 0x4d886029
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb1072
Exception code: 0xc0000005
Fault offset: 0x0002dfe4
Faulting process id: 0xb48
Faulting application start time: 0x01d130c0562dc278
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 3bca7889-9cb7-11e5-a2db-005056b17feb
Details:
INTERAXION.EXE
20.0.0.65517
4d886029
ntdll.dll
6.1.7601.18229
51fb1072
c0000005
0002dfe4
b48
01d130c0562dc278
C:\INTERAXION\APS\EXE\INTERAXION.EXE
C:\Windows\SysWOW64\ntdll.dll
3bca7889-9cb7-11e5-a2db-005056b17feb
I contacted Microsoft and this is what they answered:
Please find the result of the analysis below:
2 process crash dump was collected by our diagnostics.
dump 1:
we have an exception when freeing from the heap , calling module WD160VM:
10 0471ed80 765b98cd ntdll!RtlFreeHeap+0x142
11 0471edcc 25f5632e msvcrt!free+0xcd
12 0471edd4 00000000 WD160VM+0xf632e
Usually we crash in ntdll freeheap because the address specified by the module is invalid or the heap block is corrupt.
This time, it looks the application tries to free an address, which is NOT EVEN A HEAP address, but an address from the module:
0:023> kP
00 0471ed60 77052aa5 ntdll!RtlpFreeHeap(
void * pBlock = 0x2604ffc8)+0xcd
03 0471edd4 00000000 WD160VM+0xf632e
0:023> !address 0x2604ffc8
Usage: Image
Base Address: 25e60000
End Address: 2607e000
Region Size: 0021e000 ( 2.117 MB)
State: <info not present at the target>
Protect: <info not present at the target>
Type: <info not present at the target>
Allocation Base: <info not present at the target>
Allocation Protect: <info not present at the target>
Image Path: C:\INTERAXION\APS\EXE\WD160VM.DLL
Module Name: WD160VM
Loaded Image Name: WD160VM.DLL
Mapped Image Name:
More info: lmv m WD160VM
More info: !lmi WD160VM
More info: ln 0x2604ffc8
More info: !dh 0x25e60000
Action: contact the vendor of WD160VM.DLL.
dump2:
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.
0f 030cef50 25fd651b 0x0
10 030cf144 25fddd16 WD160VM+0x17651b
11 030cf148 03c62488 WD160VM+0x17dd16
Does anybody have a clue what would cause WD160VM.DLL to crash our INTERAXION.EXE ?? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 11,diciembre 2015 - 16:05 |
Hi
from what I understand, your "interaxion" was created with windev 16 and
has a bug. The WD160VM dll is the virtual machine in which the pseudo
code is run.
As to what can cause such a random crash, there are lots of
possibilities. I'm listing a few here:
http://fabriceharari.com/UK/Page_ArticlesList.awp…
Without full access to the program sources, it will be impossible to be
more precise.
Best regards
--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting
Ready for you: WXShowroom.com, WXReplication (open source) and now WXEDM
(open source)
More information on http://www.fabriceharari.com
On 12/11/2015 9:22 AM, Ioakim Ioakimidis wrote:
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 :
General:
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time
stamp: 0x4d886029
Faulting module name: WD160VM.DLL, version: 16.0.150.6, time stamp:
0x4deced51
Exception code: 0xc0000005
Fault offset: 0x00007846
Faulting process id: 0x92c
Faulting application start time: 0x01d12e7adc45c4ba
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE
Faulting module path: C:\INTERAXION\APS\EXE\WD160VM.DLL
Report Id: ecaa0656-9a77-11e5-85d3-005056b17feb
Details:
INTERAXION.EXE 20.0.0.65517 4d886029 WD160VM.DLL 16.0.150.6
4deced51 c0000005 00007846 92c 01d12e7adc45c4ba
C:\INTERAXION\APS\EXE\INTERAXION.EXE C:\INTERAXION\APS\EXE\WD160VM.DLL
ecaa0656-9a77-11e5-85d3-005056b17feb
We have also recorded the following errors (which occur more often):
General:
Faulting application name: INTERAXION.EXE, version: 20.0.0.65517, time
stamp: 0x4d886029
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp:
0x51fb1072
Exception code: 0xc0000005
Fault offset: 0x0002dfe4
Faulting process id: 0xb48
Faulting application start time: 0x01d130c0562dc278
Faulting application path: C:\INTERAXION\APS\EXE\INTERAXION.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 3bca7889-9cb7-11e5-a2db-005056b17feb
Details:
INTERAXION.EXE 20.0.0.65517 4d886029 ntdll.dll 6.1.7601.18229
51fb1072 c0000005 0002dfe4 b48 01d130c0562dc278
C:\INTERAXION\APS\EXE\INTERAXION.EXE C:\Windows\SysWOW64\ntdll.dll
3bca7889-9cb7-11e5-a2db-005056b17feb
I contacted Microsoft and this is what they answered:
Please find the result of the analysis below:
2 process crash dump was collected by our diagnostics.
dump 1: we have an exception when freeing from the heap , calling module
WD160VM:
10 0471ed80 765b98cd ntdll!RtlFreeHeap+0x142
11 0471edcc 25f5632e msvcrt!free+0xcd
12 0471edd4 00000000 WD160VM+0xf632e
Usually we crash in ntdll freeheap because the address specified by the
module is invalid or the heap block is corrupt.
This time, it looks the application tries to free an address, which is
NOT EVEN A HEAP address, but an address from the module:
0:023> kP
00 0471ed60 77052aa5 ntdll!RtlpFreeHeap(
void * pBlock =
0x2604ffc8)+0xcd 03 0471edd4 00000000 WD160VM+0xf632e
0:023> !address 0x2604ffc8
Usage: Image
Base Address: 25e60000
End Address: 2607e000
Region Size: 0021e000 ( 2.117 MB)
State: <info not present at the target>
Protect: <info not present at the target>
Type: <info not present at the target>
Allocation Base: <info not present at the target>
Allocation Protect: <info not present at the target>
Image Path: C:\INTERAXION\APS\EXE\WD160VM.DLL
Module Name: WD160VM
Loaded Image Name: WD160VM.DLL
Mapped Image Name: More info: lmv m WD160VM
More info: !lmi WD160VM
More info: ln 0x2604ffc8
More info: !dh 0x25e60000
Action: contact the vendor of WD160VM.DLL.
dump2: 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.
0f 030cef50 25fd651b 0x0
10 030cf144 25fddd16 WD160VM+0x17651b
11 030cf148 03c62488 WD160VM+0x17dd16
Does anybody have a clue what would cause WD160VM.DLL to crash our
INTERAXION.EXE ?? |
| |
| |
| | | |
|
| | | | |
| | |
| | |
| |
|
|
|