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

Article translations Article translations
Article ID: 970101 - View products that this article applies to.
Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.
Expand all | Collapse all
Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.


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

 

0x0000C1F5

Cause



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.

Resolution



To resolve this issue the corrupted file needs to be repaired. 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.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 970101 - Last Review: June 10, 2011 - Revision: 1.1
APPLIES TO
  • Windows Vista Starter
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Ultimate
  • Windows Vista Service Pack 1
Keywords: 
kbrapidpub kbnomt KB970101

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com