BSOD problems with W2K sp4 and Network

[stfaprc]

When starting in regular mode, the splash screen shows but then is followed by a BSOD with
Stop Code:0x0000001E
KMODE_EXCEPTION_NOT_HANDLED message.

Changing keyboard did not help.

VGA Mode does work IF the network cable is not plugged into the NIC . However, once the login is done and one plugs in the cable, W2K reports that connection made but then goes into that BSOD.

This occurs with both the builtin Intel NIC and a new NetGear PCI NIC. Makes no difference if the builtin NIC is disabled or uninstalled.

I even uninstalled the microsoft client and tcp/ip drivers from the built-in NIC and it still gives the BSOD when booting up normally.

Next guess: i'll try disabling the online NIC via the BIOS

message changed, now it is:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP

I changed the RAM but still same message

I re-enabled the onboard NIC , started up in VGA mode,
reinstalled the IP stack, filled in the IP addresses
and then 3 seconds after I finished that - BSOD.

But this time with a different message:
STOP 0x0000001E (0xC0000005 0x00000000 0x00000000)

still no mention of any subsystem

A Linux Live CD had no issue, nor did an XP sp1 install.

There was a strange problem of the user losing the DNS entry which required typing the DNS backin and rebooting.

any ideas ?

 

[wolluf]

I'd try a repair reinstall:-

http://support.microsoft.com/default.aspx?scid=kb;en-us;292175&Product=win2000

 

[stfaprc]

i suppose i will have to try it .

I do have mini-dumps available from the failed startups,
as well as a DrWatson user.dmp (that i did not know about) that seems to have occured when the problems started up .

Is there a utility that would be able to clue me in as to what the problems are by using either of them?

 

[wolluf]

I've never had much joy trying to diagnose stop codes (or mini-dumps) - either from MSKB or elsewhere. In my experience its just a waste of time - a repair reinstall is easy enough to try, just takes same sort of time as install. It doesn't always cure the problem - but the fact you say you've done an XP install (complete?) gives confidence the hardware is ok, and its the 2k installation that's corrupted - and it usually cures those situations. If it fails, I'd just back up, wipe the drive and do a clean install.

 

[stfaprc]

wow, I did the reinstall of W2K and the same results - if anything the matter got worst.
The system would boot up after I got rid of the video driver, but it did so with the NIC disabled. Each time I enabled the NIC - boom - restart. not even a BSOD.

 

[wolluf]

Did xp really install ok (and run) with that NIC?
Have you tried a clean install of 2k yet?

 

[stfaprc]

yepp, XP really installed quite nicely.
No point in doing a clean install of W2K as we really were trying to save the information from the persons login.

A little further information:
upon the "repair" installation the NIC did take the IP addressing except for the gateway. When I entered a gateway address the pc rebooted, then kept the gateway address in its profile but stopped sending any packets anywhere.

Another oddity is that spoolsvcs kept on trying to connect to 85.255.113.142 DNS


We have decide to give up. User is using XP on that pc until we get a new pc in.

 

[rampeace]

My pc had the exactly the same symptoms as stfaprc pc. I tried a new NIC card, updating drivers, windows repair but none of them work. So last option was a clean install and it worked. Thank you for your advice.