Crash on Win 10

• Nov 28, 2020 - 06:53
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Randomly
Status
closed
Regression
No
Workaround
No
Project

It was rather random.
Starting Musescore by itself crashed a couple of times.
Starting by clicking on a mscz file crashed a couple of times.
Both methods succeeded other times.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.2.311459983, revision: 465e7b6

PC: ASUS Zephyrus G14 with AMD Ryzen 9 4900H with Radion Graphics 3.00GHz

If there is an option to automatically send a crash report, I would like to do that.

Attachment Size
ScreenHunter_03 Nov. 27 22.52.jpg 41.87 KB

Comments

Status active needs info

Can't spot anything in that score that might explain crashes. And it doesn't crash for me either.

Steps to reproduce?

That is not a MuseScore crash though, but one of the Operating System (a BSOD, Blue Screen Of Death), and most like an issue with the operating system rather than MuseScore

Try Google on that "BAD_POOL_CALLER"

Severity S3 - Major S2 - Critical

Recently, I updated MuseScore and when I went to open it, is says " the previous session quit unexpectedly" and when I click "Yes, Restore session" it closes out and does the same thing again. How do I fix this? I've been working on a project for some time now, and I don't know how to open it.

In reply to by Jojo-Schmitz

I updated 11 outdated drivers and opened Musescore about 20 times. So far no more crash!
This was 1) surprising because this laptop is brand new and 2) confusing because crash only happened right after Musescore was run. But I do realize both aren't a proof that it can't happen. I'll keep watching out for this issue.
Thank you so much for giving excellent insights and help!
I feel this may be closed for now.

Status closed needs info

I saved the screen shots just in case. They are the ones marked with 'OUTDATED'.
There was one which I don't remember if it was included in this list that caused Windows from booting properly. I had to button-boot a couple of times and then go through troubleshoot so that the system could get back to a restore point. Other than that, everything ran OK. Sorry I can't remember what that driver was exactly.

Here is a note that I kept.

======================
Re: Bad_pool_caller BSoD

Windows is up-to-date.
This laptop was purchased new this week.

Followed suggestions from https://windowsreport.com/bad-pool-caller-windows-10/ and updated 11 outdated drivers.

https://support.microsoft.com/en-us/windows/fix-error-0xc2-bad-pool-cal…

One device driver update prevented the Windows from booting.
Performed repair by restoring to a previous point during bootup trouble shooting.

Upon successful restore, the following error window popped up.
"Check the Windows Store for more info about AMD Radeon Software."

Launched MyASUS.
Hardware Diagnostic showed 2 updates were needed.
GameFirst VI, and ROG Keyboard Firmware Update tool V2.3.0.