win2k continuous rebooting on startup after sp4 install

[Guest]

I am having the same problem as others, ever since I
installed SP4, I have continuous rebooting on startup.
Unfortunately, I did not back up the files when I
installed SP4, so I can not uninstall.

I replaced winsrv.dll with a copy from my laptop, which is
working fine,but it had no apparent effect.

I followed some advice from this group and disabled Auto
Restart. I recieved the following blue screen error
message:

*** STOP: 0x00000050
(0XF000FF53,0X00000000,0XF83365C1,0X00000002)

*** Address F83365C1 base at F832B000, DateStamp 3ef274ef -
i81xdnt5.dll

Beginning dump of physical memory
Physical memory dump complete. Contact your system
administrator or technical support group.


If you have any idea how I can solve this, please advise.
I can boot in safe mode, so I can make changes.

Post reply here or email me at michaelATserv-airDOTcom

Thanks

 

[Gregg]

I have the exact same problem, and not on one computer, on different
computers, with different chipsets.
Now, I have Not for Retial or OEM Distribution copies of win2000, I'm
wondering if that's the problem.
When Service Pack3 came out, I installed it, and it went through the
continous reboot. I uninstalled it, and it worked fine. I figured, what
the hell, I'll wait till the next service pack. When SP4 came out, I
installed it, and wouldn't you know it, same thing, continuous reboot cycle.
I then thought maybe it was my athlon chipset, so I had an old intel
computer, and installed win2000 server on it, again, it was the not for
retail version you got from Microsoft with the Microsoft Hot Kit.
Is that the problem, you can not upgrade the hot kit version any more than
SP2?
Any thoughts on this would be appreciated.

 

[Adrian Ochoa]

Please see my post and let me know if you have tried any
of the steps since you are able to get into safe mode.

Were you able to get into safe before you replaced the
DLL??

Please get back to me.

Adrian

 

[Guest]

We have had 3 compaqs with the same problem. we are running it unattended through a script, not using SUS.

If you run the w2k repair twice it seems to fix it after the fact. Still looking for the cause though.