?????

[Brown Hornet]

hey all,this is a bit long so bear with me this is the screen my brother's computer
show's when booting up after going through xp splash screen.

a problem has been detected and window's has been shut down
to prevent damage to your computer.

UNMOUNTABLE_BOOT_VOLUME

check to make sure any new hardware or software is properly
installed. if this is a new instalation ask your hardware/software
mfg.for any window's update you might need.
if problems continue disable or remove newly installed hardware/
software.disable bios memory options such as caching or shadowing.
if you need to use safe mode to remove or disable componets restart
press f8 to select advanced startup options,and then select safe mode.

technical information:

***stop: 0x000000ed(0x80e90cc0,0xc0000032,0x00000000,0x00000000)

i tried to get into safe mode but it brought me back to thius screen
any help would be great

[pam123]

Did this just drop on him from nowhere ?
From your post I assume you'd know if he had installed new hardware or software or if he was trying to install XP.
So, unplug the comp and take the sides off the case and check to make sure that everything is tightly installed and/or connected, the problem could be nothing more than bracket creep.
If all's right there go into the bios and 1. make sure everything is recognized correctly . 2. set the floppy to first in the boot order.
That last is because you're going to download a diagnostic from the HDD manufacturer's web site and save it to floppy. When you save and exit do it with the floppy in the drive so that the computer will boot from it.
Run the diagnostic and we can go on depending on what you find.

edit : The odd are that he needs a repair install of XP.
See info here : http://support.microsoft.com/default...NoWebContent=1

[Brown Hornet]

his computer is a pre-built i asked him if he had any disk's or floppy
that came with it and he said he had lost them.so what is the worse
case scenario with no disk's?

[pam123]

He gets to call customer service at whatever company he got the comp from and pay them whatever they want to charge for replacement disks.

[tacoeater]

i have a customer who has had this error twice during the last six months. the first time the chkdsk /r did not work but the fixboot did. the second time the computer came in the chkdsk /r got it up and running again. i never really was able to figure out what is causing this but i told her to be ready to replace her hard drive next time (i assumed it was a failing hard drive).

[Brown Hornet]

i figured it out,i used my brother's HD as a slave drive in my rig.seem's it was
full of trojan's did a good clean-up and it run's fine in his rig


thanx everyone