Doman2006-08-09 04:20:17
This is crashing my friend's computer. How do I help him fix it?
A problem has been detected and windows has been shut down to prevent damage to your computer. UNMOUNTABLE_BOOT_VOLUME
if this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or softwar is properly installed. If this is a new installation, ask your hardwore or software manufactrurer for any windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disblae BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable compnents, restart your computer, press F8 to select Advance Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: OxOOOOOOED (Ox823EOCO8, OxCOOOOO9C, OxOOOOOOOO, OxOOOOOOOO)
Please and Thanks
A problem has been detected and windows has been shut down to prevent damage to your computer. UNMOUNTABLE_BOOT_VOLUME
if this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or softwar is properly installed. If this is a new installation, ask your hardwore or software manufactrurer for any windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disblae BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable compnents, restart your computer, press F8 to select Advance Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: OxOOOOOOED (Ox823EOCO8, OxCOOOOO9C, OxOOOOOOOO, OxOOOOOOOO)
Please and Thanks
Unknown2006-08-09 04:40:36
I've seen this error before, but I can't recall if it was because the fan on my video card broke, and it overheated after about 30 seconds, or because the hard drive got rather damaged and needed replacing.
Either way, I fairly certain it's a hardware problem. If he installed any new hardware recently try taking it back out. Other wise, if you know enough about computers, I would recommend just trouble shooting by swapping out each part available and see when it works.
Unless someone knows exactly what it means. That would save you the trouble and potential damage of taking pieces out.
Either way, I fairly certain it's a hardware problem. If he installed any new hardware recently try taking it back out. Other wise, if you know enough about computers, I would recommend just trouble shooting by swapping out each part available and see when it works.
Unless someone knows exactly what it means. That would save you the trouble and potential damage of taking pieces out.
Unknown2006-08-09 08:42:32
BUY A MAC!
Unknown2006-08-09 10:52:28
Its actually a UDMA error. If he hasn't changed the hardware recently, or hasn't touched the BIOS recently, and it used to work, then the Hard Drive is dead/dieing.
One thing to try is to boot into the recovery console from the CD and run
chksdk /r
see if that helps if not, its definitely because of an actual hardware failure in the HD and not just an unlucky corruption of the filesystem.
I am actually pretty doubtful that it is a corrupt filesystem, because the second hex address would be 0xC0000032
If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
actually, I have a question for you, is it ALWAYS an 0x000000ED or is it sometimes a 0x0000007B?
Also, is the person on the latest fixpack, as their used to be an error with disk caching in windows XP that would cause this error.
One thing to try is to boot into the recovery console from the CD and run
chksdk /r
see if that helps if not, its definitely because of an actual hardware failure in the HD and not just an unlucky corruption of the filesystem.
I am actually pretty doubtful that it is a corrupt filesystem, because the second hex address would be 0xC0000032
If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
actually, I have a question for you, is it ALWAYS an 0x000000ED or is it sometimes a 0x0000007B?
Also, is the person on the latest fixpack, as their used to be an error with disk caching in windows XP that would cause this error.
Mirk2006-08-09 13:18:56
QUOTE(Ytraelux @ Aug 9 2006, 03:42 AM) 317030
BUY A MAC!
Contrary to popular belief, macs do crash.
Shamarah2006-08-09 14:52:44
QUOTE(Mirk @ Aug 9 2006, 09:18 AM) 317077
Contrary to popular belief, macs do crash.
A lot.
Unknown2006-08-09 15:53:59
Not as much as other computers
And their prettier. And almost everything in Vista was already there in Mac OS X Tiger. AND now that Apple's announced their next system, I really wouldn't be surprised if M$ delayed it again
And their prettier. And almost everything in Vista was already there in Mac OS X Tiger. AND now that Apple's announced their next system, I really wouldn't be surprised if M$ delayed it again
Unknown2006-08-09 16:52:37
QUOTE(Ytraelux @ Aug 9 2006, 04:53 PM) 317105
Not as much as other computers
My linux server has NEVER crashed. My XP machine has crashed maybe once.
Mac users really need to get a clue about the real world
Pretty != Better
The fact that I get more power for 1/10th the price is my big reason for never buying macs.
Macs are for Artists, PCs are for Gamers/Developers its just the way it is.
Unknown2006-08-09 17:00:14
Tell game develpers to give a damn about Macs and that will change.
Unknown2006-08-09 18:12:39
I have no respect for Mac after I witnessed the stupidity of the first generation I-Mac. There was no eject button for the cd drive. You had to drag the icon to the trash. If you happened to forget, or it got shut off by someone else, you couldn't reboot the computer with the CD in the drive, and had to get a frick'n paper clip to hit the tiny little eject nub thing that was set back inside a tiny little hole for some obscene reason.
I just shook my head and walked away.
I just shook my head and walked away.
Unknown2006-08-09 18:25:30
QUOTE(Ytraelux @ Aug 9 2006, 06:00 PM) 317121
Tell game develpers to give a damn about Macs and that will change.
It doesn't work that way...you ahve to convince everyone to buy Macs and then when they have a 70% market share more games will be developed for it.
Anyway I am trying to help someone fix his problem...bloody Mac fanboys hijacking everything.