ProppFrexx ONAIR User-Forum

Hi there,

So I just started trying to get my radio broadcasting stuff all back in order to work on a small internet radio project here. I just did a fresh install of PFOA and set my mixers up in the software like I had before and am getting a CTD after a few minutes. I'm not sure if it's because I'm on teamspeak (a gaming voice chat software) while using PFOA but I've tried without that program running and still have issues. Below is the log from Windows Event Viewer including my system specs:

Windows 10 x64 Pro
ASUS Rampage III Formula Main Board
Intel i7 970 CPU
ASUS GTX 970 OC 4GB GPU
24 GB DDR3 Ram
FocusRite 2i2 Audio Interface

System Log:

Log Name: Application
Source: Application Error
Date: 2/27/2016 3:32:49 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Chris-PC
Description:
Faulting application name: ProppFrexx ONAIR.exe, version: 3.0.15.21, time stamp: 0x562dfb5d
Faulting module name: mfmpeg2srcsnk.dll, version: 12.0.10240.16412, time stamp: 0x55b995f4
Exception code: 0xc0000005
Fault offset: 0x000722c1
Faulting process id: 0xff0
Faulting application start time: 0x01d1719c54e7da41
Faulting application path: E:\radio42\ProppFrexx ONAIR\3.0\ProppFrexx ONAIR.exe
Faulting module path: C:\WINDOWS\System32\mfmpeg2srcsnk.dll
Report Id: 5118abb5-40e5-4052-a18f-483729155403
Faulting package full name:
Faulting package-relative application ID:
Event 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="2016-02-27T20:32:49.000000000Z" />
<EventRecordID>22120</EventRecordID>
<Channel>Application</Channel>
<Computer>Chris-PC</Computer>
<Security />
</System>
<EventData>
<Data>ProppFrexx ONAIR.exe</Data>
<Data>3.0.15.21</Data>
<Data>562dfb5d</Data>
<Data>mfmpeg2srcsnk.dll</Data>
<Data>12.0.10240.16412</Data>
<Data>55b995f4</Data>
<Data>c0000005</Data>
<Data>000722c1</Data>
<Data>ff0</Data>
<Data>01d1719c54e7da41</Data>
<Data>E:\radio42\ProppFrexx ONAIR\3.0\ProppFrexx ONAIR.exe</Data>
<Data>C:\WINDOWS\System32\mfmpeg2srcsnk.dll</Data>
<Data>5118abb5-40e5-4052-a18f-483729155403</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Really appreciate any help with this. There's no error logs from PFOA itself, only the windows log.

Additionally this log popped up in the Event Viewer as well:

Log Name: Application
Source: .NET Runtime
Date: 2/27/2016 3:32:49 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Chris-PC
Description:
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 53D522C1

Event 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="2016-02-27T20:32:49.000000000Z" />
<EventRecordID>22119</EventRecordID>
<Channel>Application</Channel>
<Computer>Chris-PC</Computer>
<Security />
</System>
<EventData>
<Data>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 53D522C1
</Data>
</EventData>
</Event>

The faulting module is actually the file called: mfmpeg2srcsnk.dll

This file belongs to the Windows Operating System and is part of the Media Foundation which is responsible for the audio processing.
Hard to say why this is failing and creating and exception.
May be it is corrupted, not correctly installed or it is failing due to a system driver issue.
E.g. it could be a sound driver issue. But it could also be a decoding error with a specific file.

Do you get the exception with every audio file or only with certain files during playback?
And is the exception reproducible?

As there is no direct ProppFrexx error being logged, I am afraid it is a system issue and not directly a ProppFrexx error.
So please double check your system and check if may be some of your audio files are corrupt?

Hey Bernd,

I get the exception any time ProppFrexx is open actually. I've let it sit with nothing playing at all and the mic muted and still get the crash so I'm kind of at a loss. I haven't noticed it giving this exception on any certain song but I'll do some testing here. I'll load up the same playlist everytime and let it play out and log which file it stops on. The odd part is when there's nothing at all playing or running on PFOA and it crashes. I'll also try to run it without a playlist loaded and see if it still crashes.

I guess I could try to completely wipe PFOA out of my system and get all traces somehow and maybe start over just in case there is something there that may be conflicting. I do have ProTools installed which installs an ASIO driver and it errors out when not in use. Maybe that's causing an issue so I'll uninstall that driver along with VoiceMeeter which is another audio driver for a 'virtual audio interface' and strip down to bare FocusRite drivers and the Windows drivers.

**Update** I tested this issue about 5 times now in a row. It doesn't matter if there is a song playing or if the encoder is running etc. But at exactly 11 minutes and 50 seconds (every time) the program crashes with that exception. I've run SFC /Scan now and fixed any system files. Aside from re-installing Windows 10 I'm stumped... I also just completely uninstalled PFOA 3.0.15.21 but now realized that I don't have a copy of the installer anymore. I know the new version is 4.0 and eventually I'll more than likely upgrade to that but can't afford it at the moment. Is there a link to v3.0 anywhere? Searched the forums and the links I found are broken. Thanks

That's exactly it Bernd. I start PFOA and at exactly 12 minutes (I thought it was 11:50 but 10 seconds is from loading a playlist etc) the program crashes with that exception even without loading a playlist or doing anything for that matter. Just having the program open in general.

Today I have tried what you said, loaded it up and instead of using ASIO I used WASAPI and WDM both. Still got the same exact crash. I have not done a 100% clean wipe/reinstall of PFOA yet but that'll be my next step just in case my old install that I copied over was corrupted. If worst comes to worst I'll have to do a Windows 10 reset but hoping to hold that off till the last second. I unfortunately don't have another computer to test the software on at the moment but I'm sure it's as you have said and is a driver/system issue. It's just getting to the bottom of it without taking Windows back to day zero lol. Thanks for your help with this! Really appreciate it.

**Update** Just wiped PFOA completely and did a 100% fresh install from absolute scratch. No traces of PFOA were left in the PC. After installing from the new installer and setting things up with my mixer in PFOA the program now crashes within a couple minutes at most. Still getting a crash just way faster and more aggressive now. Not much time to even change audio driver inputs etc. I'm going to do some hardware testing next (Unplug my Scarlett 2i2 and run on windows audio etc.). Looks like I may indeed ultimately need to do a win 10 reset though as this isn't clearing up

~Chris

Hi,

here is the link to the v3.0 insztall:
http://www.proppfrexx.radio42.com/downl ... _Setup.zip

What do you mean by it crashes after exactly 11:50 sec.?
Does it mean you start PF, do absolutely nothing and then it crashes with the above exception?
If yes, it must have something todo with your audio driver. You might try a different driver mode (e.g. switch from WASAPI to WDM or vis versa) just to see, if that changes things...

Do you have a 2nd PC somewhere to see, if the issue is there the same?

Hey Bernd,

Wanted to post an update for ya here in case someone else has a similar problem down the line. The issue with my PFOA is resolved! Without having to reformat or reset my PC as well... For some reason, there were old sound devices registering as being used in PFOA which were no longer plugged in to the computer. I can only imagine that these we'll call them 'imaginary devices' are what triggered the exception every time since PFOA and Windows were looking to access them but yet they don't exist on my PC. After wiping out all traces of PFOA (or so I thought) I switched to ASIO and still got the crash. I then thought of the AppData folder and went searching.. The appdata/roaming folder still had settings saved which were storing these 'imaginary devices' in the config. After wiping the appdata folder for PFOA and switching to my ASIO drivers I got an error that the other sound devices didn't exist. After making sure they were no longer selected anywhere in the program I am now back to normal and have zero issues! Thanks again for helping to figure out where I needed to look for the problem because otherwise I'd probably still be searching lol!