3CX PhoneSystem service crashes with Event ID 1000

[crsc]

I had V5.0 b3648 working with 24 extensions with only minor isssues for 3 days. All extension are IP phones. Today, the 4th day, the system has crashed a number of times with the error at the end of this message. The only modification has been the introduction of the 3CX client app, in Desk Phone mode, at three workstations.

Do anyone knows the meaning of this error ID? I also have the Dr. Watson log for anyone to who might want to analyse it.

Thanks.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 12/14/2007
Time: 1:48:32 PM
User: N/A
Computer: PBX
Description:
Faulting application 3CXPhoneSystem.exe, version 5.0.3648.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x0001218e.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 33 43 58 ure 3CX
0018: 50 68 6f 6e 65 53 79 73 PhoneSys
0020: 74 65 6d 2e 65 78 65 20 tem.exe
0028: 35 2e 30 2e 33 36 34 38 5.0.3648
0030: 2e 30 20 69 6e 20 6e 74 .0 in nt
0038: 64 6c 6c 2e 64 6c 6c 20 dll.dll
0040: 35 2e 31 2e 32 36 30 30 5.1.2600
0048: 2e 32 31 38 30 20 61 74 .2180 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 31 32 31 38 65 0001218e

-----------------------------------------------------------------------

 

[Mori]

My guess is that your 3cx serverbox is having some trouble.

Its the windows systemfile ntdll.dll thats faulting.

Read more about it here.
http://www.computerhope.com/issues/ch000960.htm

 

[crsc]

I know about the Windows system DLLs. The crash is in response to a system call from the application. The event ID in this case is provided by the client application. The most common case is a call to an object in the system dll that has already being released.

Any of the 3CX programmers what to take a look at it?

Thanks.

 

[archie]

It seems the crash is caused by unregistration and immediate registration of our client. These both bugs will be fixed really soon. Though, I have yet to found a place to fix in PBX code, and client code is fixed already.