Windows 2000 keeps locking up

  • Thread starter Thread starter Joseph O'Brien
  • Start date Start date
J

Joseph O'Brien

I've been having trouble with a Windows 2000 box for a while now. It
always locks up (i.e., the screen freezes, does not respond to
keyboard input). There doesn't seem to be a pattern to it, other than
I can never run Windows for more than an hour, usually less. Also,
anytime I try to install software, it locks up.

I have performed the following test and actions to no avail:
Virus / Malware test (ran tests from two vendors -- it came up clean)
Chkdsk /r (from repair console -- it locks up if I try it from the desktop)
SMART test
memtest (from startup disk -- memory checks out)
heavy load test (from startup disk -- can't remember vendor -- ran for days)
In-place Windows 2000 upgrade
BIOS CMOS flash and upgrade
Added case fan, cleaned and reseated CPU heat sinks
Click to expand...
I thought I had it figured out when I was able to go for a long time
in safe mode, but as soon as I tried to install software, the same
thing happened.

Folks, I'm at a loss. Short of reformatting, can anyone else offer any
suggestions? I might replace the video and network card, just in case
there's a bad driver somewhere, but other than that, I'm about to give
up.

Thanks for any advice.

Joseph
 
Hi,

If it were mine, I would run a couple of routines off-line.
(You might want to do this with the cover off and a small fan blowing on
the case, just in case it is temperature related)

First,
You'll need your install CD
Start
Run.
"type" SFC /scannow
Once you get through with this, you will need to reinstall your SP4 and
rollup for SP4

If these work okay, Try putting your case back on and installing
software. I would stay off-line, until after you do this, just in case
you have gremlins.

If all is going okay, try running online and see if you have this start
happening again. If it does, you might consider running Highjack This,
SpyBot S&D, and AdawareSE. www.spychecker.com should have all these free
downloads. You might want to get them before you start anything and
install them, if the System File Checker frees you up to install
anything.

If you didn't have any luck with the freezing, I would try a parallel
install. To do this go into your BIOS and change the first boot device
to CD, and boot with you installation CD, using KB292175
http://support.microsoft.com/default.aspx?kbid=292175

Also KB306952 http://support.microsoft.com/default.aspx?kbid=306952
tells you what this does and does not do.

After this, you will need to reinstall your SP4, and SP4 rollup.

Sometimes these things will drive you bonkers.

good luck,
dc



| I've been having trouble with a Windows 2000 box for a while now. It
| always locks up (i.e., the screen freezes, does not respond to
| keyboard input). There doesn't seem to be a pattern to it, other than
| I can never run Windows for more than an hour, usually less. Also,
| anytime I try to install software, it locks up.
|
| I have performed the following test and actions to no avail:
|
| > Virus / Malware test (ran tests from two vendors -- it came up
clean)
| > Chkdsk /r (from repair console -- it locks up if I try it from the
desktop)
| > SMART test
| > memtest (from startup disk -- memory checks out)
| > heavy load test (from startup disk -- can't remember vendor -- ran
for days)
| > In-place Windows 2000 upgrade
| > BIOS CMOS flash and upgrade
| > Added case fan, cleaned and reseated CPU heat sinks
| I thought I had it figured out when I was able to go for a long time
| in safe mode, but as soon as I tried to install software, the same
| thing happened.
|
| Folks, I'm at a loss. Short of reformatting, can anyone else offer any
| suggestions? I might replace the video and network card, just in case
| there's a bad driver somewhere, but other than that, I'm about to give
| up.
|
| Thanks for any advice.
|
| Joseph
|
 
I misspoke.
Not a parallel install, a In-place Upgrade or Repair Install is what I
should have said.

sorry,
dc



| Hi,
|
| If it were mine, I would run a couple of routines off-line.
| (You might want to do this with the cover off and a small fan blowing
on
| the case, just in case it is temperature related)
|
| First,
| You'll need your install CD
| Start
| Run.
| "type" SFC /scannow
| Once you get through with this, you will need to reinstall your SP4
and
| rollup for SP4
|
| If these work okay, Try putting your case back on and installing
| software. I would stay off-line, until after you do this, just in case
| you have gremlins.
|
| If all is going okay, try running online and see if you have this
start
| happening again. If it does, you might consider running Highjack This,
| SpyBot S&D, and AdawareSE. www.spychecker.com should have all these
free
| downloads. You might want to get them before you start anything and
| install them, if the System File Checker frees you up to install
| anything.
|
| If you didn't have any luck with the freezing, I would try a parallel
| install. To do this go into your BIOS and change the first boot device
| to CD, and boot with you installation CD, using KB292175
| http://support.microsoft.com/default.aspx?kbid=292175
|
| Also KB306952 http://support.microsoft.com/default.aspx?kbid=306952
| tells you what this does and does not do.
|
| After this, you will need to reinstall your SP4, and SP4 rollup.
|
| Sometimes these things will drive you bonkers.
|
| good luck,
| dc
|
|
|
| | | I've been having trouble with a Windows 2000 box for a while now. It
| | always locks up (i.e., the screen freezes, does not respond to
| | keyboard input). There doesn't seem to be a pattern to it, other
than
| | I can never run Windows for more than an hour, usually less. Also,
| | anytime I try to install software, it locks up.
| |
| | I have performed the following test and actions to no avail:
| |
| | > Virus / Malware test (ran tests from two vendors -- it came up
| clean)
| | > Chkdsk /r (from repair console -- it locks up if I try it from the
| desktop)
| | > SMART test
| | > memtest (from startup disk -- memory checks out)
| | > heavy load test (from startup disk -- can't remember vendor -- ran
| for days)
| | > In-place Windows 2000 upgrade
| | > BIOS CMOS flash and upgrade
| | > Added case fan, cleaned and reseated CPU heat sinks
| | I thought I had it figured out when I was able to go for a long time
| | in safe mode, but as soon as I tried to install software, the same
| | thing happened.
| |
| | Folks, I'm at a loss. Short of reformatting, can anyone else offer
any
| | suggestions? I might replace the video and network card, just in
case
| | there's a bad driver somewhere, but other than that, I'm about to
give
| | up.
| |
| | Thanks for any advice.
| |
| | Joseph
| |
|
|
 
I think Newbie hit it, you have HEAT related problem. Just what it is is
anyone's guess but I'd start by blowing the dust out of the box! That is
something FEW people do and it can really get thick in there over time,
creating problems. In fact I just cleaned a friends computer. Her's had
not been cleaned in two years and the amount of dust, especially on the
CPU cooler, was astounding. What I do is blow it out with compressed air
from a small (5 gal.) tank. If you have a vacuum cleaner with a reverse
outlet for blowing air, use the crevice attachment to create a narrow
stream of air and blow the dust out of everything (outdoors with the
case opened of course). This cleaning is something everyone should do
yearly as regular maintenance.

If still no joy (and you are SURE *EVERYTHING* is clean, e.g. PS fan,
CPU cooler and fan, other heat sinks, memory chips etc) I'd run a memory
checker and check the systems memory integrity. MANY lockups as you
describe also result from failed/failing memory chip(s).
You can google for memory testers, MS also makes one and it is free.

Let us know how you make out!

Vic
___
 
Joseph,

What's the processor temperature in the BIOS when it locks up?
Click to expand...

You can't always rely on BIOS temperature readings. It's possible for
the die itself to heat up before any other sensors can see it. Without
knowing the exact CPU, it's hard to say how it's checked.

I once built a computer, and it would lock up during the Windows
install. After alot of experimenting, I figured out it was caused by
having a bit too much heat sink compound preventing the die from
transferring the heat to the heatsink efficiently. Once I thinned it
out, it worked fine. This was with an AMD CPU.

Also, fully verify that the CPU heatsink is properly mounted. See if any
other chips might have heatsinks and that they are getting airflow. This
also includes any cards, especially video cards. Make certain any video
card fans are actually working and, when powered off, spin more or less
freely (they will usually be 'bumpy' due to the magnets.)
 
Thanks to everyone for your advice. However, I believe I covered all
your suggestions in my original post. I have a temp. monitor running,
and I believe both processors remain at a reasonable temperature (I
can't remember exactly what this is, but it was low enough).

I did check the BIOS temp reading, but BIOS actually locks up as soon
as I enter the PC Health screen.
 
Thanks to everyone for your advice. However, I believe I covered all
your suggestions in my original post. I have a temp. monitor running,
and I believe both processors remain at a reasonable temperature (I
can't remember exactly what this is, but it was low enough).

I did check the BIOS temp reading, but BIOS actually locks up as soon
as I enter the PC Health screen.
Click to expand...


I think I figured it out. I want to put this out there for anyone else
having similar trouble.

The original problem was Windows 2000 frequently hanging (screen
frozen, network activity ceased). After multiple trips to the recovery
console, several in-place upgrades, and much pulling out of hair, I
still could not fix the problem. After a little more digging, I
realized that the problem might have to do with the on-board HighPoint
370 hard drive controller. The system board is an Abit VP6.

To fix the problem, I disabled the UDMA ATA-100 controller in the BIOS
(at this point, it's running in ATA-133/ non-UDMA mode). I also ran
SIGVERIF.EXE to check for and remove unsigned device drivers in
system32/drivers (I had never before heard of this utility). Several
of the unsigned drivers had to do with the HighPoint controller.

After this, I haven't had any trouble. I'm not sure where exactly the
problem is, but at this point, I don't care. It would be nice to be
able to run in UDMA mode, but I'm just happy to have the computer
running again.


Joseph
 
Back
Top