Advanced boot problem with Windows XP

  • Thread starter Thread starter Christian Stange
  • Start date Start date
C

Christian Stange

This is a very special case, so I will spend some time describing my
needs, how I solve them, and the problem that has surfaced.

I'm running a datalab whit Windows/Linux dualboots. The point in my
setup, is that it should be possible for me from my server to decide
which OS the machines should boot into.

To do this,I've installed a network enabled GRUB (The GRand Unified
Bootloader) and configured it to ask my DHCP server for what boot
configuration I should use. So far so good.

In my initial testing, I didn't connect to my network; I loaded my
configuration file from local disc, and with this setup, both Linux and
Windows booted as they should. So the core configration scripts are
correct.

When I started to connect to the network, and with this setup, Windows
XP loops at the Windows XP logo.

I say it loops, because the animation continues forever. If I try to
boot in a different mode, I can se that it loads a lot of sys files and
stops after loading cpqagp.sys (or agpcpq.sys:-)) I believe that this is
the final step before the Kernel get started; but I'm unable to get this
properly confirmed. But it means that the boot sequense has been
transferred to NTLDR, it is able to read the disk, and it is able to
find its files.

My first suspicion was that Windows XP is unable to boot with an active
networks card. But that would make it impossible to PXE start Windows,
and I find that hard to believe. On the other side, there could be an
undocumented boot option that is used in those setups.

While I know that this isn't standard Windows problem, it seems to be a
serious bug, that is hard to catch. I would really appreciate all
information that can help me solve this problem and make my setup work
as intended.

regards
christian
 
I have done some more testing. The added information is put inn where
apropiate.

The windows version is Windows XP Pro build:2600 (SP1)

Christian said:
This is a very special case, so I will spend some time describing my
needs, how I solve them, and the problem that has surfaced.

I'm running a datalab with Windows/Linux dualboots. The point in my
setup, is that it should be possible for me from my server to decide
which OS the machines should boot into.

To do this,I've installed a network enabled GRUB (The GRand Unified
Bootloader) and configured it to ask my DHCP server for what boot
configuration I should use. So far so good.

In my initial testing, I didn't connect to my network; I loaded my
configuration file from local disc, and with this setup, both Linux and
Windows booted as they should. So the core configration scripts are
correct.
Click to expand...

If I ever the scripts to NOT to use the network, everything works again.
So it is triggered by the network settings.

When I started to connect to the network, and with this setup, Windows
XP loops at the Windows XP logo.
Click to expand...

(black screen, Windows XP Logo, rolling animation in the middel of the
screen)
I say it loops, because the animation continues forever.
Click to expand...

No, it doesnt. It ends up with a stop screen after some time;

STOP 0x0000007b (0xf7c9e640,0xc0000034,0x00000000,0x00000000)

If I start it in safe mode, the Stop message is slightly different :

STOP 0x0000007e (0x00000006,0x8067bf52,0xF7c9e704,0xf7c9e404)

Ive tried googling a bit around this, without getting anything I believe
I can use.

If I try to
boot in a different mode, I can se that it loads a lot of sys files and
stops after loading cpqagp.sys (or agpcpq.sys:-)) I believe that this is
the final step before the Kernel get started; but I'm unable to get this
properly confirmed. But it means that the boot sequense has been
transferred to NTLDR, it is able to read the disk, and it is able to
find its files.
Click to expand...

So far, Ive started it with /bootlog, /execute, /pcilock /debug and
/sos. Same stop message for everyone.

It seems that /bootlog doesnt work; I cant find a ntbtlog.txt that has
correct timestamp in regards to the boot test.
My first suspicion was that Windows XP is unable to boot with an active
networks card. But that would make it impossible to PXE start Windows,
and I find that hard to believe. On the other side, there could be an
undocumented boot option that is used in those setups.

While I know that this isn't standard Windows problem, it seems to be a
serious bug, that is hard to catch. I would really appreciate all
information that can help me solve this problem and make my setup work
as intended.

regards
christian
Click to expand...

Still hoping for some help.
 
The STOP 0x7b error is an inaccessible boot device
The STOP 0x7e error is a system thread exception

From this link: http://aumha.org/win5/kbestop.php the most common,
related problems seems to be bad device drivers.

Suggestions:
A) See if the STOP error refers to a particular file - if it's a device
driver for something on your system this should give you an ide of what
to update first!
1) Flash your BIOS to the latest version.
2) Visit Windows Update and get all the updates for your system
3) Update all of your motherboard drivers
4) Update your video drivers to the latest WHQL certified version
(either from nVidia or ATI - not from the card manufacturer's site -
they add stuff to the drivers that may cause problems.)
5) Update every other device on your system if the other steps don't
succeed.

Good Luck!

- John
 
Back
Top