I do not accept Omni's ideas of running stability tests over long hours overnight.
I think there is a much simpler approach to that:
1) If a system is really unstable, then most applications would suffer some way and would become unstable.
2) If you install a virgin XP-SP2 system with the newest audio and sound drivers, install MS Office and a few other basics apps (Firewall, Antivirus, WinZip, Adobe Reader, Backup, MS Office 2003) and MC11 still crashes, then with the greatest probability MC11 might be the culprit.
3) Until 11.0.64 MC11 was pretty stable, although up to then I used it mainly for playback. Starting with 11.0.70 I ripped about a dozen cd's, re-ripped another 2 dozens and imported many new images doing plenty of tagging. It was at that point that MC11 started to crash on a quite regular basis (with the old 2 years old setup and also with the freshly installed XP-SP2.
4) I feel that for beta testing MC11 should have some kind of debug option that can be turned on in case of need and automatic reports go directly to J River.
I read somewhere that Microsoft gets nowadays most of the bugs from Windows and their programs from their built-in automatic error reporting system and not from beta testers any longer. A beta tester's view in some way is always quite subjective and also error-prone