We help IT Professionals succeed at work.

Blue screen when admin logs on

Tomdp
Tomdp asked
on
Hi,

On my W2K server, I have the following problem:
When a member of the administrator group logs on, right after it shows "applying your preferences", the system hangs with a blue screen. The error message is "STOP ERROR 0x0000001E", the file causing this is ntoskrnl.exe . Curiously, this only happens for logins that are members of admin group, not for normal users. The server functions as MS Exchange 2000 server. The problem also occurs when I try to logon with terminal client. Any thoughts?
Comment
Watch Question

CERTIFIED EXPERT
Top Expert 2007

Commented:
Start using the NT resource and other tools to check the policies etc.

Step by Step Guide to Managing the Group Policy Feature Set
                                         http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/dsec/dsec_pol_zbgy.asp

"Troubleshooting Group Policy in Windows 2000"
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windows2000serv/support/tshootgp.asp


http://www.microsoft.com/TechNet/win2000/win2ksrv/adguide/addch11.asp
NTFRSUTL
http://www.microsoft.com/windows2000/downloads/tools/default.asp   utilities and downloads
http://www.microsoft.com/windows2000/techinfo/reskit/tools/default.asp resource kit tools


I hope this helps !
CERTIFIED EXPERT

Commented:
Tom, generally (and I say that tongue in cheek), stop 1E errors mean that something is out of date.

What service packs have been applied?

This admin group you speak of, is this "the" system admin group or another group with admin authority?

Your terminal client logon, is this being done externally as through RAS?

Dennis

Author

Commented:
Thanks for the suggestions so far. Some answers:

- I'm using SP2
- The admin grup is "the" admin group. Choosing the builtin Administrators group or the Domain Admin group doesn't seem to matter
- I've checked the KB already. So far no help. Particulary the fact that regular users can still log on seems to be something that is not adressed by the issues in the KB. I will continue to check of course
- Thanks for the sytem policie tips. I will check this. It will take some time, though.

Author

Commented:
last one:
terminal client logon from within the domain (terminal server in remote admin mode)
CERTIFIED EXPERT

Commented:
Check the policies issue before we go too much further.

Author

Commented:
Thanks for the tips so far. No luck yet with the policy checks. Any hints on specific things to look for?
By the way, something important I forgot to mention: I have two other servers in the domain (the active directory master and a RAS server) on which all users can log on fine. Doesn't this make a policy issue unlikely?
CERTIFIED EXPERT
Top Expert 2007

Commented:
It could mean that you need to check the replictions. You may have a corrupted policy on one server and OK on the rest.

I hope this helps !
CERTIFIED EXPERT

Commented:
Okay, let's go back to the beginning for a second. Has this problem existed since you setup the server, or did it begin after applying a service pack or hotfix?

Author

Commented:
For clarity I'll try to sum it up:
- The server is running W2K Server edition
- Service pack 2 is applied
- MS Exchange Server 2000 standard is installed
- no additional hotfixes
- the problem was not always there
- unfortunately it's unclear when "it" began. There's only one other (junior) admin and he swears he knows nothing about it. I was not present when it started. He claims to have logged out with a normal login and logged in with admin login when the blue screen first came. There had not been an admin for some weeks on that server.
- the problems do not occur on two other servers in the domain

hope it helps...

Commented:
Hi Tomdp,
- This question is still open and needs to be closed. If any of the comments above helped you, please accept it as an answer. If not please send an update about your issue so that the question can be finalised.

- **** PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER ****


- Experts, please feel free to add any comments before the question is closed.


- If no comment is added to this question, question can be deleted and points might very well be removed.


Thanks,


Pasha

Cleanup Volunteer

2 open questions:
12/29/02 http:Q_20438589.html "Designing pocketpc notes"
10/07/01 http:Q_20191864.html "Blue screen when admin logs on"
CERTIFIED EXPERT

Commented:
Recommend that the question be deleted.

Author

Commented:
Fixed the problem myself. Problem was caused after installation of CD burning software (Nero) which caused the system to hang. After removing the software (safe mode) because we figured it was causing the problem, some registry entry still remained active and loaded the faulty driver, therefore complicating the problem because it was not really obvious that not all of the soft had been removed. Will look up details if anyone is interested (driver provided by nero was suited for NT-not W2K if I remember correctly).
Points to stevenlewis because the answer was in there, somewhere
CERTIFIED EXPERT

Commented:
Well done Tom and thanks for remembering Steve!

Explore More ContentExplore courses, solutions, and other research materials related to this topic.