I see you mentioned that you had to replace some bad system memory (RAM) on your system. When system memory goes bad it can cause information to be stored on your hard drive incorrectly; I have seen it many times where bad memory actually corrupted a dump file and when the Error Reporting tool attempts to send it the either cannot or it sometimes will interfere with any security software program's proper operation.
I would recommend that you run a complete disk check on the affected OS drive to check for any errors that may have occured while the bad memory was in use.
SGFC, this could be a one-time random neutrino crash or a real, but uncommon issue. As can be seen in the log entries, the service was automatically restarted. What OS were you using at the time of this problem (I susect XP, unfortunately.) Is there anything in Norton's History under Symantec Error Reporting around the same time? If so, in the More Details, what Error ID is provided?
Actually there are quite a few errors dating back to May.
Thanks for the error IDs! Both errors types are very uncommon but after researching them, I think that I may have discovered another issue that I've asked one of our teams to research.
I had a recent WERFAULT Actor...do not recall a WERFAULT before ?
WERFAULT
[image]
just before WERFAULT
[image]
These tamper protection detections, as with SGFC's previous one, are Windows Error Reporting detecting the ccSvcHst 'crash' and trying to submit it to Microsoft for analysis.
re > the ccSvcHst 'crash' and trying to submit it to Microsoft for analysis.
I did review Problem Reports & Solutions....no event to match this time
I did review Norton's History under Symantec Error Reporting...last event was June 06
& Errors = 0
Would I have observed any behavior associated with the ccSvcHst 'crash' ?
Thnx
Depending upon which of the two instances of ccSvcHst crashes, the symptoms will be different. If the 'service' instance crashes, there should be nothing for you to notice, it should be automatically restarted within a few seconds. If the 'user' instance crashes, your tray icon may disappear. In some cases it may be automatically restarted but usually you have to log off and back onto your system.
Thanks for the error IDs! Both errors types are very uncommon but after researching them, I think that I may have discovered another issue that I've asked one of our teams to research.
Good to hear. It hasn't happened since this post. The only way I noticed it is because I was running a Full System Scan and when I got back the UI was gone. I thought I was having Déjà vu.