ProppFrexx ONAIR User-Forum

Thanks a lot! Also for the patience and understanding.

Just had anther error but different this time( I do have the crash dump, and have restarted ProppFrexx with crash dumps to try and catch that other error):

Faulting application name: ProppFrexx ONAIR.exe, version: 4.1.5.3, time stamp: 0x5dff6857
Faulting module name: bassenc.dll, version: 2.4.14.0, time stamp: 0x5b4caac6
Exception code: 0xc0000005
Fault offset: 0x000000000000253d
Faulting process ID: 0x2abc
Faulting application start time: 0x01d5cfbd03fec4ca
Faulting application path: c:\Program Files\radio42\ProppFrexx ONAIR\ProppFrexx ONAIR.exe
Faulting module path: C:\Program Files\radio42\ProppFrexx ONAIR\bassenc.dll
Report ID: 48d0080e-9f03-465f-a0fc-c153763893e4
Faulting package full name:
Faulting package-relative application ID:

.NET Application Error:
Application: ProppFrexx ONAIR.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF8AE93253D

No need for this crash dump, as this one you already send. Which is already fixed in the next version.

Just had the same one again:

Faulting application name: ProppFrexx ONAIR.exe, version: 4.1.5.3, time stamp: 0x5dff6857
Faulting module name: bassenc.dll, version: 2.4.14.0, time stamp: 0x5b4caac6
Exception code: 0xc0000005
Fault offset: 0x000000000000253d
Faulting process ID: 0x333c
Faulting application start time: 0x01d5d2470ef300f2
Faulting application path: c:\Program Files\radio42\ProppFrexx ONAIR\ProppFrexx ONAIR.exe
Faulting module path: C:\Program Files\radio42\ProppFrexx ONAIR\bassenc.dll
Report ID: 3f4b0b91-be06-4bd8-9a42-fd431ab93413
Faulting package full name:
Faulting package-relative application ID:

I will upgrade while it's now off to the new version you've just released.

This error is already fixed with the latest v4.1.5.4 a so please check for updates.

The original error never seems to have happened again?!

No other error, just keep getting the same one at the moment as I've listed above.

I've updated and hopefully that should be the last of these errors.

Well, the initial post in this thread relates to a different error - as said, which seems to have never happened again.

radio42 wrote: ↑28 Jan 2020 19:56 Well, the initial post in this thread relates to a different error - as said, which seems to have never happened again.

Yes, that error seems to have gone even though nothing has changed our end, and with that last update the other error too.
It's been running stable for for about a week now without issue.

Thanks for your help!

Perfect!

Does the new update 4.1.5.6 have anything to do with the bug I've reported here? I'm currently running with crashdumps enabled and don't want to restart ProppFrexx until it crashes again.