Fix error

Most of people attributing this issue to a bad Vista SP1 update or patch, and it seem that the people who have this problem are increasing more and more.
A short description of why this error can appear, is that Windows Vista support atomic transactions to NTFS file using Transactional NTFS component, and the system use this component to make easier the work for application developers and administrators, when they writing file output routines. The log file thus generated while using TxF is called $TxfLog file. If $TxfLog file suffers inconsistencies, it is supposed to be fixed by Clfs.sys driver (Common Log File System driver).
However, if it fails to correct, your system becomes unbootable displaying some errors on blue screen. Such situations might force you to reformat the hard disk and restore lost data from the previous backup.

The above error occurs if both of the following conditions are true:

• $TxfLog file is corrupted
• Clfs.sys driver (Common Log File System driver) fails to fix $TxfLog file corruption
• Common Log File System or CLFS is the logging system used by Windows for creating high-performance transaction logs. It is accessed by both user-mode and kernel-mode applications. Its driver file is termed as Clfs.sys.

To fix this error you can follow one of these methods:

Method 1

• If you have installed more than one hard disk into the system, you should simply remove the disk on which the $TxfLog file is damaged and doesn’t contain Windows Vista.
• In case you are using only one disk in your system, you can restart the system using an earlier operating system (like Windows XP) installation disc and use it reformat the hard disk to reinstall Windows Vista. You should restore your lost data from your previous backup.
Sometimes, backup fails to give required results because of reasons like interruption while taking backup, not regularly updating it and more. In such cases, data recovery applications come as rescue. This Data Recovery Software use powerful scanning algorithms to analyze the media for lost data and restore it at a safe location.

Method 2

You can fix the problem by accessing the disk using an operating system that doesn’t depend upon Windows file systems (e.g. Linux).

To make operations below, you should have a sysadmin tools like SystemRescueCD. This is a Linux-based live destroy that has all sorts of diagnostic and repair goodies on it. I figured that if I booted the SystemRescueCD disk, I might be able to diagnose, and maybe even repair, the problem.

Download SystemRescueCD, burn a copy, and add it to your sysadmin bag of tricks.

Part 1

Info: You need a SystemRescueCD disc. Don’t forget that Linux commands are case-sensitive, so pay careful attention to upper and lower case letters and spaces between items on the command line. Also note that several of these file names contain dollar signs ($), and the $ must be escaped from interpretation by the shell by preceding it immediately with a backslash (\), e.g. “\$foo” when referring to a file named $foo.
1. Boot the SystemRescueCD disc, answering any localization questions as required, until you get to a shell prompt.
2. Mount your hard drive at /mnt/windows using ntfs-3g, e.g. “ntfs-3g /dev/sda1 /mnt/windows”. You may have to “ls /dev/hd*” or “ls /dev/sd*” or “fdisk -l” to figure out the correct device to mount. If you are using a RAID device for your root file system, run “dmraid -ay” to attempt to mount all available RAID file systems, then “ls /dev/mapper” and look for your device. Also, if the NTFS file system is corrupted (which it probably is if you are reading this post) you may have to add the “-o force” flag to the mount, e.g. “ntfs-3g /dev/sda1 /mnt/windows -o force”.
3. Verify that you have the correct file system mounted by “ls /mnt/windows”. You should see the content of “C:” or whatever is your boot drive in Windows… if you don’t, repeat step 2 until you mount the correct device.
4. Navigate to the first hidden folder: “cd /mnt/windows/\$Extend”. Note the backslash before the $; that is important as it keeps the command shell from interpreting the $ (it is really part of the file name).
5. Navigate to the second hidden folder: type “cd \$RmMetadata”. Once again, note that the $ is escaped with a backslash.
6. Type “ls”. Among the files/folders listed you should see “$TxfLog”.
7. Take a deep breath and recursively remove the $TxfLog file: “rm -rf \$TxfLog”. Once again, note that the $ is escaped with a backslash.
8. Use “ls” to verify that it has been deleted. (You should see the same listing as in Step 6 except the $TxfLog folder is now missing.)
9. Type “cd /”
10. Type “umount /mnt/windows” to cleanly unmount your NTFS filesystem.
11. Type “init 6″ to reboot, removing the CD when appropriate.

At this point, your systems will no longer blue screen, but it may not boot, either. To fix that, here’s part 2, for which you’ll need a Vista DVD.

Part 2

12. Boot the Vista DVD and choose “Repair my computer”.
13. When the system looks for Vista installations to repair, it probably won’t find any – click Next.
14. In the System Recovery Options list, choose Startup Repair. The system will process for a minute or two, then state that it needs to reboot to finish its repair. Allow it to reboot.
15. Remove the DVD at the appropriate time and allow the system to boot from the hard drive.
16. If the system complains that it was not shut down properly, choose “boot normally”.
17. You may have to repeat steps 12-16 up to five times to “convince” the system to rebuild itself. If the system gets “stuck” during the rebuild process for more than an hour or so, force it to reboot (hit the reset switch or power-cycle the system) and try again.

Fix Windows Vista 0×0000C1F5 error via articlebase and delmartian