Tech Support banner
Status
Not open for further replies.
1 - 4 of 4 Posts

·
Registered
Joined
·
3 Posts
Discussion Starter · #1 ·
Problem Description

I had installed TopLinkBuilder on my XP (SP2) machine, the installation was successful; But when I run the program, I ecountered the following problem

"Application failded to initialize properly (0xc0000005)"

Actions Tried

I have tried to resolve the problem in different ways but I failed.

1. Try to change the compatibility mode to Windows 2000 and all the other options. I didn't work.
2. Uninstall and reinstall the program. It didn't work.
3. Installed the program on an NT machine, it worked well; then I copied the whole directory back to my XP machine. still encountered the same problem
4. Ran sfc /scannow, still got the same problem
5. To exclude the program for DEP configuration, still got the same problem

Debugging message


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: ToplinkBuilder.exe
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00400000 00500000 image00400000
ModLoad: 7c900000 7c9b0000 ntdll.dll
ModLoad: 7c800000 7c8f5000 C:\WINDOWS\system32\kernel32.dll
ModLoad: 10000000 1009b000 C:\TOPLink\Builder\ESVM40.dll
ModLoad: 00270000 0027b000 C:\TOPLink\Builder\ESAE40.dll
ModLoad: 7e410000 7e4a0000 C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f57000 C:\WINDOWS\system32\GDI32.dll
(ee8.290): Break instruction exception - code 80000003 (first chance)
eax=00191eb4 ebx=7ffd6000 ecx=00000007 edx=00000080 esi=00191f48 edi=00191eb4
eip=7c901230 esp=0007fb20 ebp=0007fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
7c901230 cc int 3
0:000> g
ModLoad: 5cb70000 5cb96000 C:\WINDOWS\system32\ShimEng.dll
ModLoad: 6f880000 6fa4a000 C:\WINDOWS\AppPatch\AcGenral.DLL
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f02000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 76b40000 76b6d000 C:\WINDOWS\system32\WINMM.dll
ModLoad: 774e0000 7761d000 C:\WINDOWS\system32\ole32.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 77120000 771ab000 C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 77be0000 77bf5000 C:\WINDOWS\system32\MSACM32.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.dll
ModLoad: 7c9c0000 7d1d7000 C:\WINDOWS\system32\SHELL32.dll
ModLoad: 77f60000 77fd6000 C:\WINDOWS\system32\SHLWAPI.dll
ModLoad: 769c0000 76a73000 C:\WINDOWS\system32\USERENV.dll
ModLoad: 5ad70000 5ada8000 C:\WINDOWS\system32\UxTheme.dll
ModLoad: 71590000 71604000 C:\WINDOWS\AppPatch\AcLayers.DLL
ModLoad: 73000000 73026000 C:\WINDOWS\system32\WINSPOOL.DRV
(ee8.290): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000320 ebx=00000000 ecx=004f0010 edx=00000010 esi=00400080 edi=00000320
eip=7c923287 esp=0007fa88 ebp=0007fb18 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
ntdll!LdrpCheckForSecuROMImage+0x76:
7c923287 8b11 mov edx,dword ptr [ecx] ds:0023:004f0010=????????
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

Matched: 7c8866fc kernel32!BasepAppCertDllsList = <no type information>
Matched: 7c8848d0 kernel32!BasepAppCertDllsList = <no type information>
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
ntdll!LdrpCheckForSecuROMImage+76
7c923287 8b11 mov edx,dword ptr [ecx]

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 7c923287 (ntdll!LdrpCheckForSecuROMImage+0x00000076)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 004f0010
Attempt to read from address 004f0010

FAULTING_THREAD: 00000290

DEFAULT_BUCKET_ID: INVALID_POINTER_WRITE

PROCESS_NAME: image00400000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 004f0010

NTGLOBALFLAG: 70

APPLICATION_VERIFIER_FLAGS: 0

LAST_CONTROL_TRANSFER: from 7c9216ea to 7c923287

STACK_TEXT:
0007fb18 7c9216ea 00400080 7ffdf000 7ffd6000 ntdll!LdrpCheckForSecuROMImage+0x76
0007fc94 7c921639 0007fd30 7c900000 0007fce0 ntdll!LdrpInitializeProcess+0x10b0
0007fd1c 7c90eac7 0007fd30 7c900000 00000000 ntdll!_LdrpInitialize+0x183
00000000 00000000 00000000 00000000 00000000 ntdll!KiUserApcDispatcher+0x7


PRIMARY_PROBLEM_CLASS: INVALID_POINTER_WRITE

BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_WRITE

FOLLOWUP_IP:
ntdll!LdrpCheckForSecuROMImage+76
7c923287 8b11 mov edx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ntdll!LdrpCheckForSecuROMImage+76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 411096b4

STACK_COMMAND: ~0s ; dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; kb

FAILURE_BUCKET_ID: ntdll.dll!LdrpCheckForSecuROMImage_c0000005_INVALID_POINTER_WRITE

BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_WRITE_ntdll!LdrpCheckForSecuROMImage+76

Followup: MachineOwner
---------

Please help! Thank you in advance!
 

·
Registered
Joined
·
2 Posts
I found a solution for my problem. Our application was working without problems for lots of years until we came up with a new executable name.

The problem was that I did not copy the matching "ini" file to the distributable runtime image.

Esvm40 needs the matching ini file to load properly but it doesn't tell you. It just complains corrupting your heap.

example
before (crash)
MySystem.icx

after (happy)
MySystem.icx
MySystem.ini

one last thing, Vista doesn't suffer from heap corruption as XP
 
1 - 4 of 4 Posts
Status
Not open for further replies.
Top