Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BLUE SCREEN!!

Status
Not open for further replies.

Bgarret

IS-IT--Management
Joined
Apr 15, 2002
Messages
78
Location
US
I know this is pretty basic, buti need to know how to freeze the screen on Nt Server at the blue screen. where is says how many processors you have and the amount of memory. I have a .dll missing and before i can read the screen it flicks off..

Any Help??
 
Try using Crtl-S (it used to work under DOS) and Crtl-D to release.

Check your Event Log, it may have put the error in there too. New Zealand, a great place to live.
tokala@orcon.net.nz
 
Bgarret,

The easiest way is to turn off the automatic reboot. In the Control Panel double click the System icon and go to the "Startup/Shutdown" tab. Turn off the check box next to "Automatically reboot".

Whenever the system "blue screens" it will need to be manually rebooted. For this reason, you may want to turn this back on when you have fixed the problem (I prefer to leave it off on all my servers).

Also, as darrangl mentioned, on SP5 and later, there should be an event in the system log, with at least the first line of the crash dump.

Good Luck!!

Cheers,
Sam
 
Problem is there is a missnig dll file and it wont boot into windows. The blue screen im talking about is the one that is suppose to come up. It tell you the # of processors and the amount of memory before going to windows. On this screen it quickly tells me that it cannot find a path to a required dll.
 
The thing is.. When you find out what DLL is missing your gonna end up having to dig around for a copy and put it in the correct directory, which may be complicated by NTFS etc etc...

If I were you look at whats needed to get the system back up and running, quickly, rather than spending lots of time trouble shooting this issue, simply follow the well trodden path of recovering a broken system.

The most popular ways of fixing issues like this are;

1)
-Try booting with the "LAST KNOWN GOOD CONFIG" by hitting the "Space Bar" when prompted

2)
-Install NT4 into another directory eg c:\tempnt

-Install Service Pack and Backup software

-Restore C:\WINNT from a working backup


3)
-Boot from NT4 CD rom

-Add support for Array controller / SCSI controller using F6

-Upgrade or Repair the installation of NT found

-Upgrade will keep the existing registry, Repair will use either the Emergency Repair disk OR the contents of %systemroot%\repair

-If you dont have a recent ERD OR don't update the repair folder with rdisk then accounts etc may be lost



If you'd like any other help with this post a message


Best of Luck

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top