That happened my Dell Laptop - it meant the hard drive was fucked. Luckily it was in warranty so they sent someone out with a new one. They got me to do a few diagnostic checks before they sent someone out - they thought it might be just looking at the wrong drive letter. It wasn't though. Hope you've backed up your hard drive recently, I didn't.
As I say, in my case it was because the hard drive was fucked. I'm no expert but scanning that article and from what I googled when it happened to me this error message can be caused by other things too. Unfortunately, I don't know enough about it to help you further, sorry.
Or, you can do what I do and write your own cron job shell script that uses rsync to synchronise your stuff to a remote location (namely, my mate's NAS - he uses mine in reverse for the same thing).
In my experience there are two types of people in the world, those that make backups and those that just wish they made backups. If the worst comes to the worst and the drive is toast, I found this very useful:
Hi, is this disk on a machine that you can bootup still?
I'm guessing you can't because of the nature of the machine, but perhaps you have a way...
If you can access it (recovery disk, dual boot or move the physical disk to another machine being the most likely ways) and then get to a command prompt and run chkdsk /f on the affected drive.
I've had this happen before, something has become corrupt in the boot sector and the data is almost certainly fine, chkdsk is quite likely to resolve, though not certain.
To check if your hard disk is completely dead, download a Linux distribution -- Xubuntu would be a good choice (http://www.xubuntu.org/).
Download the iso file; you'll then need a program to create a disk image from this file to a CD-R. (Nero, which often comes with Windows, will do this. If not, go to filehippo.com and download DeepBurner for free.)
You can then boot from this CD without affecting your computer, assuming you have an optical drive. If you're lucky, you'll be able to explore your hard disk from the desktop and maybe recover something.
To echo what barndoorio said, try the recover disk again before anything else. It's possible the hard disk itself is OK but the boot sector or the FAT has become corrupted. It may not have booted because of your boot priorities in BIOS. When you get the very first loading screen upon turning on the computer, you have to press a key (often Del - it should say) to enter setup. From their make the CD drive the first boot device. Then insert the recovery disk, save and restart. If that doesn't work, you may well be screwed.
If you have XP, just boot from the original XP CD.
Then press 'R' and you should get a DOS prompt. Type "chkdsk /p" (without quotations) and smack enter. Then type "fixboot" (without quotations) and hit enter again. Type "Y" (without quotations) and enter. Then type "exit" (without quotations) and your PC will now reboot.
If that doesn't work then just boot from the CD, hit "R" and when you get into DOS type "chkdsk /r" and then enter.
For it to blue screen then it is reading something off the hard disk.
If the hard disk was completely toast, its would fail at the end of the POST, that is the black screen and all the writing you see for the first 10 seconds or so when you first switch on the machine.
The blue screen is more likely a software than a hardware error and can be down to corrupt boot files.
Could also be that it cannot read the boot files because that part of the Hard disk is buggered hence why Fartle correctly asks you to fix the boot files.
I don't do desktop support, but i have fixed a few failed servers and i would use fartle's command.
Comment