Jump to content
Posted 02 January 2010 - 04:00 PM
Posted 02 January 2010 - 04:11 PM
Posted 02 January 2010 - 04:43 PM
Posted 02 January 2010 - 05:24 PM
Recovery Console tutorial located here:
Posted 02 January 2010 - 08:47 PM
Posted 03 January 2010 - 06:10 AM
Do your remember the exact name of this particular fake anti-virus program?
A fake virus center kept popping up as a program on the computer
Posted 03 January 2010 - 01:02 PM
Posted 03 January 2010 - 06:02 PM
Posted 03 January 2010 - 08:36 PM
Please let us know what BSOD error message you see when doing the above.
Please get a look at the error message presented by the BSOD (blue screen of death).
Start tapping the F8 key after you press the ON button, and continue tapping until you are presented with the "Windows Advanced Options Menu" screen.
Use the UP/DOWN arrow keys to select "Disable automatic restart on system failure" and press the <ENTER> key.
Your system will attempt to restart normally, but when it crashes, it will not re-start. Instead, you will see a BSOD with error message.
Record the error message in full detail, and post in this thread.
Edited by AustrAlien, 03 January 2010 - 08:56 PM.
Posted 03 January 2010 - 10:02 PM
Posted 04 January 2010 - 06:24 AM
That's OK: chkdsk /f does not work from the Recovery Console (it only works from within Windows). From the RC, use chkdsk /p to do the same job.
The only command that would not work was "CHKDSK /F"
A problem occurred within a read or write to a FAT16 or FAT32 file system drive. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of FASTFAT.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions
Posted 04 January 2010 - 07:49 AM
remain unclear about whether you have actually run chkdsk /r
This is a 5 stage process, and will take a little time (in some cases, a lot of time). It will scan the hard drive surface and attempt to fix errors as well as fix file system errors (it includes the functions of chkdsk /p)
Rather than attempt to predict how long CHKDSK will take to run for a given volume on a given hardware platform, suffice to say that it can take anywhere from a few seconds to several days -- depending on your specific situation.
Posted 04 January 2010 - 02:58 PM
Posted 05 January 2010 - 01:47 AM
The problem lies within a "FAT16 or FAT32 file system drive", which is a little unusual, in that I would be expecting your Windows system to be on an NTFS file system drive. How many hard disk drives are connected? What partitions (drives) are present on those HDDs? What file system is employed on each of those drives?
A problem occurred within a read or write to a FAT16 or FAT32 file system drive.
Posted 05 January 2010 - 08:38 PM
Edited by EvanTheMagician, 05 January 2010 - 09:17 PM.
0 members, 0 guests, 0 anonymous users