Blue screen (stop error) occuring constantly but not always at the same times

• Mar 28, 2021 - 23:49

Hi,

I have been trying to use MuseScore for the past few months and invariably come across this issue every time I try to come back to it. I am almost certain it is some sort of issue or incompatibility with SOME sort of audio driver of mine but I have no idea how to figure out what.

I cannot reproduce this issue reliably but MuseScore will, invariably, cause a bluescreen during every session. However, WHEN it causes the bluescreen is not consistent:
— opening MuseScore can cause other applications using audio (i.e. Foobar) to hang, and when I try to interact with them a bluescreen occurs
— trying to adjust the audio I/O settings in MuseScore usually causes a bluescreen
— and, if all else fails, closing MuseScore will cause a bluescreen.

I don't really have any idea why closing MuseScore would bluescreen my computer, let alone the other issues.

• I am using 3.6.2 ... fresh installs. I am uninstalling and reinstalling MuseScore every time I come back to trying to use it.
• I am on Windows 10 Pro.
• It isn't related to any scores as I am creating fresh, new files every time I try to use this program.
• My primary audio playback device is a Focusrite USB Scarlett 2i2 first gen, drivers are the newest (4.65.5.658, firmware 492), through which I have a headphone output and mic input
• I am using no other audio playback devices (all others are Disabled in the Windows Sound manager)
• NO OTHER PROGRAMS cause this issue, I have never encountered a bluescreen with relation to audio programs outside of MuseScore

Any ideas as to what I can do? I suspect it might be a combination of an incompatibility and a wonky driver, but I do not know where to start looking. I have read the "known incompatibilities" list and while I do use a Wacom tablet, it is never plugged in when I am using MuseScore.

Thank you—
B

Comments

• Mar 29, 2021 - 01:10

For trouble shooting, I would strip your system down to basics. Disconnect all peripherals. No Focusrite. No midi keyboard. Onboard only. Shut down the computer for a minute to let it think about its sins. Start the computer. Open MuseScore and see what happens. If it works, you can start adding stuff.
I have a Focusrite. You have to make sure it is plugged in before you start MuseScore. As well as select it properly in I/O. API setting needs to be ASIO driver.

Reply

• Mar 29, 2021 - 13:31

Aye, from the tests I ran this morning it seems that something in the Focusrite's setup is bugging it out. Do you know if MuseScore needs a specific sample rate to run properly? It may be in part because the Focusrite was running at 48000 instead of 44100. Also going to be trying disabling the "apps can take exclusive control" option for the Focusrite in the sound manager. Will see what happens.

Reply

• Mar 29, 2021 - 22:22

I haven't messed with my Focusrite all that much with MuseScore. Only to plug it in and see if headphones work. MuseScore sample rate is adjustable. You might check in the manual to see if there is a downside to changing it . Come to think of it, I'll bet that 48000 creates a bigger file.

Reply

• Mar 31, 2021 - 01:50

An update:

I am not sure why this solution seems to have worked so far, but I have done these two steps and not encountered a single crash or BSOD yet despite attempting deliberately to cause one by messing as much as I could with MuseScore's audio settings (so, this is good):

  1. I have set the audio sample rate of my Focusrite's ASIO to 44100 Hz.
  2. I have disabled "exclusive control" of the Focusrite in the Windows audio settings.

Doing these two things seems to have stopped the BSODs. Not really sure why this worked, but I won't complain as long as it stays working. I will report back in case it changes or stops working.

—B

Reply

Do you still have an unanswered question? Please log in first to post your question.