After our recent round of Microsoft patches, we are seeing an usually high number of servers BSODing with STOP 0A errors with no conclusive resolution.
At the same time, we are seeing server crashing with 0A or C5 error when Symantec antivirus is running its schedules scans. I did a sav debug on those servers and did not identify any particular reason for the crashes. At first I thought the crash was caused by SAV while scanning application files, but it wasn’t. [MS confirmed this is a different issue]
MS confirmed that servers running terminal services (like ever server) with MS09-059 can potentially have this stop errors and the only solution is to apply this hot fix below: