Backup Exec CPS 12 Causes random server reboots.

After installing Backup exec CPS 12 on my Windows 2003 SP2 File server, it blue screens reboots randomly, sometimes as many as three times a day.  I generally get a stop error as I have listed below.

The only programs running on this server are McAfee Virus Scan 8.7i and Executive Software Undelete 3.0.083.

I can't seem to find any information about why this error might be occuring.  Listed below is entry in the event viewer that comes up after the server restarts.

 Event Type:      Warning
Event Source:      USER32
Event Category:      None
Event ID:      1076
Date:            11/12/2008
Time:            1:11:25 PM
User:            COMPASS\administrator
Computer:      TCHAIKOVSKY
The reason supplied by user COMPASS\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
 Reason Code: 0x805000f
 Bug ID:
 Bugcheck String: 0x00000050 (0xb9c8e954, 0x00000000, 0x8089b780, 0x00000000)
 Comment: 0x00000050 (0xb9c8e954, 0x00000000, 0x8089b780, 0x00000000)

For more information, see Help and Support Center at
0000: 0f 00 05 08               ....    
Who is Participating?
AndrewinMPLSAuthor Commented:
Removing Symantec. Replacing with Commvault Simpana 8. Veritas was the truth!
I wouldn't be surprised if this would be an incompatibility of CPS and McAfee virusscan. Make sure that both products are fully patched. Try removing McAfee for a while and see if the problem disappears.
AndrewinMPLSAuthor Commented:
I ran CPS over the weekend on this server using Symantec Antivirus instead of McAfee with no errors, but then on Monday as users started using the system again, I started getting random reboots with the same stop error as listed above.  

It seems that when users are accessing files on this server (it is my main file server), it somehow interferes with CPS and causes the reboot.  Once I remove CPS, the problem stops.
I know this seems to have started after installing CPS, but have you run RAM diagnotics already? Microsoft at indicates RAM as a common cause for 0x00000050 crashes.

It the bugcheck code always 0x00000050 or does it change between reboots. A changing bugcheck code is often an indication of a hardware problem.

Is the system set up to create a memory dump? If so, you may want to open the dump in the Windows debugger and run the !analyze -v command. See what it reports or post the output of the !analyze -v command.
AndrewinMPLSAuthor Commented:
We also had found this reference. We replaced all of the memory in the server. It is less than 1 month old. Again we do not have issues with the server if CPS services are removed. We are checking into our IScsi drivers and dump file analysis. Any other thoughts would be welcome. :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.