I haven't had any problems like this With 2000 PRO or Server and i suspect
that the OS doesn't like something in your hardware.
I suspect it is  like NT4 in this regard.... if it likes your stuff then
it's great and if it doesn't then it is one battle after another. I have
been lucky...no battles like this yet.

What I have noticed about Win2K is that like NT when it first came out the
more hardware you throw at it the better it runs. Server has many more
tools then Workstation does. Drivers for old devices are a problem. I can't
get drivers for my SCSI scanner either and UMAX says they aren't going to
write them. You probably noticed that where as you can install NTWKS into
as little as a 75 meg directory ( I have done this) Win2K takes a least 500
meg.

People keep telling me they run games in Win2K just fine but I have had one
problem after another so now I boot into 98 if I want to play a game. Maybe
it is my Diamond TNT2 Ultra which doesn't have great driver support.

With all your problems I would suspect something more fundamental ...on the
motherboard or video card. Maybe a patch or a driver. I kept having
problems shutting down after I installed a Matrox G 200 in my Win2K Server.
Then I discovered I had to install a special VIA patch....problems went away.

Mark Rode
The NOSPIN Group


>   I've been a bit disappointed that my SCSI scanner (Tamarack 6000Ci)
>isn't supported (needs Adaptec EZ-SCSI), nor is my Intel QX3 USB
>Microscope (supports only Win98 -- c'mon Intel, grownups can enjoy
>this too!).  I guess I'll have to keep my 98SE system alive for a
>while longer, too.
>
>   But what I'm really looking for help on is crashes of the Win2K Pro
>box.  I've had several different recurring ones, and I'm hoping I'm
>not alone:
>
>1.  LSASS.EXE crashes when I log in.
>   This one seems to have gone away after a hard power down, but
>without knowing what caused it, I'm afraid it may return at any
>moment.
>
>2.  KMODE_EXCEPTION_NOT_HANDLED
>   I'm working my way through the knowledge base to try and close in
>on this one....
>
>3.  Machine total freeze/lockup, *possibly* associated with mouse
>movement
>    Are other people encountering these?  Are there tools I
>could/should be using to diagnose them?

        The NOSPIN Group provides a monthly newsletter with great
       tips, information and ideas: NOSPIN-L, The NOSPIN Magazine
           Visit our web site to signup: http://freepctech.com