Migrating from Intel to AMD machine for Win2K3 Server = 0x7B Stop

Discussion in 'Server Setup' started by RCL, Feb 12, 2007.

  1. RCL

    RCL Guest

    Hi all

    For 4 months, on and off, I've been trying to move my x86 Windows 2003
    server from a dual Supermicro Intel board over to a new Asus M2N-E AMD
    AM2 Dual-Core AMD x64 motherboard. During November I had posted the first
    problem whereby the "Blue text" portion of the in-place re-install would lock
    up at saving "Configuration". I decided to disable the nVidia nForce-570
    raided drives and go with software RAID instead, as that has been super
    stable on my existing Supermicro configuration. That solved the lock-up
    problem.

    Hoping that things would go well after this, it did not. After the in-place
    re-install, I get the nasty 0x7b stop error:

    (0xF789e63C, 0xC0000034, 0x0, 0x0)

    It did not give the often-quoted "INACCESSIBLE_BOOT_DEVICE" error along with
    the stop error text.

    I have spent a good part of a month investigating this error up and down,
    from a distance with no luck, and hence I've come back to this forum for more
    professional advice.

    I initially wanted to blame the "nVidia nForce-570 SataRaid driver" since
    that was high on my hit list, based on how many times it came up in forum
    discussions. To ensure its proper installation, I used nLite and integrated
    the newest WHQL drivers, just as documented here:

    http://www.msfn.org/board/index.php?showtopic=50659

    To my mismay, that didn't change anything after the in-place re-install.

    During December I also gutted the source Win2K3 OS of drivers, services,
    etc. before bringing it over to the new machine, but that didn't help either
    (that did, however, help me migrate the same OS back to my Supermicro board a
    few years ago).

    Where may I go from here to push this problem further and determine which
    driver is leading to the boot problem? Seeing that the Win2K3 OS is now
    situated on a SATIA II drive (no RAID for now), it would make logical sense
    that it has to be related to the SATA driver. BUT, a clean install of WIN2K3
    off my original CD + the same WHQL nForce drivers has been running fine for
    months. This is the real oddity to me.

    Thanks for any suggestions. I will be keen to try anything and everything at
    this point to help pinpoint the start-up driver problem.
     
    RCL, Feb 12, 2007
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.