0
0

If I open Nuendo 3 using my ASIO drivers, then open FMod Designer (v1.4.6) using my Windows drivers, close Nuendo and then close FMod I get a blue screen crash which says BAD_POOL_CALLER. It doesn’t crash until I close FMod Designer. This has also happened while using Designer simultaniously with other audio programs like Sound Forge and Vegas. It would be wonderful if instead of a blue screen of death, FMod could work alongside other audio programs or at least fail gracefully.

Many thanks,

Adam Smith-Kipnis

  • You must to post comments
0
0

Correction to my previous post: They were both using the same ASIO drivers but I’ve now switched it to use another sound card though I have not yet tested this same crashing issue.

  • You must to post comments
0
0

Sounds like a problem with your ASIO drivers or maybe FMOD’s interaction with them. Can you confirm that the BSOD does not occur when you use Windows drivers with FMOD Designer? Meantime, I’ll see what I can do to make our ASIO support more robust.

Cheers,

  • You must to post comments
0
0

I just tested opening Nuendo and FMod alongside each other using the same sequence of events as described in my previous post, except this time FMod was using my MAudio Ozone which is set as the default windows playback device while Nuendo was using the ASIO drivers on a Tascam FW-1884. I did not get the BSOD this time around.

  • You must to post comments
0
0

Thanks Adam. Also, I have to ask, do you experience any other ASIO-related problems on that machine i.e. BSOD, crashes when starting up/shutting down other programs that use ASIO?

Cheers,

  • You must to post comments
0
0

I don’t have this problem when starting up or shutting down other programs. I just have one strange OS soft crash that happens about a half hour after I start up my computer in the morning if I just logged out instead of shutting down the box the night before. Very strange but I’m pretty sure that it’s unrelated to FMod.

  • You must to post comments
0
0

Ok, thanks for that. I’ll go over our ASIO code and make sure we’re not doing anything naughty.

Cheers,

  • You must to post comments
0
0

BCCode : 19 BCP1 : 00000020 BCP2 : 8832AC10 BCP3 : 8832ADF0
BCP4 : 883C23C0 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Just got one more crash when closing down Absynth. I think I had FMod open and I closed it during the time that I had Absynth open running as a standalone. Absynth was also started using the Ozone and then reassigned to the FW-1884 ASIO drivers before I closed it.

Thanks for looking into it!

Adam

  • You must to post comments
0
0

Using v1.4.15 if I open a second version of FMod while one is already running and then close down both versions I will get a blue screen of death every time. I found this out when I accidentally opened another FMod window when I already had one open. The first error message I recieved was PFN_LIST_CORRUPT and the second time it happened I recieved BAD_POOL_CALLER.

  • You must to post comments
0
0

Thanks Adam, still trying to track that down on our end.

Cheers,

  • You must to post comments
Showing 9 results
Your Answer

Please first to submit.