Log in Netowrk Server

  • Thread starter Thread starter Matt Powell
  • Start date Start date
M

Matt Powell

We are running Windows 2000 SBS server.
The server boots up with no problem and procedes to the
log in screen where users can then access their data on
the server.

The issue is when I try to log the into the server as
Adminsitrator or any other user I get a Blue Screen Crash.
The screen reads the following message.
Stop: 0x0000001e (0xc0000005, 0x8051d116, 0x00000000,
0x00001003
KMODE_Exception)Not_handled.

The server is a Dell Poweredge 2500, and I have spoken
with them and run hardware diagnostics, also spoken to a
nmumber of people who are just as confused as me!!

Any help would be gratefully appreciated.

Thanks

Matt
 
Matt Powell said:
We are running Windows 2000 SBS server.
The server boots up with no problem and procedes to the
log in screen where users can then access their data on
the server.

The issue is when I try to log the into the server as
Adminsitrator or any other user I get a Blue Screen Crash.
The screen reads the following message.
Stop: 0x0000001e (0xc0000005, 0x8051d116, 0x00000000,
0x00001003
KMODE_Exception)Not_handled.

The server is a Dell Poweredge 2500, and I have spoken
with them and run hardware diagnostics, also spoken to a
nmumber of people who are just as confused as me!!

Any help would be gratefully appreciated.

Thanks

Matt

You might have a corrupted version of userinit.exe.
Try replacing it via a networked PC. You should also
try Safe Mode - this will tell you if the crash is caused
by the various drivers that are active in normal mode
only.
 
Ok thanks I will try the USERINIT file first,
unfortunatley the blue screen crash also happens in all
modes of Safe Mode, which is why I am having trouble is
diagnosing the issue.

Matt
 
If you record the entire contents of the BSOD, it typically shows the last
things in memory before the crash. You can also have it save a "memory
dump" to disk. MS Product Support Services and help interpret the screen
and may be able to help recover the dump file from the drive. If it uses a
single drive (not RAID) then you can put the Drive into a good running
machine as a *slave* drive and copy/delete/add files to it then put it back
on the 2500. The Recovery Console can also be of help,...such as in
replacing the USERINIT file.
 
I believe the the problem is associated with no permission on systerm
partition for everyone. I had this problem and discovered it by analising
disks permissions.

thanks.


Phillip Windell said:
If you record the entire contents of the BSOD, it typically shows the last
things in memory before the crash. You can also have it save a "memory
dump" to disk. MS Product Support Services and help interpret the screen
and may be able to help recover the dump file from the drive. If it uses
a
single drive (not RAID) then you can put the Drive into a good running
machine as a *slave* drive and copy/delete/add files to it then put it
back
on the 2500. The Recovery Console can also be of help,...such as in
replacing the USERINIT file.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Ok thanks I will try the USERINIT file first,
unfortunatley the blue screen crash also happens in all
modes of Safe Mode, which is why I am having trouble is
diagnosing the issue.

Matt
 
Back
Top