Unmountable Boot Volume error

budfroggybudfroggy
edited May 2004 in Hardware
Alrighty,
As i boot up Win XP, i'm gettin an unmountable boot volume error blue screen... i've been having slight issues with my pc as of late with no sound on boot up.... I want to swap out my HD to make sure thats not the problem, but i dont have an available desktop...My computer is home-made (by my brother) and has an Assus motherboard, AMD Athlon Thunderbird... I've checked and rechecked connections, as that would be the obvious problem to me since its saying it cant find my HD (i think...)

spanks for your help..

Comments

  • budfroggybudfroggy
    edited May 2004
    update-
    I went into the setup menu, and the computer is recognizing my hardrive...

    I jsut put it into another computer, and it took a boot disk for it to boot up, however, i got another error screen while trying to boot up with safe mode and again with last known good config, but i got a blue screen, and i'm only getting technical information now about the error...no real title
    if it helps, this is what i reads :
    Technical Information:

    ***STOP: 0x0000007B (0xF895C640,0xC00000000,0x00000000)

    thanks again for help...im desperate. :banghead:
  • muddocktormuddocktor
    edited May 2004
    Go to your hard drive manufacturer's website and download their diagnostic utilities and run them on the hard drive. It sounds like you have an older computer and your hard drive might be getting errors.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    Here is a tip from Microsoft that will clue in the set of things that might be happening here:

    http://msdn.microsoft.com/embedded/community/tips/xp/stoperr7b/default.aspx

    Note, this is about an unsucessful install, but also explains what happens when you take a HD with an install on it and try to boot in a box that does nto have saem hardware as first box (in XP's case, this means same model motherboard and can mean same BIOS rev also).

    Thus, you can get this the way the update said caused it, without even having bad hardware, just bad drivers that mismatch actual hardware in place.

    This is one reason I have two boxes with same motherboard in both, and keep work data on FAT32 drives that are so similar that they can be physically swapped (with boxes off, cold-swapped) to carry data into othter box.

    Part of why Microsoft does not give a solution that addresses exactly what happened, is DRM. Only thing I can say, is do this only for work file recovery, do not do it for an XP O\S recovery. That scenario is deliberately being removed (and has largely already been removed) by designing XP and later to prevent backups from being used for piracy purposes.

    You can work in recovery console slowly to recover things this way with command line commands, but not boot XP unless the hardware swapped to is very similar to the hardware installed on.

    John D.
Sign In or Register to comment.