Understanding PHYLock Errors
The following is a list of PHYLock errors, which are written to the Image for Windows log file, and the steps needed to resolve them. PHYLock Settings can be found by running Image for Windows and clicking the Settings button. If more information is required on PHYLock, please see the KB article Introduction to PHYLock.
Note: If you experience PHYLock errors, it's recommended to run chkdsk /f on the partition(s) to ensure the file system is clean. File system errors can cause multiple issues, including the caching of items that may not need cached.
PHYLock Error 0002h
A larger RAM Cache is needed. When a Disk Cache is being used, this error means that the RAM Cache has filled up. The RAM Cache is used to handle requests needing to be saved to the cache (intermediary buffer).
Increase the size of the RAM Cache Size (KB) option. The default size is 8192KB (8MB). It's recommended to increase the size by 1024KB - 2048KB (1MB - 2MB) at a time to see if it resolves the problem. For example, try an increase from 8192 to 10240. Do not use a value below 2048 for this setting. Also, see the note below. Additionally, if you have a Norton product installed, see PHYLock Errors when Norton LiveUpdate Runs.
PHYLock Error 0003h
PHYLock has insufficient space to save cache data. A larger cache is needed. When the Disk Cache is enabled this error refers to the Disk Cache. When the Disk Cache is disabled and only the RAM Cache is being used, this error refers to the RAM Cache (see Error 0002h, above).
Increase the size of the Disk Cache Size (MB) option. The default size is 600MB. It's recommended to increase the size by 512MB at a time to see if it resolves the problem. For example, try an increase from 600 to 1112. Also, see the note below.
PHYLock Error 0004h
The memory slider needs set to a higher value. Try setting the Memory slider one position to the right and see if it resolves the problem. You should only need to adjust this if you receive an error that says PHYLock out of memory or cache space or PHYLock failed to cache changes and you've already substantially increased the size of the RAM or Disk cache and it didn't solve the error.
PHYLock Error 0005h
This error indicates that a pending write to a location hasn't been completed before another write to the same location is requested. It can also be caused by something like a rootkit. In some cases, this error will show up several times, stick around for a few days, and then disappear. chkdsk should be run on the partition to ensure the file system is clean (e.g. chkdsk c: /f). A deep rootkit detection scan may also be necessary.
PHYLock Error 0007h
This error indicates a write error.
Bad sectors on the disk can cause this error. Check the disk for bad sectors (e.g. chkdsk c: /r). Running diagnostic software on the disk may also be helpful (most manufacturers provide utilities to check their drives).
Performing a major Windows upgrade or software updates that change the driver order can cause this error. To resolve this issue, uninstall PHYLock (a reboot is not necessary after uninstalling), reinstall PHYLock, then restart Windows.
PHYLock Error 0008h
This error indicates a read error.
Bad sectors on the disk can cause this error. Check the disk for bad sectors (e.g. chkdsk c: /r). Running diagnostic software on the disk may also be helpful (most manufacturers provide utilities to check their drives).
Note: For errors 2 and 3, you need to ensure you're not running some other operation that results in heavy disk activity (like defragging) while the backup is running since that can cause a lot of changes. Additionally, deleting a lot of data while the backup is running can cause problems as the backup file itself may use those sectors (they are no longer in use by the system, but the backup needs to keep track of them).