ProppFrexx ONAIR User-Forum

Hello and HELP

We run Proppfrexx on a dedicated server – windows 2022 server 64 bit and are experiencing irregular Proppfrexx crashes (yesterday 3 times – last time before that was 3 weeks ago) due to ntdll.dll
We always get the same error in the windows log – there is no error in the Proppfrexx log (maybe because Proppfrexx doesn’t have the time to write it due to the crash).

We’ve had this propblem since the move to the dedicated server, we’ve update Proppfrexx to the latest version and did all the windows updates, but the problem keeps pupping up.

Does anyone experience the same issue ? Does Proppfrexx have a difficult time with windows 2022 server (difficulties in TRY and CATCH)

Thank you for your advice and help !
Ewoud

When there is no entry within the Error.log, the crash is definitely not related to a direct application error! Every try-catch or even uncaught exception will always be recorded - that is for sure.

The ntdll.dll is the core kernel library of the windows operating system. Ie. if that library causes a crash, this is a direct indication, that the operating system is. It stable. This can be caused by any component of the system, eg. the IO System, the Network, the Audio system, memory, graphics etc.
Unfortunately this can not directly be diagnosed. I am sorry.
Often a reinstall of the operating system might help, but is no guarantee, as even defect hardware might cause this issue.

However, there are many users, who use that server operating system.

Hi Bernd,

There is indeed no direct application error but there is no entry in the prop log, so no entry is written by prop, so prop crashes as the error generated isnt handled. Our question is: is it possible to catch the ntdll error so prop ignores it and keeps operating.

Do you know of any incompatibilities of the.prop software with virtualisation?

Thank you!
Ewoud

Of course, as said. An application can only react on and detect errors caused by the application.
Any error causes outside the application, eg. within a driver or the OS can not be detected or logged. Those kind of errors are only present in the Windows Event log.