Fax Server keeps faulting** NTDLL FAULT WINDOWS

[coldtech]

at 7:00 am:

Faulting application name: 3CXFaxServer.exe, version: 9.0.14510.0, time stamp: 0x4d00fccd
Faulting module name: 3CXFaxServer.exe, version: 9.0.14510.0, time stamp: 0x4d00fccd
Exception code: 0xc0000005
Fault offset: 0x000b5703
Faulting process id: 0xfd4
Faulting application start time: 0x01cba6b2851a2a2b
Faulting application path: C:\Program Files (x86)\3CX PhoneSystem\Bin\3CXFaxServer.exe
Faulting module path: C:\Program Files (x86)\3CX PhoneSystem\Bin\3CXFaxServer.exe
Report Id: 4c1752d7-1343-11e0-b75d-005056830011

Restarted the service and then at 10:30am:

Faulting application name: 3CXFaxServer.exe, version: 9.0.14510.0, time stamp: 0x4d00fccd
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c
Exception code: 0xc0000005
Fault offset: 0x0002e1fe
Faulting process id: 0xf68
Faulting application start time: 0x01cba7627999146f
Faulting application path: C:\Program Files (x86)\3CX PhoneSystem\Bin\3CXFaxServer.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 80348705-1360-11e0-b75d-005056830011

 

[nb]

Re: Fax Server keeps faulting ** NTDLL FAULT WINDOWS

But the fax service crashes, stops what?
Does this happen during operation?
Logs etc are required for Fax.
Also is this the only component that raises ntdll exception? Are there other components that are not 3CX Related?

 

[pratikdbl]

Hello there,
I also have the same problem but with 3cx mediaserver. It was also giving ntdll.dll problem. Then I tweaked something in windows. And the 3cx phone system worked for few hours. But again it gave kernel32.dll problem.

This problem has gone too much worse now. I have restarted 3cx several times. For few minutes it works but then many rings come at once which is not really a call. When the phone is received, it is cut. This has annoyed our Call Agents too much.

If you get any solution to this, please advise us. We have already posted this problem to 3cx but we haven't got any reply yet.

 

[nb]

What have you tweaked in windows? ntdll is a windows core component. If ntdll causes a crash there is something wrong there. Try giving full system updates.

 

[pratikdbl]

I enabled Data Execution Prevention (DEP) in System Advance Settings and added an exception - "Windows Explorer/explorer.exe". Then windows stopped popping up windows to notify ntdll.dll problem.

But the problem was not actually gone. These were other problems we got after that

1. A call comes to our extension 1013. The agent at 1013 receives the phone. But the phone is cut off and that call is directed to another extension. When picked up, it again cuts off and then goes to another extensions one by one, cutting off on reception.

There is same phone number in two queues which is abnormal. In this case also, the call goes to all the extension which cuts off on reception. In the snapshot attached you can find this situation.

2. Sometimes, some extensions don't get incoming call at all. That is, the ACD does not direct the call to some extensions at all even though the extension is free.

Pratik

 

[pratikdbl]

Sorry I could not attach snapshot

 

[nb]

What do the logs say? Are you sure this is not some ring group you made?

Or are you sure that there isnt some forwarding rule that rings for X seconds and then forwards to somewhere else?

What is ACD ?