You are here:Home»KB»PC»Windows Family»Windows Vista»How to work around Stop Error 0x0000C1F5 on a Windows Vista-based computer
Saturday, 26 November 2011 15:07

How to work around Stop Error 0x0000C1F5 on a Windows Vista-based computer

Written by

When you start a Windows Vista-based computer, you may receive the following Stop error message on a blue screen:

0x0000C1F5

This issue can occur if the system file $TxfLog file has become corrupted. The Common Log File System (Clfs.sys) driver does not fix the $TxfLog file when the file becomes corrupted. In addition to the Stop error message, Windows Vista may not start until the offending disk is removed or repaired.

To resolve this issue the corrupted file needs to be repaired.


Solution 1:

This can be accomplished by booting to an installation disk that has the ability to self heal this type of issue. This can be done with a Windows 7 Beta installation disk. To recover a Windows Vista volume with Stop Error 0x0000C1F5 without data loss, perform the following steps:

  1. Obtain a Windows 7 Beta or later Windows 7 installation disk
  2. Insert the disk into the disk drive and boot from this Windows 7 Beta installation disk

    Note: Once booted, cancel out the Windows7 setup. Do not install Windows 7.
     
  3. Once the system has booted successfully, remove the Windows 7 Beta installation disk and reboot the computer from the hard drive.

Note: The Windows 7 Beta installation disk includes self-healing code that resets the corrupted $TxF RM log file, therefore the problematic volume should be recovered by simply booting from the Windows 7 Beta installation disk.

Solution 2:

If solution 1 fails and gives you the same error even when you boot of the OS bootable media your only course of action is the following which will fix the probloem in all cases but has an extra step

  1. remove the offending harddrive
  2. attach it to a working windows PC, Vista or Windows 7 is prefered via a USB adapter (other mconnection methods might work). Connect it when windows is booted and running
  3. you should see that you can see the files on the disk (might not be able to in all cases)
  4. chkdsk the faulty partition / harddrive. i would check the whole disk while i was at it but most likely not required
  5. chkdsk should find errors and repair them
  6. done
Read 1811 times Last modified on Saturday, 26 November 2011 15:22