Yeah, there is a divide between what software will or will not crash. Essentially it's a combination of software using features and the features not being stabl

Yeah, there is a divide between what software will or will not crash. Essentially it's a combination of software using features and the features not being stable. The best combination is either software that knows the issues for each implementation and can work with it, or software that doesn't use the features (either not using them natively or by making it unavailable to the software). It's amazing how string-and-chewing-gum some hardware is with software working around so many issues to not crash. Sometimes there is good documentation, errata or usable flags (like MSR bits), sometimes it's just 'lower the pressure until it stops crashing' and you get a fat list of quirks.