Musescore 3 crashes Windows 11 Laptop if closed or unplugging headphone cable
Sooo my friends,
After a very long debuggin phase including Microsoft support, Dell Support, Intel and countless hours by myself, I discovered that it is in fact Musescore that seems to be the culprit.
The symptoms:
1: Opening the Laptop after it has been closed for some time results in a blue screen "Your device ran into a problem and needs to restart..."
It will only happen after some time.
2: While working on the laptop, pulling out (unplugging) the headphone audio connector also immediately results in the same blue screen. (I use the audio connector to connect to my external amplifier)
The blue screen flashes by rather fast so I took a picture of it with my phone and the small print states:
Stop Code
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENNDING_OPERATION
What failed: IntcOED.sys
Further investigation showed that this is in fact the
Intel Smart Sound Technology (Intel SST)
driver version 10.25.0.3950 that failed.
All efforts to try and resolve that by updating the driver have failed. There is no updated driver or anything like that available from anywhere that I could find.
I then noticed that this problem does not occur when Musescore 3 in not open.
I tried to disable this Intel Smart Sound Technology (Intel SST) in device manager.
Then, Musescore only produces super loud white noise but the crash problem stops.
Musescore did NOT crash anything when in Windows 10, that started on Windows 11.
Any ideas?
Best regards
Bernt
Attachment | Size |
---|---|
WIn11 crash Intel SSD 20250518_133150.jpg | 3.12 MB |
Comments
What version of MuseScore 3 exactly?
Does it happen with MuseScore Studio 4(.5.2) too?
In reply to What version of MuseScore 3… by Jojo-Schmitz
I do not have that - sorry.
Does it have a different implementation of how it interfaces to audio drivers?
While any version of MuseScore is open in any version of Windows...
That just the way it is and not likely to change.
Both can cause MuseScore to fail and/or crash. I've never heard of either causing a blue screen. That is some kind of system problem.
Sibelius has the same thing happen.
So, yes, MuseScore is the "culprit", but easily avoided.