Sav10.0.1.1000 Brightstor 9 - backup bsod

Symantec is aware of the issue and released a new version of symevent to correct this problem. You may run into a stop 0x8E when you use BackupExec or Roxio Easy CD Creator.


I checked the Symantec FTP site, and the new sevinst.exe (symevent) was posted there yesterday. I recommend installing it, and the problem will probably go away.

thank you. I saw this post KB article on Symantec's site, and wasn't sure if it related to my issues, since I was not getting that exact stop message. of course, at this point, trying that could not hurt (much!). I will check it out and post here once I know the results. thx

What stop code did you get?

This is two different servers. One is a backup domain controller, the other is a file and print server. Most of the time, when it crashed it was caused by ofant.sys. So I removed the open file agent from one server just to test. I have seen bug check 0x000000c2; 0x000000d1; 0x00000044. This is from one of the servers. They are all over the place (errors) and I am looking at each one via microsoft. I know the main event on these 2 servers was the SAV10 update. I did nothing else to them that day.

I would definitely give the new symevent a shot. It won't hurt. I'd definitely like to see whether it resolves your problem.

I ran the symevent update. Noticed that symevent.sys changed from rev level 11.6.2.4 to 11.6.4.1. I've run 4 consecutive full backups without a crash. this was our Win2003 Secondary Domain Controller. I am going to let this run for a few days and see. the other server is a heavily used production server, and I removed SAV10, so I am going to have to wait a few days before I can take that one down again for reinstall, reboots and testing.

thank you for the advice on symevent. I will keep you posted.

Bettyb,


I getting ready to try this on one of my win 2000 DC's. I'm going to go from .359 to .1 to fix the cpu usage issue and thanks to oggywan will update the symevent immmediatly after that.

Wondering if you've had any further issues since updating?

THX

I updated from 10 to 10.1 to help with the rtvscan overhead issues. From a client perspective, this is much improved. I also wanted to turn off do scan at login, since it was very annoying - - I do full system scans daily on clients. One outstanding issue I still have - - my parent server ALWAYS gets an exception and the symantec service stopped when I unlock the server group, and when I attempt to manage any client - - I had been through all of Symantec's troubleshooting - no luck. I have two sites and this is happening on both server groups. Funny thing is it worked for about 6 weeks! I was hoping 10.1 would fix that, it did not. I have a dialogue going to Symantec - - but they have not been of much help. Pretty much telling me the same things I see in their knowledge base. I haven't updated symevent on that server yet and I am wondering if that could be a magical cure.

I have updated the symevent on my DC's and will try to update mine from .359 today as well. I'll let you know how it goes.

Please no BSOD