Ntdll.dll error

michaelgears · 29 Apr 2011

-Application is integrated with an Intra Oral X-Ray sensor.
-The application runs within a process of another application which is listed in the error below "trackerb.exe".
-The error occurs when x-ray interface is closed.
-When the application is NOT running within a process of "trackerb.exe" application, the error does NOT occur.

Log Name: Application
Source: Application Error
Date: 26/04/2011 9:43:43 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: OP2
Description:
Faulting application name: trackerb.exe, version: 10.50.0.902, time stamp: 0x4d51b1dd
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab44
Exception code: 0xc0000374
Fault offset: 0x000c35e3
Faulting process id: 0xf48
Faulting application start time: 0x01cc0417763448de
Faulting application path: C:\PROGRA~1\TRACKE~1\trackerb.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 331c0d2a-700b-11e0-aa4b-bc305ba6182b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-04-26T13:43:43.000000000Z" />
<EventRecordID>7003</EventRecordID>
<Channel>Application</Channel>
<Computer>OP2</Computer>
<Security />
</System>
<EventData>
<Data>trackerb.exe</Data>
<Data>10.50.0.902</Data>
<Data>4d51b1dd</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7600.16695</Data>
<Data>4cc7ab44</Data>
<Data>c0000374</Data>
<Data>000c35e3</Data>
<Data>f48</Data>
<Data>01cc0417763448de</Data>
<Data>C:\PROGRA~1\TRACKE~1\trackerb.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>331c0d2a-700b-11e0-aa4b-bc305ba6182b</Data>
</EventData>
</Event>

SmurofNeves · 29 Apr 2011

Can't you repair the installation in a whole.? Run the setup again and view the options.

The causes of ntdll.dll error messages can vary greatly. However, most ntdll.dll errors result from a corrupt or damaged version of the ntdll.dll file itself, corrupt hardware drivers, or issues between Windows and other programs.
NOTE: THIRD PARTY SOFTWARE DISCLAIMER
Using Third Party Software, including hardware drivers can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the use of Third Party Software can be solved. Using Third Party Software is at your own risk.

Method 1: Perform a clean boot
How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Regard

**cluberti** · 29 Apr 2011

Also note that ntdll, being an API dll, can cause crashes in the applications using those APIs if you don't ref/deref properly within the app itself. It's likely that if the app works fine without being inside trackerb, but fails in trackerb when it's a child of that app, the problem is in trackerb's use of one of the nt! APIs, causing the error. The error code 0xc0000374 also translates to an actual win32 error for it's exit code, 8007006D, which is "ERROR_BROKEN_PIPE". It's likely that trackerb is using a named pipe to communicate with the child process, and the child process is exiting before trackerb can close the pipe down during process termination. Either the trackerb code needs to be updated to handle this error condition gracefully, or the code of the child app needs to be updated to run properly when being controlled by a named pipe via a parent PID. I'm going to suggest the former is FAR quicker and easier than the latter.

michaelgears · 05 May 2011

Thanks for your replies guys, I know this was a tough one. We found the cause of the error and you will not believe what caused it. Another USB device was connected to the computer caused the error, in this case it was a microphone. Once microphone was disconnected, no error occurred upon acquisition. But we still have to fix the app.

SmurofNeves · 06 May 2011

Do you need help fixing the app?

WarGato · 13 Apr 2012

michaelgears said:

Thanks for your replies guys, I know this was a tough one. We found the cause of the error and you will not believe what caused it. Another USB device was connected to the computer caused the error, in this case it was a microphone. Once microphone was disconnected, no error occurred upon acquisition. But we still have to fix the app.

I cannot believe this is the answer, but it is. Unplugged my USB camera with microphone and BAM! my code starts working again. My code was dying on a SqlConnection.Open call, was not able to capture the exception. Looked in the Application Log and noticed it had to do with ntdll.dll, which eventualllllly led me to this forum and this post. I have two things to say about this: michaelgears, thank you so much for posting that answer, never in a million years would I have figured that out. And Wow, this is about the most obscure , completely unrelated to my actual code, error I have ever had to run down, thank you Microsoft.