ProppFrexx ONAIR User-Forum

Hi Bernd,

Our studio version of PF is lately crashing regularly. From the Windows Event Log we get this:

Logboeknaam: Application
Bron: Application Error
Datum: 23-03-17 21:18:33
Gebeurtenis-id:1000
Taakcategorie: (100)
Niveau: Fout
Trefwoorden: Klassiek
Gebruiker: n.v.t.
Computer: AFM-Studio-1
Beschrijving:
Naam van toepassing met fout: ProppFrexx ONAIR.exe, versie: 3.0.15.21, tijdstempel: 0x562dfb5d
Naam van module met fout: ntdll.dll, versie: 6.1.7601.23572, tijdstempel: 0x57fd02d3
Uitzonderingscode: 0xc0000005
Foutoffset: 0x0004eb83
Id van proces met fout: 0x1b8c
Starttijd van toepassing met fout: 0x01d2a3fc564df97d
Pad naar toepassing met fout: C:\Program Files (x86)\radio42\ProppFrexx ONAIR\3.0\ProppFrexx ONAIR.exe
Pad naar module met fout: C:\Windows\SysWOW64\ntdll.dll
Rapport-id: e2a644e1-1005-11e7-a001-003067c46f94
Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-23T20:18:33.000000000Z" />
<EventRecordID>103815</EventRecordID>
<Channel>Application</Channel>
<Computer>AFM-Studio-1</Computer>
<Security />
</System>
<EventData>
<Data>ProppFrexx ONAIR.exe</Data>
<Data>3.0.15.21</Data>
<Data>562dfb5d</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.23572</Data>
<Data>57fd02d3</Data>
<Data>c0000005</Data>
<Data>0004eb83</Data>
<Data>1b8c</Data>
<Data>01d2a3fc564df97d</Data>
<Data>C:\Program Files (x86)\radio42\ProppFrexx ONAIR\3.0\ProppFrexx ONAIR.exe</Data>
<Data>C:\Windows\SysWOW64\ntdll.dll</Data>
<Data>e2a644e1-1005-11e7-a001-003067c46f94</Data>
</EventData>
</Event>

And for the .NET Runtime we get this error:

Logboeknaam: Application
Bron: .NET Runtime
Datum: 23-03-17 21:18:31
Gebeurtenis-id:1026
Taakcategorie: Geen
Niveau: Fout
Trefwoorden: Klassiek
Gebruiker: n.v.t.
Computer: AFM-Studio-1
Beschrijving:
Toepassing: ProppFrexx ONAIR.exe
Framework-versie: v4.0.30319
Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.
Uitzonderingsinformatie: uitzonderingscode c0000005, uitzonderingsadres 7791EB83

Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-23T20:18:31.000000000Z" />
<EventRecordID>103814</EventRecordID>
<Channel>Application</Channel>
<Computer>AFM-Studio-1</Computer>
<Security />
</System>
<EventData>
<Data>Toepassing: ProppFrexx ONAIR.exe
Framework-versie: v4.0.30319
Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.
Uitzonderingsinformatie: uitzonderingscode c0000005, uitzonderingsadres 7791EB83
</Data>
</EventData>
</Event>

Can you tell me what is wrong? Because it is happening almost every week now!

Also I noticed that when we use our external Airence mixer with PF the CPU load is always around 25% when PF is doing nothing!
Is this correct? When I unplug our external mixer it will only use 2% in standby time.

Best regards,
Jesper

Ok thank for your answer. We already thinking of upgrading to PF4. But we need to pay full price right now because we're too late upgrading.
So that's an issue for the people who decide. Right now I will figure out if we can turn back the .net framework update.
Thanks for now!

The error log indicated, that the crash happens directly within the .Net Framework itself (module ntdll.dll).
So it looks like one of your system components or system drivers is effectively causing the crash.
As the error just recently started to occur, I assume, that it is caused by some recent Windows or driver update (as you never updated ProppFrexx).
As a result, I cannot actually help much, but it seems, ProppFrexx is 'just' using the system component or driver (e.g. the graphics, network or sound card)...

I guess you know, that the v3 already came to its End-of-Live since 1 and 1/2 years. So there is no support anymore for v3.
You might install the new v4 to see, if the trouble disappears and then think of upgrading ?

Yes, that was your obvious decision.