BSOD When i logon

You need to find the reason for BSOD.
Look at the error messages you receive and search the MS support site.

Before you jump into any experiments, take a full backup of your system.

You may try to reapply Service Pack 2 and Hotfixes. To do that, you would have to do it in unattended mode. With Win2kSP2, try the following:

Unpack win2ksp2.exe to some directory. You can do it from some PC on the network. The syntax is win2ksp2.exe -x. Choose a network share on your Exchange Server as destination folder. If you don't have suitable network share, you can create one using Computer Management Console/Shared Folders.
Once you have SP2 files unpacked, you should run a command (something like):
C:\Temp\W2K_SP2\i386\update\update.exe -uYou can add this command to Scheduled Tasks on your Exchange server.
Repeat this for Hotfixes as well.

If that doesn't help you may need to reinstall Windows 2000. I have not tried it for your scenario, but if you specify that you wish to install into same drive and directory, you will not loose your present settings. However, you should be able to restore from backup you made in first step.

Sometimes we get that problem here, but with workstations and they go into a constant reboot cycle. We believe it is caused by Virus DAT updates, (it only happens to some PC's on Thursday's, when DAT's are released). We need to start up in Safe mode, disable the Virus software under the system icon. Then restart the PC normally, then put the Virus software back in automatic. We only need to do this once on the PC and the problem doesn't come back ???
For what it is worth , hope it helps Dave,,

Hi,

The previous answer was right in that you need to know what it is thats causing the BSOD.

OK... a few things to look at...

Are there any error events in the event log?

What reason is mentioned in the BSOD? It could be "VMM" for a memory related problem or "VxD" for a device driver problem...

Does it BSOD straight away? Or after a few moments? Does it look like it *nearly* logged in?

Did it always do this? Did you install software and then have it start? Or perhaps some hardware?

Did you even change any settings before you last successfully looged out? For instance, you may have changed the screen resolution?

Lets us know some more so we can help you...

Cheers,
Tim.

Hello

When you have a Compaq server, the first thing to do is to:

1. Check compaq web site for any ROM upgrades and latest NTSSD. Sometimes they ship the server with a "version" of their firmware that can make dodgy things.

2. If you reallywant to get to the Root cause of your problem you need to analyze the memory dump. Before you analyze it, make sure you run the memory dump check. See MS technet for this.

3. Once we know that we have a good memory dump it would help a lot if we had a pstat, your eventlogs and a msinfo32 file.

4. Make the memory dump avalible on a ftp server and I will look at your memory dump to see what the root cause of your problem are.

5. If you are not interested in providing me with the memory dump I need to know the stop code (The first 4 lines of your memory dump)

6. What happends if you create a dummy user and then log in with this account on your server?

You need to be much more detailed before I can answer your question!
kmex