Discussion Locked

System Reboots at Login PLZ HELP

0 helpful
147 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a NT Server that reboots 40 % of the time at the NT login Screen and 60 % of the time if you just leave it after you log in . Its not consistant but it always reboots in under 3 min but not always at a certin time (ex. not always at the 2 minmark.)I'm not sure what to do with it at this point I dont want to reinstall NT At this time the system is at a remote site and the staff their aren't able to reinstall. any idea's any files i could replace that might be causeing this problem?? Thanks in Advance

147 replies

by stuart.clark

From what you have described it sounds like it could be a thermal problem with the server. If the server itself is getting too hot this could cause it to reboot itself. other possible problems could be that the system hardware has been misconfigured. Hope this helps..

by Former member

The question was auto-closed by TechRepublic

by listas

Have you installed a new driver before this began to happen ?
Are you waiting to log in or you put your username and password just as the ctrl-alt-del salute appears ?
Can you go back to your previous installation ?
What happens if you leave the server without logging in ?
Hope this helps
Martin

by mwf

From the symptoms you describe, I lean towards a thermal problem. Typically a broken fan in the computer. However, it may be a memory leak that a program or service is causing. Check the performance counters for CPU and memory use if/when you can log in.

by dave

I had a problem similar to this last month. Are you running Norton Utilities on your server? The system will spontaneously reboot while running a Norton Utilities application. Are you running Microsoft Exchange Server 5.5, nternet Information Server 4.0, or Microsoft Transaction Server?
If you are running Norton Utilities with any of these, then you will experience random lockups and reboots.

This is a known problem with MS Exchange Server and Internet Information Server. You can apply specific hotfixes for Service Pack 3 to fix this problem. For more information, see the Microsoft article Q147222 at: http://www.microsoft.com/kb.

If you're running these programs, then this should fix your problem.

by Former member

The question was auto-closed by TechRepublic

by bleechack

You can check to see if you have a heat problem or an installation problem by plugging in an old hard disk you probably have laying around and installing NT to it. If you still have the problem after booting to the other disk, I would guess heat orvirus. If you no longer have the problem, you can pretty much figure that your NT installation is corrupted. Might try running winnt32.exe /b /u from the NT CD \i386 directory if this is the case.

by Former member

The question was auto-closed by TechRepublic

by rogued,mcse

More than likely it is a memory leak or a problem with overheating (broken fan) However, have you tried selecting last know good configuration at startup. Also, try booting from the ERD (Emergency Repair Disk)Other than that I'm afraid you are going tohave to take a little trip to the remote location. In that case don't forget your NT 4.0 CD with SP 4 or better. Also make sure a good backup is obtained through a remote machine. Hope this helps.

by Former member

The question was auto-closed by TechRepublic

by nitin

If it reboots without showing blue screen, it definitely thermal problem(are you using overclocked cpu?)
If it shows BS, it is 99% driver/services problem. Post more details

by Former member

The question was auto-closed by TechRepublic

by kahana

I had a similar problem a few weeks ago after replacing the driver on a scassi card and it turned out to be an irq problem between the matrox screen card to the scassi card.

by Former member

The question was auto-closed by TechRepublic

by hcmartin

If all the other answers have failed try replacing the power supply. You can hook in one temporarly for a test. Next check out the motherboard. A loose connection on any of the power cables/connectors or printed circuits can cause this.

by sakis samaras

well after all the above answeres i feel like there is no much i may say but this:
if you just are'nt able to get your hands to that server try to contact your local staff and ask them to boot from an old-good MS-DOS disks not to access any HD (it woulnd't be possible any way) just to find out it it's H/W problem. If it is the machine will reboot anyhow (It's likely thermal problem or a power supply problem)
In other hand (the DOS does not care a bit for IRQ conflicts exept if you call a specific programm to access this IRQ) if the computer seems to function OK that leads you to corrupted S/W install (unfortunalty you have to take the steps refered to the previus answere with win32.exe from CD or rescue disks)
Hope helps

by sgravelle

If there's heavy electrical equipment nearby or other signs of dirty power, such as flickering lights, add a power conditioner such as an APC line R 250. A UPS alone is not enough in a dirty power environment. Its purpose is to take over during power OUTAGES, but it will not shore up the power SAGS like a conditioner will.
Also, check very closely for any bent pins or other signs of shorting on all attached cables. If you don't see any bent pins, try replacing any SCSI cables just the same.
GoodLuck in any case.

by Former member

The question was auto-closed by TechRepublic

by chris

I had this problem once, and it was exactly what everyone else has been saying. The machine was just getting too hot and would reboot itself. I ended up adding another case fan to the box and I haven't had a problem since.

Hope this helps!!

by Former member

The question was auto-closed by TechRepublic

by gdanen

I have more questions than answers at this point. Which service pack are you running? What services are started that are not standard NT services (e.g. tape backup, virus scanning, etc.)? Have you recently changed hardware and/or drivers? Is the server on a reliable UPS? Have you checked temperature and humidity? How about static electricity? Is the server secured and away from user traffic?
I hope these questions help you to find the source of your problems. Good luck!

by barranco

Well, You do have a choice of answers, but before you get your hands to deep into a mess, check the CPU fan, make sure is turning and flowing at normal speed, and if your server is connected to a UPS, also check that it is functioning properly, at normalcharge and no faulty state.
Good Luck

by Former member

The question was auto-closed by TechRepublic

by ram

I had a similar problem with a server, but it was not a thermal problem. One of the SCSI Raid cards would reset the motherboard.
Once I replaced the card the machine was fine. When I put it in a test machine the same problem accured. Hope this helps.

by rindi1

It sounds like a driver problem. Did you install anything new before this startet happening? A new display driver or modem driver? Or did you install servicepack5? Can you boot in VGA mode? If yes, try to deinstall the last installations you made.
Ive had similar problems with a modem driver. If the modem was turned off during startup, the pc bootet ok. Service pack 5 also caused a similar effect, also together with the modem.

by aquarian

Two things:
- boot to a DOS disk. If it doesn't boot after 30 minutes, forget the thermal issue. It's still possible, but highly unlikely.

- this may take a few attempts at logging in, but change the setting "reboot on a critical STOP error". This is a setting in the system properties, don't remember exactly where. This will make the machine go to a "blue screen" and give you the offending error and last file accessed. If this is a video file, then check your IDE/SCSI drivers and video drivers, otherwise, check Microsoft's web site / technet for the error. Good luck :)

Oh, easiest way to get to that setting is to right click on My Computer, choose properties.

by Former member

The question was auto-closed by TechRepublic

by mkelley

I know you have a million answers at this point to look through, but I agree with m_frei, video cards can cause strange problems in NT servers, try to bring it up in VGA mode to eliminate that from the equation.

by Former member

The question was auto-closed by TechRepublic

by greg.ahler

After all the talk about thermal probs, I, too, feel that anything I say would be redundant. I do, however, have a temporary solution that you can use until the unit is in your reach. Tell the users at the remote location to run the server with the case off, and a small room fan pointed directly into it. It's not clean, but it keeps the air moving until you can visit to change out the fans.

by Former member

The question was auto-closed by TechRepublic

by jonbarnett

This a long shot.. and only applies if you have UPS attached. The UPS could be failing and powering off after several minutes. It could also be a commmunication issue with a smart-UPS. After all services are started, Powerchute could be sending acommand to restart.
This is easy to check in either case... bypass the UPS

by Former member

The question was auto-closed by TechRepublic

by gunslinger98

I have had this problem myself before, and the problem turned out to be a bad power supply not supplying voltage consistently, causing lockups occasionally but rebooting (often within minutes of bootup). Otherwise, it sounds like a heat issue (internal fans, or more likely chip fans). I hope this helps you out.

by lfe

I had a problem very similar to this on a server that was running the older version of the Gateway Service for Netware. I had to remove the gateway and reinstall it to solve the problem.

by Former member

The question was auto-closed by TechRepublic

by akmcmast

I have had a server do that with a thermal problem. The server would get hot and then just shut itself off. If it is a possible program conflict of some kind, you can always try the last known good hardware profile. It actually does work once in a while. Maybe cool off the computer or the room it is in for a couple of days and see if it still reboots on its own. If it does, then it is most likely not a thermal problem.
Good luck!

by Former member

The question was auto-closed by TechRepublic

by jkay

The problem I have with all the other answers is that they seem to ignore the fact that this only occurs when you logon and not when the machine is just sitting idle.

Go to some other machine (remote is fine) and logon with a userid/password thatmatch the administrator userid on the target host.

Then go into the event viewer and choose log/select computer

Enter \\ and the fully qualified domain name of the remote server (or its IP address).

Almost certainly there will be something in the event log about what failed.

Does this fail with ANY user that logs on or just some of them?

by Former member

The question was auto-closed by TechRepublic

by golgojake3

This should help you, I used to have the same problem, While im not sure this applys to you it might. Usualy the reason this occours is that to many programs are running at startup, have you installed any new software? Some programs i have installed have also caused this probrem (Nortion Utilities caused mine), try to uninstall the software (if youve installed any latley), this solves the problem 50% of the time. Other than that I have no clue on how to help, but try that, and mail me and tell me if it works.

by Former member

The question was auto-closed by TechRepublic

by tcoffman

I had an NT box do almost the same thing. It turned out that the CPU Fan had failed. I replaced the fan and had no more problems.

by Former member

The question was auto-closed by TechRepublic

by martin.vonrotz

Is it possible that you have installed an older version of a Virus Checker Software? I did have the same problems once with an older version of Mcafee. Another possibility is that you have changed to a different keyboard layout without having the correct files on the server. This will cause a BSOD as well.

Anyway, you should be able to see what driver is causing the problem on the BSOD.
Install a dummy NT on a different location on you server and then delete the corrupt driver on the original installation. You should be able to reboot to you original installation then and try to fix the problem.

by Former member

The question was auto-closed by TechRepublic

by pendletonrg

I'm coming into it late and I hate to step off the beaten path here, but one of your RAM chips could also be bad. One other note on heat, make sure you have all the covers over unused slots in the case, that will mess with cooling as well.

by Former member

The question was auto-closed by TechRepublic

by carloso

You may have a thermal or memory problem. Check for the obvious. Fans not working. Loose connections,cards and if possible swap your memory. Also do a "plain" boot up by a floppy disk and see if you pc reboots by itself.

by jmoore59

Since the Thermal aspect of this issue has been thoroughly covered. Let's try for something a little more complex.
You mention that the server Re-boots within 3 minutes of startup. since it doesn't seem to matter weather or not if you are logged in. I would think a look at some of the running services may be in order.
What services is this server running. E-Mail? DHCP? etc..
Try to get into Control Panel/Services and set most of the additional services in manual mode. This way they won't start automatically. Then, turn the services on 1 by 1, with plenty of time in between service starts, until you find the service that is re-booting the server.
Basically, what I am proposing is that you isolate the startup of services to locate the failed service.

I have an NT server that is running Netscape Messaging server 3.6 that always issues an error message about not starting everytime I reboot the server. However, The process always starts and runs correctly. Is there something wrong with it? No. It

by Former member

The question was auto-closed by TechRepublic

by ustutz

While this does not address your question at hand, it might help you in the future. Consider installing some form of remote administration solution. E.g., HP has their "Remote Assist Modem", which, ICW pcAnywhere, allows you to connect to the system consle via a dialin connection. That allows you to power cycle the server and watch the boot screen / BSOD remotely. That modem can also page you on system failures (including power outages).

by Former member

The question was auto-closed by TechRepublic

by bruce.torley

Have you tried to disable the SNMP service from starting? It is possible a rogue sNMP agent is causing this to happen.

by Former member

The question was auto-closed by TechRepublic

by spettit

We had a similar problem with two systems at my company. In the first instance it turned out to be a faulty system board. In the second, one of two 128MB SDRAM modules was bad. Once replaced everything was fine.

by Former member

The question was auto-closed by TechRepublic

by sameersana

hi ,

I think the problem is in your Motherboard or Ram. Just replace the RAM & then check. If the problem persists than all i can say is you have a faulty MOther board.

by Former member

The question was auto-closed by TechRepublic

by kbw

re-format all drives!!
re-install!
clean!
monitor!!!!!
repeat!!!!!!
record!!!!!!
back-up on hot swaps
like your job??move???resign??metacom??

by tickboy

Blame your predecessor. Actually, I would have to agree with half of the responses since I believe it MUST be Services related. Do your best to change all non-essential services to Manual startup then isolate the problematic one.

by Former member

The question was auto-closed by TechRepublic

by nbard

There were a couple of suggestions about booting to a DOS diskette to see if it is a overheating issue. I believe that is a good way to start. If that is OK and you haven't installed anything new ( which if it is a remote and they can't reinstall,you probably haven't), chek the date and time stamp on the winlogon.exe file. I know this sounds crazy, but I had an experience where the servers didn't reboot, but the desktop would disappear and the only time you could see it was after killing the winlogon.exe. After talking with Microsoft, they gave us a newer version of the file and we haven't had any problems since. Hope it helps.

by Former member

The question was auto-closed by TechRepublic

by jjoeclark

Its not heat if it happens after 2 minutes ,
Stop your guessing and get up there.
Signed
Management

by srunfola

I had a Windows workstation doing that. It turned out to be the Power Supply. The machine was getting to hot.
Hope this helps.

by mark.r.weisskopf

Hi

I gues you can see from the answers you've got so far that your symtoms could be caused by a plethora of possibilities. One thin that may help you isolate any of the software based causes ( i.e new dlls and/or drivers ) is to look ant the boot.ini switches that allow you to boot NT with vaying degrees of debugging capabilities. You could create various boot.ini files and send them to this remote site, and get the personel there to report their results.
Hope this helps.

Good luck
Mark

by mfr

Hi Jason,

Ok, you've had a lot of response to this question, so you may have already resolved it.

I had a problem whereby I logged in, more often than not, to NT then the server fell over, what I found it to be was a PROCESSOR problem, I called the vendor had another processor shipped out and no more problems.

I'm not sure if this had already been mentioned as I skip a lot of answers.

Good luck.
Gary.

by haissam

Jason,

Do you have the server configured for autoreboot after a stop error?
If so, I recommend that you take it off and enable memory dumping to be able to analyse the reasons why it's rebooting. If not let me know and we'll try to find a solution

Regards

by kcoupland

We had two servers that went down in our office, and replaced the fans, added fans and still had the same problem. Turned out the RAM was bad in one and in the otehr it wasn't all seated - problem fixed....

by royrubio

Had similar situation. I ran a hardware diagnostic and found out some problems in video card. However, had no time to replace it so I thought of applying SP5 with the hope that it will be handled. After SP5 was applied, the problem disappeared.

by wordmaster1

I have had similar problems due to several sources. The one not mentioned so far was a short in a power cable. Have the people at the source open the case and just wiggle the power wires while it is booting to see if this causes a reboot. Wires often come loose in the plastic plugs. They can also wiggle ribbon cables as I have seen bad cables cause the same thing. Bad memory and a bad processor are also likely causes

by cspadp

reapply the latest service pack. I had the exact same thing happen after i install SP5 and then did a basic install of my standard apps. the DP fixed it up immediately.

by fdb55

Have you looked at the possibility of a bad microswitch between the power supply and the MBD? I have seen this scenario played out before, with the resolution being the replacement of that pesky on/off button that is causing interruptions in continuity.

by mrushing

my .02. POWER SUPPLY OR HEAT. I WOULD REPLACE POWER SUPPLY AND TAKE THE CASE OFF AND POINT A FAN AT IT.

by nghtwolf

First check your power man. features in your bios settings. power man, and NT dont always seem to work hand in hand, and if your hardware is mixed, low brand of mother board, also make sure that the memory is seated firmly, also check to see what mghz your mem is and if your system supports it.

by nghtwolf

like the other proposed answers uninstall sp6, Then install sp 4, before installing any service pack that is i.e. new off the shelf you should wait about 2-3 months to see if there are any major bugs in the latest release of the serveice pack.

by zbrain75

I don't believe you necessarily have a thermal problem. I have a windows95 computer that I installed myself with a top quality MB, Intel P2, all quality parts. I had the same problem just this week. It had a lot of software on it and much of it would start from the registry. When I disabled my sound card software (a memory hog), the situation stabilized. I bought MacAfee Utilities, tried to repair registry, and it trashed my system. Your problem is probably memory or SW. Read reviews on utility programs, such as Norton or Symantic. Try to get a good utility program, do system checks, especially memory(ROM tests are not thorough). Stop SW packages from running at startup, one at a time and see if you can find any patterns. Good luck.

by ghary

1. re-blow the bios chip..
2. replace motherboard and see.
3. install service packs.
4. have a drink.
5. kick wall.
6. What other pereferals do you have on the system .. eg scanner , hard drives

hope this helps .. sorry if it dosent ...

have a good un ....

Greg

by catracho2k

Software or Hardware? If you did not install anything a day before this started to happen then it's Hardware.

Have you installed any new Hardware a day before this started happening?
1. NIC & SCSI cards: These cause systems to reboot in random basis. Like your case.

2. Video cards: These if not installed w/ the right drivers can cause a system to reboot. Modems do the same thing also, but i don't believe you have one on the MB.

But,
I strongly feel it's the POWER SUPPLY! 99.9%
Hope this helps.

by artkenney

My first guess would be a termal problem. A non-functioning CPU fan or other heat generating problem. If the CPU fan is working check the ventilation around the server...even with a fan if it doesn't have proper ventilation you could have a heat problem with tbe CPU or elsewhere on the motherboard. My bet is an overheated CPU though. Hope this helped.

by mark.peterson

I would think of a thermal problem. Have you asked the user to select the VGA mode startup? This is analogous to the safe mode in Win95/98.

by neverfearsmithishere

Does this server blue screen or just reboot?

If it just reboots, then it can be driver related. If RAS is installed, could be a IRQ conflict if using an internal modem with RAS.

If you are using PCANYWHERE, there is a fix for this on Symantec's site.

Need more info - SP LEVEL, services loaded, etc.

Not a thermal problem if it is always on, just reboots.

by bcros

I had this happen once on a machine that had been "ghosted" (drive duplication), and the answer was to a) change from domain to workgroup, b) delete server from server manager, c) wait 15 minutes, d) add server to domain, e) change from workgroup todomain. Just an idea. Good luck.

by pat.schmid

The chance of solving this problem long distance is nil. Problems like this a due to one of two things - a severly hosed NT installation or it is hardware. While thermal problems have been proposed, I had a very similar problem due to a bad memory bank - I would reboot when the blue screen was displayed, as the logon would dsplay, immediately after logon, or within a few minutes of logon.

It was a pain to determine the cause of te problem. First I had to rebuild my NT Server from scratchto prove the problem was independent of the software (if the problem occurs with a default installation and you nopw the CDs are good then the cause must be hardware). Then we ran the diagnostic tests for several days straight without finding anything.

Next we stripped the machine down - I mean removed harddrives and anything else that wasn't required to get back to the barebones minimum hardware required to boot to DOS. Then stepwise we added a peice back to the system and repeated our test. When we got to p

by liebenberg

Like everyone else is saying it could be a heat problem. The thing that I would like to add is unselect the "Reboot after critical stop error" from the startup/shutdown dialog box and see if it still happens. If that doesn't help I am 99% sure that it is heat. If it is heat try to bring down the CPU speed a bit. I have heard of pentium 3 600mhz that can only run at 550mhz because of this problem

by liebenberg

Install win98 on the first drive and format it with FAT32. Install Windows Nt on the second drive and format with NTFS. Mark win 98 drive as active. When wanting to work with NT mark that as active. Another way to do this maybe is to install NT. Create a user that has very secure password and give only that user the right to access the drive letter that you want to be hidden. This will work even better if the other people are connecting remotely as they will not be able to see anything if you don't share it.

by jshellshear

Jase, this is not an easy thing to answer immediately without more diagnosis. Where any changes made to the system that resulted in this condition ? Was it ever stable in the past ? Did you make an ERD disk ? Have you examined the event log for errors ? If you can provide any more information then we can probably resolve this in a day or two. I suggest though without further examination that this is probably a hardware related issue, probably related to either the hard drives or system board orperhaps the CPU. When the reboot occur does the screen simply go black and then reboots to Bios ? Do you have a faulty power supply ? How old is the PC ? Let me have some more pertinent info and I will assist you as best I can. Best Regards and Happy Xmas.

John.

by fsevena

One question I would have might amount to:
"How old's the system board?" Or more specifically "How old is the CMOS battery." Sometimes a failing CMOS battery will cause mysterious reboot problems which might be misinterpreted problem as a thermal or software crash. It is often easier to replace a CMOS battery than a hard drive or motherboard. (That would depend on the system, though.) I hope I have been of some assistance with your problem, & good luck!
Greg

by mr paulus

Working in Tech Support for a major computer vendor, I have seen this several times. Driver/service problems results in BSODs almost all the time. Furthermore, if this was the case, the time for the problem to occur would be the same, and occur every time.
I am affraid it is a thermal problem. But, replacing or adding internal cooling devices might not solve the problem, because the fail might be internal to one of the components. CPU problem is most likely, as we have seen this a lot in tech support. Otherwise, motherboard or memory are possible points of failure.
This is what you do:
Go on site, remove the cover, power on the server, examine the internal cooling devices. Add cooling by using an ordinary table fan. If problem vanishes,the original cooling devices does not operate as they should. If not, your CPU is more than likely defect. If possible, try another identical CPU from an other computer if possible.
If problem remains, you can try to remove one or more of your memory modules if possib

by mr paulus

...and here is the rest:
possible.
By now you would know the source of the problem. If you feel uncomfortable troubleshooting hardware like this, call your tech support and yell at them like most other people :-) Just make sure they bring a new motherboard, RAM as well as a new CPU.
Again, I see this on a weekly basis, and feel sure about my diag from the information available.
Good luck to you!

Cheers, Mr Paulus.

by blueleader

Primary suspect: overheating.

Power supply fan and CPU fan working correctly?
Is the CPU fan the correct model for your CPU (they have different speeds and powers), like, is it cooling the CPU enough?
You could use thermal grease between CPU case and fan also to reduce the heat.

by martin_louis

Hi,
I just had the same problem - it was like reproducing your case.
The problem was the power supply to the system.Check your source of power to the system.

Regards
Martin

by questng

Did you have this problem originally? There is either a hardware problem such as memory chips, power supply and others as everyone suspects. Or IRQ conflict and so on. Check to see if the hardware is in Microsoft's HCL (Hardware Compatibility List).

Good luck

by vze29tvd

I saw this same symptom, just once, yesterday on NT Workstation. I mapped a hard drive from one workstation to another. Then on the second workstation I started ie5setup by double-clicking on the file name in Explorer. Ie5setup tried to copy a number of files to the temp directory on the second computer. There was not enough space on the drive containing the temp directory to hold all the files, which caused a series of error messages on the second computer, and the first computer to rebootwith no warning or error messages.

by dennisjh

I have had this problem on servers and workstations throughout my client base. I have found in almost all of the cases it was a heat problem. In a few of the instances, it has been the CPU fan. However, it a more recent one it was the the power supply fan that had failed. The power supply was fine but the fan itself on the supply failed. Since this is a remote location, you may want to have someone check to feel if any air circulation is felt at the back of the server. It may be a longshot, but in these situations, it usually is. Good Luck.

Dennis

by sarunachalam

I had faced a similar problem and one of the reasons I found was that a new network driver was installed instead of the recommended network driver. In this case, the server used to keep booting up again and when we installed the correct network drivers for the NIC this problem stopped. You will have to identify this problem by a process of elimination and get to the root. Hope this helps you.