Fun. STOP 0xED: UNMOUNTABLE_BOOT_VOLUME
godzilla525
Western Pennsylvania Member
Last week I had to reboot my laptop after a rare 3D app crash* (Dell I8200), and almost instantly Windows XP came up with a BSoD displaying the message 'UNMOUNTABLE_BOOT_VOLUME.
*(This was a normal shutdown and reboot, windows was still functioning behind the framebuffer... all I had to do was wait and press Alt+E during shutdown to end the 3D program... saw the desktop after that, emptying out as usual, then the blue shutdown screen..)
Tried again, same thing. I went searching around, and many sites, including MS, say to load up the recovery console from the CD and run CHKDSK /R, and if that doesn't work, FIXBOOT. Fine. If I could just get that far . Tried that and it BSoD'd again, this time in NTFS.SYS. Subsequent attempts at this failed as well, this time hanging up while Windows was inspecting the disk. Repair Reinstall also fails for the same reason. Safe mode also fails.
I ran DFT on the drive (40GB Hitachi Travelstar, 5400RPM/8MB), and it did not find any errors with the unit at all.
I hurriedly ordered an external USB 2.0 2.5" drive case from Newegg, but it won't get here until sometime next week. I was hoping just to plug this into my other XP machine and CHKDSK it, hopefully being able to put the MS hamster back onto the wheel.
Fortunately, the Knoppix 3.3 Bootable Linux CD sees all my NTFS partitions just fine and I was able to copy all my data over the network to the other machine... at 2.2MB/sec. :shakehead
I'm hoping not to have to whip out the old DOS/Win98 boot floppy and trash the thing with FDISK in order to have XP use the disk again. I may end up zero-ing the drive out with DFT instead...
I'd rather not do that though since getting everything reinstalled and set up the way I need it would take days, I'd rather have a five-minute fix. Any suggestions?
...Yeah, it's pretty bad when an OS hoses one little thing enough that it renders the entire disk unusable to itself, but this is Microsoft and they NEVER THINK that ANY of their software will EVER malfunction. Idiots.
*(This was a normal shutdown and reboot, windows was still functioning behind the framebuffer... all I had to do was wait and press Alt+E during shutdown to end the 3D program... saw the desktop after that, emptying out as usual, then the blue shutdown screen..)
Tried again, same thing. I went searching around, and many sites, including MS, say to load up the recovery console from the CD and run CHKDSK /R, and if that doesn't work, FIXBOOT. Fine. If I could just get that far . Tried that and it BSoD'd again, this time in NTFS.SYS. Subsequent attempts at this failed as well, this time hanging up while Windows was inspecting the disk. Repair Reinstall also fails for the same reason. Safe mode also fails.
I ran DFT on the drive (40GB Hitachi Travelstar, 5400RPM/8MB), and it did not find any errors with the unit at all.
I hurriedly ordered an external USB 2.0 2.5" drive case from Newegg, but it won't get here until sometime next week. I was hoping just to plug this into my other XP machine and CHKDSK it, hopefully being able to put the MS hamster back onto the wheel.
Fortunately, the Knoppix 3.3 Bootable Linux CD sees all my NTFS partitions just fine and I was able to copy all my data over the network to the other machine... at 2.2MB/sec. :shakehead
I'm hoping not to have to whip out the old DOS/Win98 boot floppy and trash the thing with FDISK in order to have XP use the disk again. I may end up zero-ing the drive out with DFT instead...
I'd rather not do that though since getting everything reinstalled and set up the way I need it would take days, I'd rather have a five-minute fix. Any suggestions?
...Yeah, it's pretty bad when an OS hoses one little thing enough that it renders the entire disk unusable to itself, but this is Microsoft and they NEVER THINK that ANY of their software will EVER malfunction. Idiots.
0
Comments
might want to try the memery to
one of the two might have a loose connection
I found a site that has software and instructions on making a Bootable Windows CD (bootable as in desktop, not setup) that might allow me to fix it.
http://www.nu2.nu/pebuilder/
that bootable windows method (BartPE) also gives an NTFS.SYS BSoD.
Something with this file system is hosed so bad that it causes Microsoft's NTFS driver to go into the tank.
Also, BartPE boots and runs fine with HDD pulled.
I'm just going to wipe the disk and reinstall from scratch...
The odd part is that Windows and my data are on two different partitions, so my scheme of keeping things on separate partitions to prevent damage didn't exactly work.
Oh well...