AnsweredAssumed Answered

It wasn't 16.5.3!

Question asked by samasaurus on May 27, 2016
Latest reply on May 28, 2016 by mpgrimes

Turns out it was my new RAM, not the patch. It just took some serious gaming to make it go screwey.

Outcomes