Hi Y'all
I am sure you are in for some work now. first get SystemRescueCD ISO
from
'MAIN PAGE - SYSTEMRESCUECD' (
HTTP://SYSRESCCD.ORG/MAIN_PAGE)[/B] AND
BURN A COPY.
YOU HAVE GOT TO BE PATIENT AND GET THE DRIVE MOUNTED. ON THE DELL
INSPIRON 1720 I JUST DONE THE DRIVE IS SDA3 IT WILLBE THE LARGEST ONE.
SET THE BIOS TO BOOT FROM THE CD/DVD DRIVE.
IF YOU ARE NOT USED TO LINUX (LIKE ME) GET A BITDEFENDER RESCUE CD
WITH AUTO UPDATE VIRUS HERE
'BITDEFENDER RESCUE CD WITH AUTO UPDATE
VIRUS DEFINITION FEATURES' (http://tinyurl.com/d83klr)
This will scan your system (Takes a very long time) or cancel the scan
and work with the program.
Note !!!! This will not find the TxfLog folder Note that there is a
capitol "T" and a capitol "L" in the file. There is a file with that
name but it is in all lowercase letters. That is not the file to
remove.
These instructions are here also 'Workaround for STOP 0x0000C1F5 /
0xC1F5 / C1F5 / BSOD / CLFS.SYS / KB946084 - Delmartian Technologies'
(http://tinyurl.com/5wvrby)
There is a lot of info at the site above.
So, here's an overview of how I fixed my system. For part 1, 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".
Take a deep breath and recursively remove the $TxfLog file: "rm -rf
\$TxfLog". Once again, note that the $ is escaped with a backslash.
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.)
Type "cd /"
Type "umount /mnt/windows" to cleanly unmount your NTFS filesystem.
Type "init 6" to reboot, removing the CD when appropriate.
At this point, your system will no longer bluescreen, but it may not
boot, either. To fix that, here's part 2, for which you'll need a Vista
DVD.
Boot the Vista DVD and choose "Repair my computer".
When the system looks for Vista installations to repair, it probably
won't find any. Don't panic; just click Next.
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.
Remove the DVD at the appropriate time and allow the system to boot
from the hard drive.
If the system complains that it was not shut down properly, choose
"boot normally".
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.
That's it. With any luck at all you should have a bootable system
again.
The STOP 0x0000C1F5 bug is a nasty one, and I am confident that
Microsoft will release a hotfix and/or Windows Update for it soon. In
the meantime, if you are experiencing the problem, I hope this article
helps to get you running again.
Hope this gets it going for you! If you end up with another black
screen try here 'Error message when you start Windows Vista:
"The Windows Boot Configuration Data file is missing required
information"' (http://support.microsoft.com/kb/927391/en-us)
There is fix at Microsoft on the 0x0000C1F5. It is not final and you
have to apply for it and you will get 2 passwords to access it to run.
But what really sucks is you hav to have your system running to apply
the fix!!!!!
Nothing else from microsoft!!! except "we will fix it in Vista service
pack 2.
Ya Right
Good Luck
echostar
