Musescore 4 caused a bluescreen

• Oct 30, 2022 - 14:46

Not sure if it's caused by Musescore or my PC. I'm sharing it in case it helps; ask for any other info that may be useful.

Here is the log from EventViewer:

Faulting application name: MuseScore4.exe, version:, time stamp: 0x00000000
Faulting module name: MuseScore4.exe, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c90970
Faulting process id: 0x38a8
Faulting application start time: 0x01d8ec54121abaf0
Faulting application path: C:\Program Files\MuseScore 4\bin\MuseScore4.exe
Faulting module path: C:\Program Files\MuseScore 4\bin\MuseScore4.exe
Report Id: 4bc3820a-25f7-434f-a036-3ae111695b8f
Faulting package full name:
Faulting package-relative application ID:


A blue screen crash is always at least in part Windows' fault, but often it means an application is doing something it isn't - Windows just should handle it more gracefully.

In order for anyone to investigate, we'd need you to report this on GitHub as requested in the announcement, along with the score you were working on and the steps that led to the crash.

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