Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: stop: 0.0000007B during installation  (Read 6878 times)

0 Members and 1 Guest are viewing this topic.

spikedfox

    Topic Starter


    Rookie

    stop: 0.0000007B during installation
    « on: December 24, 2010, 03:44:30 PM »
    I always get a stop: 0.0000007B error messages when booting from the installation CD of Windows XP or XP 64.
    Usually, disabling AHCI fixes this issue, but not on this computer. I have no clue what else can be causing the problem.
    I switched 32 bit and 64 bit modes, tried both IDE and RAID modes instead of AHCI, loaded fail-safe defaults in the bios, updationg bios, without success.
    And Google does not seem to be of any more help...

    All I'm trying to do is access the recovery console in the installation CD to create a new bootloader as the current one is corrupted.

    System:
    MOBO: Gigabyte x58-USB3
    RAM: 12Gb DDR3 Corsair Dominator
    CPU: Intel i7 960
    Graphic card: Asus EAH6870

    I do not have a floppy drive.

    spikedfox

      Topic Starter


      Rookie

      Re: stop: 0.0000007B during installation
      « Reply #1 on: December 25, 2010, 10:42:39 AM »
      No one capable of helping me out?

      I have one more question, if I install a 32 bit OS on which I install a 64bit virtual machine (say, in VMware for example), will the 64bit OS virtual machine detect more than 4gb of ram?

      patio

      • Moderator


      • Genius
      • Maud' Dib
      • Thanked: 1769
        • Yes
      • Experience: Beginner
      • OS: Windows 7
      Re: stop: 0.0000007B during installation
      « Reply #2 on: December 25, 2010, 10:47:35 AM »
      From MSDN:

      Quote
      0x0000007B: INACCESSIBLE_BOOT_DEVICE
      (Click to consult the online MSDN article.)
      Windows lost access to the system partition or boot volume during the startup process. Typical causes: Installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.

      Your 2nd question is a bit unclear....if the machine is not 64bit capable you will not see 4G of RAM.
      " Anyone who goes to a psychiatrist should have his head examined. "

      spikedfox

        Topic Starter


        Rookie

        Re: stop: 0.0000007B during installation
        « Reply #3 on: December 25, 2010, 11:29:52 AM »
        The machine itself IS 64bit compatible... that is not the question. I just want to know if a 64bit virtual machine can reconise all ram even if it is working from a 32bit OS (windows XP pro in this case)

        As for your quote, that does not help me much. Alright if that's the problem, but how do I fix it?

        JJ 3000



          Egghead
        • Thanked: 237
        • Experience: Familiar
        • OS: Linux variant
        Re: stop: 0.0000007B during installation
        « Reply #4 on: December 25, 2010, 07:43:17 PM »
        All I'm trying to do is access the recovery console in the installation CD to create a new bootloader as the current one is corrupted.

        Download the XP recovery console here:
        http://www.thecomputerparamedic.com/files/rc.iso

        The machine itself IS 64bit compatible... that is not the question. I just want to know if a 64bit virtual machine can reconise all ram even if it is working from a 32bit OS

        no
        Save a Life!
        Adopt a homeless pet.
        http://www.petfinder.com/

        BC_Programmer


          Mastermind
        • Typing is no substitute for thinking.
        • Thanked: 1140
          • Yes
          • Yes
          • BC-Programming.com
        • Certifications: List
        • Computer: Specs
        • Experience: Beginner
        • OS: Windows 11
        Re: stop: 0.0000007B during installation
        « Reply #5 on: December 26, 2010, 08:46:33 PM »
        You generally cannot run a 64-bit guest OS under a 32-bit OS.  And when you can, it's hardware is virtualized. It's not going to be able to access parts of the hardware the Host OS can't.
        I was trying to dereference Null Pointers before it was cool.