Knowledgebase: > Server Applications
System State Backup Fails with "The system state backup process failed with the following exit code: -3
Posted by Ben Bower, Last modified by Kelly Mitchell on Sep 02, 2015 04:42 PM


You receive the following error when trying to perform a system state backup.

[Failed to backup system state: ] 0x30000: The system state backup process failed with the following exit code: -3; please check the log files in C:\Windows\logs\WindowsServerBackup {eFS:ClieFacade:4733}.

Upon checking the log files in "C:\Windows\logs\WindowsServerBackup\" you find the below error.

Error in backup of C:\windows\\systemroot\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.


Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system.

Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To find out which driver is causing the issue, perform the following steps on the Windows Server 2008 R2 machine.

  1. Open a Command Prompt.
  2. Run the following commands to collect the VSS writer information.
    1. diskshadow /l c:\writeroutput.txt
    2. list writers detailed (wait for output to complete, this may take a few minutes)
    3. exit
  3. Open the output file "c:\writeroutput.txt" in notepad.
    1. Search the file for the string "windows\\" without the quotes.
  4. You should see a driver listed like the one below, this is the problematic driver.
    1. File List: Path = c:\windows\\systemroot\system32\drivers, Filespec = lsi_sas.sys
  5. Open Regedit and browse to the corresponding key.
    1. HKLM\System\CurrentControlSet\service\LSI_SAS
    2. Export a backup copy of the key.
    3. Verify the DWORD "Start" is set to a value of "3" in hexadecimal. (0x3 = Load on demand)
    4. Adjust key value if necessary.
  6. Test running the system state backup from the backup manager.
  7. Verify in the Windows Server Backup console that the system state is working properly.
  8. Reboot the server.

Additional Information:

This article only applies to Windows Server 2008 R2.

(30 vote(s))
Not helpful

Comments (0)