Home › Forums › Breakaway Audio Enhancer › BSODs caused by Breakaway Audio Enhancer driver on Windows 10
- This topic has 9 replies, 6 voices, and was last updated 8 years, 10 months ago by RichP.
-
AuthorPosts
-
September 17, 2015 at 9:55 am #3051raidendevMember
Hello.
I have a problem with random BSODs on Windows 10 Pro, here is MS answers topic describing problem: http://answers.microsoft.com/thread/d7a8b999-3c09-4ac0-a693-13a0b7c5e6e7
After some experiments and researches I'm pretty sure that problem is in Breakaway driver, because BSODs not happens when I uninstall it.
Please check out this minidumps: ttp://1drv.ms/1MZCmfYSeptember 21, 2015 at 5:27 pm #5626JesseGMembercode :DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT<br /><br />SYMBOL_NAME: portcls!PcWmiLogEvent+60<br /><br />FOLLOWUP_NAME: MachineOwner<br /><br />MODULE_NAME: portcls<br /><br />IMAGE_NAME: portcls.sys
Yeah, it's the Breakaway Pipeline crashing.
I'm looking into having a new Breakaway Pipeline driver & installer built,
and I'm looking into having a new WinLicense driver from Oreans available for Windows 10, which should get rid of all of the main problemsthat a few people are having, but just the same… the maintwoproblemsright now for Windows 10.November 6, 2015 at 6:33 pm #5627powerjamMemberI'm guessing my last BSOD is related to Breakaway DJ, as my system was rock solid prior to the windows 10 upgrade, but this is not proven. But reading the posts that Windows 10 is not compatible with Breakaway products is a pretty good giveaway, I'm just confused at how my BDJ worked for over a year just fine with my same laptop with Windows 8.1.
November 6, 2015 at 9:23 pm #5628MilkyKeymasterObviously, something has changed in Win 10 that BADJ is not aware of. It might be the audio driver that has been substituted and not as compatible as before. JesseG has indicated that a new build is on the way, so let's hope that that will fix things, or maybe Microsoft will issue a driver update.
November 9, 2015 at 7:41 pm #5629powerjamMemberGood to hear about the new build. Thanks, Milky!
I actually have figured out why my system crashed in Windows 10…I'll copy and paste from my OtsUsers post in Facebook:
I am using a Denon MC6000 that is incompatible with OtsAV due to the DAC 24 bit I believe. I use Breakaway DJ to bridge the gap between the MC6000 and OtsAV and it has been rock solid for years doing it that way.
The actual cause of the crash I do believe I have discovered a workaround…It is related to Breakaway, and it stems from the way I was booting the laptop. IF I booted the laptop before plugging in the MC6000 controller Ots would have no sound usually even if I plugged in the controller after the laptop was booted and before starting Ots. Then all I would do is go into Breakaway and go to I/O configuration and then make sure the controller was selected as the sound device and then go back out of it.
This was successful previously if this happened and seemed to work in Windows 10 also. BUT after an hour or so, windows would blue screen in Win 10 when I did this.
Now I've found that if I make sure everything is plugged in, especially the controller, then everything works normally, I can do practically anything I want on the laptop, run my DMX controller, play ED video mode and even surf the internet with 10 tabs open and have my Antivirus turned on. No lags, no delays, no crashes and maybe 10-11% cpu use, most cpu use is caused by Google Chrome tabs, more than what Ots AV video and breakaway use.
So, even though it says on their website that Breakaway doesn't work with Windows 8 or 10, I've been having great success using it as long as I boot up with the controller/sound card plugged in at boot time.
December 2, 2015 at 3:56 am #5630powerjamMemberWindows 10 crashed again and locked up, restarted automatically and started doing windows 10 updates during my gig. I was livid. Of course I had a backup ready to go, but it was very embarrassing and frustrating. This is the 2nd time in a month windows 10 locked up on a very high end laptop that ran perfect with all the same software on Windows 8.1 (including Breakaway DJ).
I am rolling back to Windows 8.1 today.
December 11, 2015 at 7:37 am #5631JesseGMemberthe BSOD is from the older Virtual Audio Cable driver (which Breakaway Pipeline is a licensed version of).
a fully updated VAC
and fully updated WinLicense driverhave been prepared for the next update of Breakaway.January 14, 2016 at 11:48 am #5632fxeconomistMember[quote author=JesseG link=topic=5177.msg18637#msg18637 date=1449819421]
the BSOD is from the older Virtual Audio Cable driver (which Breakaway Pipeline is a licensed version of).a fully updated VAC and fully updated WinLicense driver have been prepared for the next update of Breakaway.
[/quote]Ok, so what are the steps to get this working ?
Right now I have uninstalled Breakaway completely.
I don't know what's the WinLicense driver.
Is there any link to get a proper Virtual Audio Cable driver, does it have be installed before or after Breakaway, could you be more specific about it? Or we have to wait until there is a new release of Breakaway ?January 19, 2016 at 3:09 am #5633DJ PaisanoMemberAny update on a new version or a fix? I have had the bsod since windows 10 was installed.
January 28, 2016 at 4:35 am #5634RichPMember[quote author=JesseG link=topic=5177.msg18637#msg18637 date=1449819421]
a fully updated VAC and fully updated WinLicense driver have been prepared for the next update of Breakaway.
[/quote]Hi Jesse – the $64,000 question is WHEN will the "next update of Breakaway" be sent into the world? ;D
-
AuthorPosts
- You must be logged in to reply to this topic.