NTDLL.DLL

[g8orade]

Thanks in advance for any help.
I have a windows xp pro sp1 system that I am getting an error like <program name> is causing an exception error in ntdll.dll. Sometimes I get a reboot when I try to open the program. I have found that I can login as another user delete the profile of the user that I get the ntdll.dll error with and they can use the program a couple of times before the issue resurfaces. Sometimes I also get a " APL +win runtime" error. I swapped memory and am still getting the same results. This is an upgrade xp from windows 98 but has been in service for over 9 mos and this has been first issues with this system. I was wondering if anyone has had any similar problems. I am wondering if its not some kind of ntdll.dll bufferoverflow issue, but so far this is only machine on network that has this issue. I have checked with hijackthis, taskmonitor, and processviewer to see if there were any programs out the norm running and everything seems to be normal. THANKS IN ADVANCE FOR ANY HELP.
G8TOR

 

[linney]

It might be worth a second opinion before you dismiss any malware as a cause of this.

Removing adware & spyware
faq608-4650

"APL +win runtime" sounds like an error from some older program but I wouldn't really know.



If you search with "NtDll" in the Help and Support program (while online) it will pull up several MSKB articles where games or media players can cause problems.

Some general things to try.

See if System Restore will get you back to a restore point before your problem with Explorer.

Try Safe Mode (Do you have this problem in Safe Mode?).

Try running ChkDsk to check your drive for errors. Right click your Drive icon/ Properties/ Tools/ Error Checking.

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

HOW TO: Verify Unsigned Device Drivers in Windows XP

http://support.microsoft.com/support/kb/articles/q308/5/14.asp

If they don't work you could try repairing windows by running it over itself. You will lose all your windows updates but your files will be untouched.

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)

 

[ArthurKnight]

Hi

I have the same problem with an App I created in VB6.

It crashes randomly, sometimes you use the program fine, then close and open again and crashes.

I installed a fresh copy of windows XPpro and 2Kpro in a VMWare virtual machine, I installed my app and crashes.

Windows gives me this file when reporting the error:

Then I tryed in another PC with all service packs and fixes installed, and the same problem again.

If you try restoring Windows it wont work, if you format the pc and reinstall neither work.

Microsoft doesn´t have explanation.

I´ll keep looking for fixing this issue

Regards.

<DATABASE>
<EXE NAME="DrVirtual.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="AutoUpdater.exe" SIZE="28672" CHECKSUM="0xC3C926B3" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00" COMPANY_NAME="IIDEA SOLUTIONS" PRODUCT_NAME="AutoUpdater" FILE_VERSION="1.00" ORIGINAL_FILENAME="AutoUpdater.exe" INTERNAL_NAME="AutoUpdater" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x13EB5" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="08/22/2005 16:02:51" UPTO_LINK_DATE="08/22/2005 16:02:51" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="DiagnosticadorAlestra.exe" SIZE="413696" CHECKSUM="0xDFC5E30D" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00" COMPANY_NAME="DeAcero" PRODUCT_NAME="DiagnosticadorAlestra" FILE_VERSION="1.00" ORIGINAL_FILENAME="DiagnosticadorAlestra.exe" INTERNAL_NAME="DiagnosticadorAlestra" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6DF4E" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="08/29/2005 14:14:50" UPTO_LINK_DATE="08/29/2005 14:14:50" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="DrVirtual.exe" SIZE="413696" CHECKSUM="0xDFC48A0D" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00" COMPANY_NAME="DeAcero" PRODUCT_NAME="DiagnosticadorAlestra" FILE_VERSION="1.00" ORIGINAL_FILENAME="DrVirtual.exe" INTERNAL_NAME="DrVirtual" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x71CDC" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="08/29/2005 14:32:04" UPTO_LINK_DATE="08/29/2005 14:32:04" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="jmail.dll" SIZE="318464" CHECKSUM="0x7B77DC4C" BIN_FILE_VERSION="4.4.0.0" BIN_PRODUCT_VERSION="4.4.0.0" PRODUCT_VERSION="JMail 4.4.0 Free Edition" FILE_DESCRIPTION="JMail 4.4.0" COMPANY_NAME="Dimac Development-Duplo AB (

http://www.dimac.net)"

PRODUCT_NAME="w3 JMail" FILE_VERSION="4.4.0.0" ORIGINAL_FILENAME="jmail.dll" LEGAL_COPYRIGHT="Copyright © 2003 Dimac Development-Duplo AB (

http://www.dimac.net/)"

VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.4.0.0" UPTO_BIN_PRODUCT_VERSION="4.4.0.0" LINK_DATE="06/19/1992 22:22:17" UPTO_LINK_DATE="06/19/1992 22:22:17" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="OSICMP.dll" SIZE="49152" CHECKSUM="0x2B01FCAE" BIN_FILE_VERSION="1.0.0.8" BIN_PRODUCT_VERSION="1.0.0.8" PRODUCT_VERSION="1.00.0008" FILE_DESCRIPTION="ICMP Component for Visual Basic" COMPANY_NAME="OstroSoft" PRODUCT_NAME="OstroSoft ICMP Component" FILE_VERSION="1.00.0008" ORIGINAL_FILENAME="OSICMP.dll" INTERNAL_NAME="OSICMP" LEGAL_COPYRIGHT="Copyright (c) 2004 OstroSoft " VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x11643" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.0.8" UPTO_BIN_PRODUCT_VERSION="1.0.0.8" LINK_DATE="06/25/2004 23:16:49" UPTO_LINK_DATE="06/25/2004 23:16:49" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="ntdll.dll" SIZE="708096" CHECKSUM="0x9D20568" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAF2F7" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

 

[linney]

Have you tried a different Compatibility Mode setting for your program to see if you can get it to work?

Will it work in Safe Mode at all?

Try the re-installing scripten.exe

http://www.microsoft.com/downloads/...43-7e4b-4622-86eb-95a22b832caa&DisplayLang=en

http://www.google.com/search?source...GLG,GGLG:2005-28,GGLG:en&q=ntdll.dll+error+xp

http://groups.google.com/groups?sou...GLG,GGLG:2005-28,GGLG:en&q=ntdll.dll+error+xp

 

[ArthurKnight]

Hi Linney,

Thanks, I checked the links, but no helped to solve my problem.

I solved the problem, the source of the problem was the component MSCOMM.DLL, we used it to check for dial-tone. The component is loaded in memory when oppen the App, then it causes to crash randomly.

The procedure was to eliminate the references to external components one by one until the App shows no fail.

Instead using MSCOMM.DLL, we used WMI (Win32_NetworkAdapterConfiguration Where IPEnabled=TRUE) and we disabled checking the line status, we did it with: InternetAutodial Lib "wininet.dll", it shows the dialog of dial-up connections, if it was able to connect then there was no phone line error. Also the functions throws an error description (dialtone error, user and pass incorrect, etc).

I looked for MSCOMM.DLL known issues but this one doesn´t appear.

Hope it helps to someone.