I had my first crash in
years going to 2016 11.. I dropped in CA2A on a fiddle track during playback.. If I add it prior to transport on, no problem. Course, could have been the fiddle...
So - 2016 10 is the most solid, but I didn't roll back to it. Didn't need to in my case and since I know the bakers are on it, I'm fine with 2016 11.
To keep the apples and oranges separate, I think the luck is in the entire environment and keeping it stable, since I seem to be having really good results. I'm just slightly smarter than a monkey so I emphasize LUCK.
In my case, the PC is relatively new, more than meets minimum spec for all the products I use, its CMOS is up to date and its plugged into a line conditioner. I keep the OS, Win 10, up to date - but do not use auto updates on it, or any software. Win 10 has been by far the most stable OS I have used for DAW work - since Windows 3.1. The ONLY software other than the OS supplied products on the DAW are Platinum, Waves, Adobe PDF viewer, Studio One 3, UC surface, MOTU AVB drivers, Presonus drivers, and Eventide H9 control. I also keep these products up to date AND keep up with product direction as good as I can - I'm a monkey, but I can read. I KNOW through experience, a key reason to stability is relatively new audio interface units AND keeping the drivers and CMOS up to date.
My average track size is around 40, with around 16 stereo buses. Depending on projects, my VST count per track is generally 2 if not more. Love the new load balance stuff the bakers have put out recently by the way... I record audio, very little MIDI - drum tracks when I'm fleshing out a new song mostly. I'm on the machine daily, at least a few hours. On weekends, I usually run (sit?) 4 hours. However, I did one 16 hour session a few weekends ago - non stop, no crashes or glitches. The only problem with that session was seat-itis.
Best regards,
LL