Hi Opus.
I'm getting quite a few P3DBKCTRL.EXE crashes with P3DV4.2, Opus FSIv5 and Windows 10
Seems to happen randomly but usually takes about 20 or more minutes of flight before it happens.
Does not seem to be related to anything I was doing at the time.
Crash report below with msvcrt.dll as the faulting module.

Thanks
gb.

 

Log Name:      Application
Source:        Application Error
Date:          25/02/2018 7:27:49 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      gb-FlightSim
Description:
Faulting application name: P3DBKCTRL.EXE, version: 5.2.0.1, time stamp: 0x59e8746f
Faulting module name: msvcrt.dll, version: 7.0.14393.0, time stamp: 0x57899155
Exception code: 0xc0000005
Fault offset: 0x000886ba
Faulting process id: 0x128c
Faulting application start time: 0x01d3ae0ded591a61
Faulting application path: C:\OPUSFSI_V5\P3DBKCTRL.EXE
Faulting module path: C:\Windows\System32\msvcrt.dll
Report Id: 08364c0c-84d9-4cd2-b778-1055fbf9326c
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="2018-02-25T08:27:49.683949800Z" />
    <EventRecordID>11454</EventRecordID>
    <Channel>Application</Channel>
    <Computer>gb-FlightSim</Computer>
    <Security />
  </System>
  <EventData>
    <Data>P3DBKCTRL.EXE</Data>
    <Data>5.2.0.1</Data>
    <Data>59e8746f</Data>
    <Data>msvcrt.dll</Data>
    <Data>7.0.14393.0</Data>
    <Data>57899155</Data>
    <Data>c0000005</Data>
    <Data>000886ba</Data>
    <Data>128c</Data>
    <Data>01d3ae0ded591a61</Data>
    <Data>C:\OPUSFSI_V5\P3DBKCTRL.EXE</Data>
    <Data>C:\Windows\System32\msvcrt.dll</Data>
    <Data>08364c0c-84d9-4cd2-b778-1055fbf9326c</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Getting same thing, but with Windows 7.

I will try mine out here using the latest OpusFSI Beta Version 5.21.3 and P3D v4.2.

In the meantime you could make sure your Windows is fully up to date.

Stephen

Mine has started to do it too on P3D v4.1, also around 20 minutes into a flight. I get the 'P3DBKCTRL.EXE has stopped working' message so I shut it down. OpusFSI keeps running though.

Windows 10 Home, P3D v4.1, FlyInside v1.8

Yes OpusFSI keeps running in my case too.

gb.

Thanks, I may have to consider and auto re start as the 'known' problems lie within the Windows audio library software and Microsoft have said in the past they are not going to update it. I will investigate further though to see if something can be done to stabilise it.

Are you both using the recommended dedicated USB sound card?

Stephen

Edited March 1, 20188 yr by Opus Software

2 hours ago, Opus Software said:

Are you both using the recommended dedicated USB sound card?

I have the SB X-fi Go! Pro usb stick. Is that still it?

gb.

Yes that's OK.

I have already modified the BK Control software so that,

1) Any crash will not notify you.

2) The OpusFSI server program will detect the crash and quickly auto restart the BK control program.

3) The BK control program will initialise itself much quicker.

So no matter what Windows does you should notice nothing more than a slight interruption to the BK vibrations.

I will post the new software in the next beta.

Stephen :-)

OpusFSI Beta Version 5.21.5 has been posted which includes the above ButtKicker auto restart and speedy initialisation upgrade.

See our SimForum Announcements,

http://www.simforums.com/forums/announcements_topic42608_post380374.html#380374

Stephen :-)

Hello I am in 5.22.2 and I still have this message every 20 mn ! very annoying

What can be the problem ? (I also disabled the windows error notification)

https://ibb.co/hq2Dex

Its a known windows driver problem and nothing to do with OpusFSI. The wdmaud driver has a problem with handling audio loops.

Nothing I can fix or change in Opus.

Microsoft has refused to fix it. Just close the message box and Opus will restart and re initialise the BK control program automatically.

I did modify the software so the OpusFSI software will not notify you of the crash (cannot stop windows doing what it does). Are you running the software in 'Admin Mode' and with AV and Win Defender shutdown.

Stephen

Edited April 7, 20188 yr by Opus Software

Just checked my mods. Both the FSX and P3D BKCTRL programs attempt to handle their own program exceptions and Application errors (they take control of all Application errors). This includes all errors (crashes) within the Windows 'wdmaud' driver. So you should not be seeing any pop up notifications, none are generated by the software.

Make sure your P3DBKCTRL.EXE program has been upgraded during the 5.22.2 install process.

I will check if anything else on your system could cause these messages to pop up even though they have been disabled. In the meantime run the FSISERVER.EXE with your P3D program argument manually via a desktop shortcut and force the FSISERVER.EXE to 'Run in Admin Mode'.

Stephen

Edited April 7, 20188 yr by Opus Software

The pop up may be totally out of my control if triggered within the Windows driver software. Nothing I can do to stop windows displaying it. In which case just close it and Opus will auto restart the BKCTRL program. No exception within the Opus BKCTRL software will cause a pop up message, it will just be handled automatically, but how Windows sees a wdmaud crash may be out of my control.

Stephen

It's been a while but I've only recently had the chance to try the new version of OpusFSI with my BK. I've done around a dozen flights and the BK has worked fine. In the instances where it does crash, OpusFSI restarts it automatically so I don't even know it's happened (I fly in VR so I don't see my desktop).

Glad to hear. Thanks for the feedback.

Stephen