search
top

Uninstall NetBackup 6.5.3 Blue Screen Error Stop 0x0000007B

Recently while in process of cleaning up systems running Symantec NetBackup 6.5.3 ran into the issue of after uninstalling the application and rebooting was greeted by a blue screen with Windows Server 2003-based computer: “STOP: 0x0000007B”

This is due to the VSP.sys driver still being referenced in the Windows registry. If you have received this error it is easy enough to fix but you will need to boot the server into safe mode. Once in perform the following steps.

  • Open regedit
  • Delete the key HKLM\SYSTEM\ControlSet001\services\VSP
  • Delete the key HKLM\SYSTEM\ControlSet002\services\VSP
  • Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}\UpperFilters and delete value of the key called VSP.
  • Reboot

If you have not uninstalled NetBackup open Control Panel and uninstall Add/Remove Programs > Veritas NetBackup 6.5.3 (6.5 Release Update 3) & Veritas NetBackup Client then perform the same steps listed above.

References:
http://support.microsoft.com/kb/947480
http://www.symantec.com/business/support/index?page=content&id=TECH125786

3 Responses to “Uninstall NetBackup 6.5.3 Blue Screen Error Stop 0x0000007B”

  1. Pelliman says:

    Please note that NBU 6.5 will go into EOl soon. See this link on SYMC.com – http://seer.entsupport.symantec.com/docs/332616.htm

    The move to 7.x requires a 64-bit server. I’m biased would suggest using a NetBackup appliance to make that move to a new platform easier and more reliable.

    • newlife007 says:

      Peter,
      Thanks for the link to the EOL. Where I am employed we have been moving all our servers off 6.5.3 to 7.x with the latest updates and updated to Windows 2008 R2 and RHEL 6.x 64 bit. I posted this error we ran into early in the process of updating the clients on the servers. It was a nasty error that caused me some concern and wanted others to have another resource to assist in their migrations.

  2. Peter E says:

    Rhanks for posting info on this issue. Glad to hear you’re moving off 6.5.x. I simply wanted to make sure your readers knew about the impending EOL.

Leave a Reply

Your email address will not be published. Required fields are marked *

top