Conflicts between BoundsChecker/Error Detection and Microquill

0 Likes

Problem:

Application fails to start up under BoundsChecker/Error Detection. Receive the error: The application failed to initialize properly (0xc0000005)"

Resolution:

While there are several potential causes of this and similar errors, this is often the result of conflicts between our hooking engine and Microquill's Heap Agent tool. If you are using any Microquill tools, please disable them before sing BoundsChecker/Error Detection. An easy way to check is to search the "modules" tab of the BoundsChecker session file generated from the failed run for "HALoader.dll". This is the hooking component of HeapAgent. If it is present, you can disable HeapAgent's injection by removing the value 'haloader.dll' from the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

Removing the entry and rebooting should prevent HALoader from injecting.

<!--- END INSERT ANSWER --->

Old KB# 11846
Comment List
Anonymous
Related Discussions
Recommended