Problems diagnosing system freezing

[Casian Moscovici]

I have an older computer with a Pentium 4 chip, P4S8X ASUS motherboard
and 512k of DDR 333 RAM. After many years of faithful and flawless
service this senior citizen has begun freezing randomly. Sometimes I can
immediately reboot it and it will run for as long as 48 hours before
locking up again. On other occasions the reboot will not even get to the
Post screen and I have to wait for minutes to hours before a successful
reboot.

Of course, hardware is the primary suspect starting with the CPU which I
suspected might be overheating. However, all the fans are in working
order and the lockups are not consistent with overheating. As I
mentioned, the machine can run for as long as 48 hours before dying.
Additionally, I have been able to occasionally reboot it immediately
after locking up even though the computer had been running for many
hours. I've run a number of hardware diagnostic utilities and all
pronounce the system as healthy.

There is one additional bit of information that might be a clue to
brighter minds than mine: I have a stick of DDR 400 RAM (also 512k) that
I used to replace the incumbent stick as a test. Every time I make the
switch, regardless of the time lag before the freeze-up and the reboot
(minutes or days), the PC successfully posts and begins to launch
Windows. Unfortunately, Windows returns error messages about system
files missing or corrupted. When I put the 333 RAM back and the reboot
makes it past the post, Windows loads up just fine.

It seems that the culprit is the RAM, but a few techs I've spoken to
blame the motherboard. I'd like to give the DDR 400 RAM a shot to
determine if it's RAM or motherboard that's bad, but don't understand
why Windows won't load. Could the 400 RAM also be bad? Is it normal and
customary for Windows to be so sensitive to different RAM? Would repair
or re-install help with the 400 RAM?

Thanks for you help

Casian

 

[Andrew E.]

Either way 512mb of ram is a min. amount for xp,768 or 1024mb will help.
Also,some boards will only run on dual-sided memory,single sided simply
doesnt work right,+ if running two or more sticks,both should be of the same
type (dual or single)...Also,to test memory,run the memory tester,get it at:
http://oca.microsoft.com/en/windiag.asp

 

[Bob Willard]

I have an older computer with a Pentium 4 chip, P4S8X ASUS motherboard
and 512k of DDR 333 RAM. After many years of faithful and flawless
service this senior citizen has begun freezing randomly. Sometimes I can
immediately reboot it and it will run for as long as 48 hours before
locking up again. On other occasions the reboot will not even get to the
Post screen and I have to wait for minutes to hours before a successful
reboot.

Of course, hardware is the primary suspect starting with the CPU which I
suspected might be overheating. However, all the fans are in working
order and the lockups are not consistent with overheating. As I
mentioned, the machine can run for as long as 48 hours before dying.
Additionally, I have been able to occasionally reboot it immediately
after locking up even though the computer had been running for many
hours. I've run a number of hardware diagnostic utilities and all
pronounce the system as healthy.

There is one additional bit of information that might be a clue to
brighter minds than mine: I have a stick of DDR 400 RAM (also 512k) that
I used to replace the incumbent stick as a test. Every time I make the
switch, regardless of the time lag before the freeze-up and the reboot
(minutes or days), the PC successfully posts and begins to launch
Windows. Unfortunately, Windows returns error messages about system
files missing or corrupted. When I put the 333 RAM back and the reboot
makes it past the post, Windows loads up just fine.

It seems that the culprit is the RAM, but a few techs I've spoken to
blame the motherboard. I'd like to give the DDR 400 RAM a shot to
determine if it's RAM or motherboard that's bad, but don't understand
why Windows won't load. Could the 400 RAM also be bad? Is it normal and
customary for Windows to be so sensitive to different RAM? Would repair
or re-install help with the 400 RAM?

Thanks for you help

Casian

To see if RAM is the culprit, download MemTest86 and let it run for a
few passes. www.MemTest.com

When a MoBo dies, the most common culprit is capacitors on the MoBo.
You may want to remove and examine the board for caps that have leaked.

But my first choice is still overheating. Now that you have checked the
fans, check the filters to make sure they are not clogged. And, clean
out the heatsinks -- esp. the CPU heatsink. On my P4C800ED, I used
MBMv5 (no longer supported) to monitor the CPU (etc.) temps in realtime;
when the CPU temp got close to 65°C under full load, I shut down and
cleaned fans & filters & heatsinks, which reduced the full load temp by
~10°C. For a good CPU load, I suggest Prime95, which bumped the CPU
temp on my P4 by well over 10°C.

If not RAM/MoBo/overheating, what's left is pretty much the Power
Supply. Most PSs are really cheap, and also inexpensive. ;-)

 

[philo]

I have an older computer with a Pentium 4 chip, P4S8X ASUS motherboard and
512k of DDR 333 RAM. After many years of faithful and flawless service this
senior citizen has begun freezing randomly. Sometimes I can immediately
reboot it and it will run for as long as 48 hours before locking up again.
On other occasions the reboot will not even get to the Post screen and I
have to wait for minutes to hours before a successful reboot.

Of course, hardware is the primary suspect starting with the CPU which I
suspected might be overheating. However, all the fans are in working order
and the lockups are not consistent with overheating. As I mentioned, the
machine can run for as long as 48 hours before dying. Additionally, I have
been able to occasionally reboot it immediately after locking up even
though the computer had been running for many hours. I've run a number of
hardware diagnostic utilities and all pronounce the system as healthy.

There is one additional bit of information that might be a clue to
brighter minds than mine: I have a stick of DDR 400 RAM (also 512k) that I
used to replace the incumbent stick as a test. Every time I make the
switch, regardless of the time lag before the freeze-up and the reboot
(minutes or days), the PC successfully posts and begins to launch Windows.
Unfortunately, Windows returns error messages about system files missing
or corrupted. When I put the 333 RAM back and the reboot makes it past the
post, Windows loads up just fine.

It seems that the culprit is the RAM, but a few techs I've spoken to blame
the motherboard. I'd like to give the DDR 400 RAM a shot to determine if
it's RAM or motherboard that's bad, but don't understand why Windows won't
load. Could the 400 RAM also be bad? Is it normal and customary for
Windows to be so sensitive to different RAM? Would repair or re-install
help with the 400 RAM?

Thanks for you help

Casian

First off, inspect the mobo carefully and have a look at the capacitors...
if any of them are swollen or leaky...go no further. If that's the case, you
will need a new mobo.
If all the capacitors look fine..then chances are it's a RAM problem.

The RAM stick that gives the errors...is bad for sure...you might as well
toss it.
OTOH: Even if your other stick passes a RAM test...it could still be
bad...or marginal enough to cause problems.

If the mobo looks OK then I'd just go out and get a new stick of RAM...
it's quite reasonably priced today and a 1 gig stick would not cost much

 

[Gerry]

Casian

Make sure the computer is free of dust.Use an Air Duster to remove dust.
Overheating could be the problem.

Try Ctrl+Alt+Delete to select Task Manager and click the Performance
Tab. Under Commit Charge what is the Total, the Limit and the Peak?

Is the computer left on 24/7?

Have a look in the System and Application logs in Event Viewer for
Errors and Warnings and post copies here. Don't post any more than 48
hours ago.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Don Phillipson]

I have an older computer with a Pentium 4 chip, P4S8X ASUS motherboard
and 512k of DDR 333 RAM. After many years of faithful and flawless
service this senior citizen has begun freezing randomly. Sometimes I can
immediately reboot it and it will run for as long as 48 hours before
locking up again. On other occasions the reboot will not even get to the
Post screen and I have to wait for minutes to hours before a successful
reboot.

Of course, hardware is the primary suspect starting with the CPU which I
suspected might be overheating. However, all the fans are in working
order and the lockups are not consistent with overheating. As I
mentioned, the machine can run for as long as 48 hours before dying.

In my desktops over 25 years three power supply units failed. This
seems about average. In a specialist computer store, it takes less
than five minutes to test voltages of an old PSU or instal a new one.

 

[Brian A.]

I have an older computer with a Pentium 4 chip, P4S8X ASUS motherboard and
512k of DDR 333 RAM. After many years of faithful and flawless service this
senior citizen has begun freezing randomly. Sometimes I can immediately
reboot it and it will run for as long as 48 hours before locking up again.
On other occasions the reboot will not even get to the Post screen and I
have to wait for minutes to hours before a successful reboot.

The problem with intermidiate shutdowns can be caused by hardware and/or
software in a various amount of different ways.

Of course, hardware is the primary suspect starting with the CPU which I
suspected might be overheating. However, all the fans are in working order
and the lockups are not consistent with overheating. As I mentioned, the
machine can run for as long as 48 hours before dying. Additionally, I have
been able to occasionally reboot it immediately after locking up even
though the computer had been running for many hours. I've run a number of
hardware diagnostic utilities and all pronounce the system as healthy.

Although you state that the fans are in working order, that does't mean
much.
When is the last time you cleaned out the dust that accumulates?
Have you looked closely at the heatsink to make sure it is not clogged with
dust?
Are the fans clean of dust?
Is the mobo and any/all connectors on it clean of dust?

There is one additional bit of information that might be a clue to
brighter minds than mine: I have a stick of DDR 400 RAM (also 512k) that I
used to replace the incumbent stick as a test. Every time I make the
switch, regardless of the time lag before the freeze-up and the reboot
(minutes or days), the PC successfully posts and begins to launch Windows.
Unfortunately, Windows returns error messages about system files missing
or corrupted. When I put the 333 RAM back and the reboot makes it past the
post, Windows loads up just fine

If you only have one stick of RAM in the machine and replacing the 333
with the 400 doesn't degrade or improve your situation, most likely your RAM
is fine.

It seems that the culprit is the RAM, but a few techs I've spoken to blame
the motherboard. I'd like to give the DDR 400 RAM a shot to determine if
it's RAM or motherboard that's bad, but don't understand why Windows won't
load. Could the 400 RAM also be bad? Is it normal and customary for
Windows to be so sensitive to different RAM? Would repair or re-install
help with the 400 RAM?

Before blaming the motherboard or other components, take a look through
event viewer for any errors at the time of shutdown for any clue and/or a
possible resolution to the problem.

Click Start > Run, type in: eventvwr.msc and press Enter or click Ok.
Expand the event viewer window.
Click once on either Applications or System in the Left pane.
Double click on an error listed in the Right pane to bring up a details
window.
Click the link if present at the end of the description to a page with a
"possible solution".



--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Bruce Chambers]

Either way 512mb of ram is a min. amount for xp,....

Another deliberate lie, Andrew? Why? At work, I have literally
hundreds of WinXP Pro machines ticking along quite happily on 512MB of RAM.

...768 or 1024mb will help.

Maybe, depending upon the applications in use. WinXP, in and of
itself, certainly doesn't need that.





--

Bruce Chambers

Help us help you:


http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot