My colleague Richard, who is an expert at diagnosing problems in MusicXML files, has taken a look at the file you sent, and this is what he found.
There are a few problematic passages in this file, which are all to do with the rounding of divisions values for tuplets. The problems are in bars 78, 79 and 99: the first two have 17:12 32nd-note tuplets, and the third has a 25:12 32-note tuplet. The divisions value used for the individual notes in the 17:12 tuplet is 42, rounded down from the real value which would be ~42.35, and the divisions value used for the individual notes in the 25:12 tuplet is 29, rounded up from the real value which would be ~24.8. I think the reason this is going wrong is that the MuseScore file attempts to correct the rounding errors across the whole tuplet by using a forward or backup node just after the tuplet has finished, instead of alternately rounding up and down individual notes within the tuplet as e.g. Sibelius does. In the case of the 17:12 you end up with an underfull tuplet which causes a crash, in the case of the 25:12 tuplet you end up with an overfull tuplet which trashes the remainder of the voice stream but doesn’t crash.
Dorico would ideally be more resilient to these kinds of problems, but equally MuseScore could perhaps approach this kind of encoding differently, too.