Need help with friends computer, please.?
Question by heavenseyes98: Need help with friends computer, please.?
I will copy everything it says on her computer when she starts it up. It won’t let me hit F8 and start in safe mode or anything. Everytime I try to go to something different, it always comes back to this screen. It won’t let me go to command prompt to override like the directions say, etc. What else can I do to get around this or change BIOS settings. It will let me get into settings but what settings do I need to change? Please help…
“STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME” Error Message When You Restart Your Computer or Upgrade to Windows XP
View products that this article applies to.
Article ID : 297185
Last Review : May 7, 2007
Revision : 1.6
This article was previously published under Q297185
On This Page
SYMPTOMS
CAUSE
RESOLUTION
UDMA Controller
Damaged File System
STATUS
MORE INFORMATION
SYMPTOMS
When you first restart your computer during the upgrade to Windows XP or when you start Windows XP, you may receive the following error message, where aaaaaaaa, bbbbbbbb, cccccccc, and dddddddd are hexadecimal numbers that may vary:
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME
NOTE: If you receive this error message when you restart the computer for the first time during an upgrade to Windows XP, your original operating system still works correctly. In some cases, a message appears on the BIOS report screen that states that the wrong cable is in use, but you may not see this message on computers that have a fast startup time.
Back to the top
CAUSE
This behavior can occur if either of the following conditions is true: • Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true: • You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
• The basic input/output system (BIOS) settings are configured to force the faster UDMA modes.
• The file system is damaged and cannot be mounted.
Back to the top
RESOLUTION
To resolve this behavior, use the appropriate method.
Back to the top
UDMA Controller
If your computer uses a UDMA hard disk controller, use the following procedures: • Replace the 40-wire cable with an 80-wire UDMA cable.
• In the BIOS settings for your computer, load the ‘Fail-Safe’ default settings, and then reactivate the most frequently used options such as USB Support.
Back to the top
Damaged File System
If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged.
If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage.
To do this, use the following steps: 1. Start your computer with the Windows startup disks, or with the Windows CD-ROM if your computer can start from the CD-ROM drive.
2. When the Welcome to Setup screen appears, press R to select the repair option.
3. If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
4. Type the administrator password when you are prompted to do so.
NOTE: If no administrator password exists, press ENTER.
5. At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.
6. At the command prompt, type exit, and then press ENTER to restart your computer.For additional information about how to use the Recovery Console in Windows XP, click the article number below to view the article in the Microsoft Knowledge Base:
314058 (http://support.microsoft.com/kb/314058/EN-US/) Description of the Windows XP Recovery Console
If this procedure does not work, repeat it and use the fixboot command in step 5 instead of the chkdsk /r command.
Back to the top
STATUS
This behavior is by design.
Back to the top
MORE INFORMATION
The purpose of this behavior is to prevent potential data loss due to the use of an incorrect IDE cable for the faster UDMA modes or due to continued access to a drive on which the file system is damaged.
Note that a variety of issues can cause file system damage, from faulty hardware to software configuration problems or viruses. You can run Chkdsk /r at a command prompt to resolve the file system damage, but you may lose some data.
Back to the top
Best answer:
Answer by lchasser
The hard drive has an error in the MBR ( Master Boot Record )
Effectively the Hard Drive is not being recognized by the system and therefore you can’t boot the machine.
Some computer shops can bypass this problem by using (Gulp) a Linux Disk with a MBR recovery tool. Check with your local computer guru shop.
Sarge
Add your own answer in the comments!