Possible Deadlock Condition

[commission]

Hello

I am running Windows Server 2003 with SP2 as a domain controller and have recently noticed the following error message on the console.

"Windows - Exception" "Possible deadlock condition"

Does anyone know what this means?

 

[Tmagic650]

Application-Termination Messages

Application-termination messages from the Executive appear when the Kernel is about to terminate either the process in which an application is running or the thread of an application. Some of these messages advise you to perform an action before restarting the application, as in the following example:

The application or DLL <filename> is not a valid Windows NT image.
Please check this against your installation disk.
In other cases, the user action is strongly implied. The following example implies that you should make sure that the dynamic-link library is in the path before you restart the application:

The dynamic-link library <filename> could not be found in the specific path <path>

In yet other cases, you can only restart the application. If one of the messages listed in Table 38.4 reappears, contact the supplier of the application.

Message box title Message text:

Access Denied
A process has requested access to an object, but has not been granted those access rights.

Already Committed
The specified address range is already committed.

Application Error
The exception name (number) occurred in the application at location address.

Application Error
The application failed to initialize properly (number).
Click OK to terminate the application.

Application Exit by CTRL+C
The application terminated as a result of pressing CTRL+C.

Bad CRC
A cyclic redundancy check (CRC) checksum error occurred.

Bad File
The attributes of the specified mapping file for a section
of memory cannot be read.

Bad Image
The application or DLL filename is not a valid Windows NT image.
Please check this against your installation disk.

Buffer Too Small
The buffer is too small to contain the entry. No information has been written to the buffer.

Cancel Timeout
The driver name failed to complete a canceled I/O request in the allotted time.

Cannot Continue
Windows NT cannot continue from this exception.

Conflicting Address Range
The specified address range conflicts with the address space.

Corrupted Disk
The file system structure on the disk is corrupted and unusable.
Run the Chkdsk utility on the volume name.

Corrupted File
The file or directory filename is corrupted and unreadable.
Run the Chkdsk utility.

Data Error
An error in reading or writing data occurred.

Data Late
A data late error occurred.

Data Not Accepted
The TDI client could not handle the data received during a transmission.

Data Overrun
A data overrun error occurred.

Device Timeout
The specified I/O operation on name was not completed before the time-out period expired.

DLL Initialization Failed
Initialization of the dynamic-link library filename failed. The process is terminating abnormally.

Drive Not Ready
The drive is not ready for use; its door may be open.
Check drive drive letter and make sure that a disk is inserted and that the drive door is closed.

Entry Point Not Found
The procedure entry point name could not be located in the dynamic-link library filename.

EXCEPTION
A real-mode application issued a floating-point instruction and floating-point hardware is not present.

EXCEPTION
Array bounds exceeded.

EXCEPTION
Floating-point denormal operand.

EXCEPTION
Floating-point division by zero.

EXCEPTION
Floating-point inexact result.

EXCEPTION
Floating-point invalid operation.

EXCEPTION
Floating-point overflow.

EXCEPTION
Floating-point stack check.

EXCEPTION
Floating-point underflow.

EXCEPTION
Integer division by zero.

EXCEPTION
Integer overflow.

EXCEPTION
Privileged instruction.

EXCEPTION
Possible deadlock condition.



Aplication Termination. Find out what application is causing this message

 

[gbhall]

well, tmagic650 !!

Getting back to ground level......

A deadlock can be as simple as this. Suppose a weak programmer wrote an application that called exclusively for file A, then file B, however briefly. At another point, it calls for file B then file A also exclusively.

If by chance, two copies of the application got to that point simultaneously, they could each be stopped by the fact that the other thread was waiting for the first to release. (I got A, but could'nt get B says the first. I got B but couldn't get A says the second.)

The operating system would detect these two threads each waiting forever for an interrupt to release, hence the message.

Dont suppose that is any use to you at all....unless you happen to be running some third-rate software on your server, like a cheapo fax server, email server, virus checker, etc etc.

 

[commission]

Ok that gives me something to go on now

Cheers guys