Jump to content

hevanw

Members
  • Posts

    1
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I know this is an old thread but wanted to share my similar experience. After 2.5 years of inactivity, I decided to revive my music hobby. I used to have Sonar X1 and Sonar Platinum. Haven't gotten to trying out the free CbB yet. I figured I'd kick off with Sonar X1 as I have all installers, docs, and experience with that. Well, upon first launch of X1, it will run the Wave Profiler, and bam, BSOD. After some experimenting, it was obvious that it was the latest Focusrite driver that is causing this. What I found is that the WDM/KS driver is at fault. There's all sorts of ugly things going on. E.g. the inputs of my 18i8 also show up with some funky "fniusbwave" names as well. Sonar X1 would also complain about them and ask to disable. ASIO on the other hand is perfectly fine with proper names for the inputs. As I still had my old drivers lying around, I gave those a try, and that didn't give any issue at all. Wave Profiler would run fine, and the inputs under the WDM/KS driver model were also properly named. Unfortunately ASIO did stutter with these drivers as I experienced with Dimension Pro. So in the end I returned to the latest drivers. Now I just hope that there are no other programs that may be using the WDM drivers, like regular Windows programs, and would cause a crash. So far, no problem with things like Spotify or YouTube. EDIT: I had the problem with driver version 4.63.24.564, which is also mentioned in this thread. Through Google, I found out that Focusrite also publishes a beta driver here : http://beta.focusrite.com/releases/focusrite_usb2_drivers/ . So I took a shot at installing 4.64.15.598, and to my big surprise this effectively fixes the BSOD. Or at least the one that I could easily trigger with the Wave Profiler. The funky fniusbwave names are still there for WDM/KS but at least the most important issue got resolved !
×
×
  • Create New...