Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
BSOD STOP Error 0x0000007B during text mode setup RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi everyone,

    Before replying in this thread, please make sure that you read the following thread all the way through so you will know the history of the issue.

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/84c9615b-918a-49bc-a8c2-48c87a5051f0/

    As you can see, I was able to get past the Error Code 18 problem by removing the floppy disk from the drive bay.

    When prompted by the installer, I press F6 to load my RAID controller drivers.  Before I am able to specify the controller driver on the floppy (currently out of the drive bay), WHS happily greets me with a BSOD STOP error 0x0000007B.  Basically, WHS is ignoring my request to specify my own drivers and tries to load the boot device all by itself.  I have tried pressing F6 once and I have tried pressing repeatedly and no difference in the results.

    Basic point, I need to specify my RAID drivers and WHS is not allowing me to do that.  Any ideas on how I can get WHS to respond to my F6 request?

    Thanks for your help,
    Brad
    Saturday, December 13, 2008 5:12 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Got this one resolved!

    Before I ever received the Error Code 18, I was trying to install with nLite so I could slipstream my RAID controller driver.  During the GUI portion (first phase) of setup, WHS still asked for the driver (even tho it was already slipstreamed).  I'm guessing because there is somewhat of a disconnect between WHS and Server 2003.  I used a floppy to load the driver for this controller (Silicon Image RAID 3112) and the drivers for my other controller (Promise TX4).  When WHS rebooted, I still had the floppy in the drive bay and this gave me the Error Code 18 from my previous thread.

    I thought perhaps I should just load the single Silicon Image RAID controller and worry about the promise controller after Windows installed.  Wrong, but I was just trying different things.  After I still received the Error Code 18 at text mode startup, I thought this didn't have any effect.  Well, it did because after I figured out to remove the floppy to get past the Error Code 18, I got this lovely STOP error.  I thought it was due to my Silicon Image RAID controller, but it was actually because the Promise TX4 PCI card was plugged in and Windows didn't have a driver for it.

    SOOOO....

    I removed the Promise PCI Card from the system, rebooted again, pressed F6 and BAM!  WHS asks me for my RAID controller driver as it dang well should! =)

    Now having seen the light, I go back to my nLite copy that I thought had failed me, used two different floppy disks to load the Silicon Image RAID controller driver and Promise TX4 SATA controller driver during the GUI portion of setup, removed the last floppy disk used from the drive bay before the reboot and whoopeee the unattended setup for WHS works like a charm.

    I post this solution because I hope and pray that it saves someone else the agony that I went through to get this to work.  Thanks to everyone for your desire to help me in my pursuit of running WHS on a RAID system drive.

    Brad

    • Marked as answer by Brad Wallace Saturday, December 13, 2008 7:19 PM
    Saturday, December 13, 2008 7:19 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    l00ker said:

    Hi everyone,

    Before replying in this thread, please make sure that you read the following thread all the way through so you will know the history of the issue.

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/84c9615b-918a-49bc-a8c2-48c87a5051f0/

    As you can see, I was able to get past the Error Code 18 problem by removing the floppy disk from the drive bay.

    When prompted by the installer, I press F6 to load my RAID controller drivers.  Before I am able to specify the controller driver on the floppy (currently out of the drive bay), WHS happily greets me with a BSOD STOP error 0x0000007B.  Basically, WHS is ignoring my request to specify my own drivers and tries to load the boot device all by itself.  I have tried pressing F6 once and I have tried pressing repeatedly and no difference in the results.

    Basic point, I need to specify my RAID drivers and WHS is not allowing me to do that.  Any ideas on how I can get WHS to respond to my F6 request?

    Thanks for your help,
    Brad


    Basically, keep trying. :)  The window is only there for a very small time and if you miss it, you get that error message.  (Or don't use RAID.)
    Saturday, December 13, 2008 5:42 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Brad,
    what kind of keyboard do you have connected?
    I have seen USB keyboards not being supported properly at Bios level (which would fit also to the text level setup of WHS).
    So you may try to check the Bios settings or attach a PS/2 keyboard, if possible.
    Is the floppy drive internal or external (USB)?

    And as I posted already in your other thread:
    Besides that, a chance to integrate the drivers could be to boot the machine from a Vista DVD, use it's command prompt under Computer Repair options and copy the inf file for the driver to the already copied Windows structure into C:\Windows\inf and the remaining driver files into C:\Windows\system32\drivers.
    (This method did work for me one time in a similar situation.) After that reinsert the WHS DVD and reboot.

    Best greetings from Germany
    Olaf

    • Marked as answer by Brad Wallace Saturday, December 13, 2008 7:19 PM
    • Unmarked as answer by Brad Wallace Saturday, December 13, 2008 7:19 PM
    Saturday, December 13, 2008 6:41 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Got this one resolved!

    Before I ever received the Error Code 18, I was trying to install with nLite so I could slipstream my RAID controller driver.  During the GUI portion (first phase) of setup, WHS still asked for the driver (even tho it was already slipstreamed).  I'm guessing because there is somewhat of a disconnect between WHS and Server 2003.  I used a floppy to load the driver for this controller (Silicon Image RAID 3112) and the drivers for my other controller (Promise TX4).  When WHS rebooted, I still had the floppy in the drive bay and this gave me the Error Code 18 from my previous thread.

    I thought perhaps I should just load the single Silicon Image RAID controller and worry about the promise controller after Windows installed.  Wrong, but I was just trying different things.  After I still received the Error Code 18 at text mode startup, I thought this didn't have any effect.  Well, it did because after I figured out to remove the floppy to get past the Error Code 18, I got this lovely STOP error.  I thought it was due to my Silicon Image RAID controller, but it was actually because the Promise TX4 PCI card was plugged in and Windows didn't have a driver for it.

    SOOOO....

    I removed the Promise PCI Card from the system, rebooted again, pressed F6 and BAM!  WHS asks me for my RAID controller driver as it dang well should! =)

    Now having seen the light, I go back to my nLite copy that I thought had failed me, used two different floppy disks to load the Silicon Image RAID controller driver and Promise TX4 SATA controller driver during the GUI portion of setup, removed the last floppy disk used from the drive bay before the reboot and whoopeee the unattended setup for WHS works like a charm.

    I post this solution because I hope and pray that it saves someone else the agony that I went through to get this to work.  Thanks to everyone for your desire to help me in my pursuit of running WHS on a RAID system drive.

    Brad

    • Marked as answer by Brad Wallace Saturday, December 13, 2008 7:19 PM
    Saturday, December 13, 2008 7:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    All those little secrets - like which cards you have in the system - make support in detail really hard.
    Good to hear, that you could solve your problem and thanks for sharing the experience.
    Best greetings from Germany
    Olaf
    Saturday, December 13, 2008 9:22 PM
    Moderator