unmountable_boot_volume

daygowop

daygowop

New Member
Critical Error- Unmountable_boot_volume!!!

hello everyone!
let me tell u guys a great story, i get into work at around 8 a.m. and immediately someone hands me their personal computer and wants me to fix a problem. i fix the problem but then proceed to clean up the machine because it had a lot of spyware and junk on it. i begin installing microsoft defender and run it when it is complete. i also run Ad-aware SE and spybot. i also configure her windows startup in "msconfig" and i am about 99.99999% sure that i did not deactivate anything that would affect the comp because i restarted the computer about 5 times and it was fine. but, i downloaded Divx and begun to install it and received a weird error message, i ignored it, uninstalled divx and then reinstalled it. it is now around 2 p.m.(as you can tell ive been working on this thing all day long), and then i get the infamous BSOD (blue screen of death), i am not sure if i rebooted the PC or if it just happened spontaneoulsy, but i am sure i had rebooted the PC twice after i configured the startup options. anywho, the BSOD said UNMOUNTABLE_BOOT_VOLUME. now, i am not too concerned on how to fix this problem because I am goin to try the chkdsk /r thing with the windows XP CD, but i am curious as to how this UNMOUNTABLE_BOOT_VOLUME message occured. was it something that i did? or was it simply the hard drive failing? or was it a virus? and if there are any other solutions to fixing the problem, feel free to post them!
thanks all!
Tony

P.S. my boss is rather upset with me! hahaha! any type of input is appreciated!
 
Last edited:
Straight from the KB:
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME

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.
 
Bad sectors or a corrupt boot.ini are likely causes.
It can also occur if 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.

Since it was previously working this isn't the case.
 
ok thats what i thought, but my boss tried to tell me that it was my fault for downloading windows defender. which could make sense, i think, because it is only a beta version, and sometimes beta versions of programs r known to do some crazy stuff. but still, i think that is highly unlikely that a microsoft product would do something like that.
 
Windows Defender is fine, I have it (and its predecessor Microsoft AntiSypware aka GIANT Antispyware)
 
You must log in or register to reply here.
Back
Top