Unmountable boot volume error?????

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
hi folks,
have an e-machines 130, 900mhz Celeron running windows XP that has
suddenly developed an error that i can't seem to fix.

When you boot it up it come up with the standard screen saying that
windows did not start successfully and offers the options of "safe
mode", "safe mode with networking" and "Safe mode with command prompt"
and "last know good configuration". it also counts down to autostart in
normal mode.

However, whichever option you choose it then goes onto a blue screen
with the following message:

a problem has been detected and windows has been shut down to prevent
damage to your computer.
if this is the first time you have seen this error screen, restart your
computer. If this screen appears again follow these steps.
If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. if
you need to use safe mode to remove or disable components, restart your
computer, press F8 to select startup options, and then select safe mode.
Technical information:
*** STOP: 0x000000ED (0x80E91E30,0XC0000032,0X000000000,0X000000000)

I have never come across this sort of error before and i am a bit
baffled. Is it a hardware problem or something with windows? unmountable
boot volume suggests hard drive problems to me but seemed unlikely.

Any advice you can offer that would point me in the right direction
would be greatly appreciated

Re: Unmountable boot volume error?????

Quoted text here. Click to load it

Damaged File System 0XC0000032


Repair install.



Re: Unmountable boot volume error?????

Quoted text here. Click to load it

Makes much more sense to work out how it got damaged first.

Boot the Ultimate Boot CD 4 Win and post the Everest SMART report for the drive.

Or boot the Knoppix CD and use smartctl to post the SMART report.

Re: Unmountable boot volume error?????

c wrote:

Quoted text here. Click to load it

That's excessive and may have problems of it's own if the file system is
already corrupted (likely).

More effective is boot to recovery console

chkdsk /r

If *that* doesn't work then at least the file system is clean for a repair

Quoted text here. Click to load it

Site Timeline