crashing problem ? - crash.jpg (0/1)

  • Thread starter Thread starter Fred
  • Start date Start date
F

Fred

I expect someone here will have a good idea about this...

As of yesterday, my PC running WinXP has started crashing (rebooting)
pretty regularly every 10-30 minutes. Even if I am not using it and
just leave it on. I haven't added/removed any software or hardware
recently so it seems to be just out of the blue. System had been fine
for months prior.

I've attatched a picture of the system message that flashes for a
quick second just as it crashes.

Any clues there?

Could it be CPU overheating? it's an AMD AthlonXP 2200 about 2 years
old. It's running about 55C during light use or idle.

Could it be symptomatic of CPU or mem failure?

Thanks for any ideas!
 
Fred said:
I expect someone here will have a good idea about this...

As of yesterday, my PC running WinXP has started crashing (rebooting)
pretty regularly every 10-30 minutes. Even if I am not using it and
just leave it on. I haven't added/removed any software or hardware
recently so it seems to be just out of the blue. System had been fine
for months prior.

I've attatched a picture of the system message that flashes for a
quick second just as it crashes.
Click to expand...

Good try on that pic....no attachments here
Any clues there?

Could it be CPU overheating? it's an AMD AthlonXP 2200 about 2 years
old. It's running about 55C during light use or idle.

Could it be symptomatic of CPU or mem failure?

Thanks for any ideas!
Click to expand...


what does the event viewer say?
turn off 'reboot on errors' in 'start up/ recovery' from- system -in control panel.
 
Ahhhhh that is a hardware conflict at the bios level.
try resetting the CMOS via the jumper
or you could try a simpler way that often works set bios switches for 'PNP os installed'
and 'Reset configuration data' to yes.(if they are there)they may be worded differently.

You may have a damaged piece of hardware

or your bios battery went dead and enabled defaults which included integrated sound or
something else.
 
Ahhhhh that is a hardware conflict at the bios level.
try resetting the CMOS via the jumper
or you could try a simpler way that often works set bios switches for 'PNP os installed'
and 'Reset configuration data' to yes.(if they are there)they may be worded differently.

You may have a damaged piece of hardware

or your bios battery went dead and enabled defaults which included integrated sound or
something else.
Click to expand...

ok, thanks.. I'll look into this. I've noticed that the HDD light is
showing a lot of activity when the system is presumably idle. Could
this be another symptom of bios level hardware conflict, or another
clue?
 
Fred said:
ok, thanks.. I'll look into this. I've noticed that the HDD light is
showing a lot of activity when the system is presumably idle. Could
this be another symptom of bios level hardware conflict, or another
clue?
Click to expand...

The hard drive light on my computer, is on pretty well solid for the first
five minutes. My antivirus software scans the startup folder, so that is
part of it. The items in my system tray have to be loaded, and that is
more activity. So there are reasons for the disk light to be active.

If I were you, I'd start by setting:

Right/click on MY COMPUTER, choose Properties/Advanced Tab/StartUp and
Recovery, Uncheck the Automatically Reboot on error box.

When there is a BSOD (blue screen of death), having the Automatic Reboot
unchecked will leave the error message on the screen. Copy off the
information presented there. Usually the first two numbers have
intelligence in them, but copy it all for the sake of completeness.
If there is a driver name, like say "nvdisp.sys", write that down too.

STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Either post back the info here, or you can start looking in this list
for clues as to the nature of the problem. If the same driver name pops
up in each case, that will give a strong hint as to which hardware
is affected. Random crashes could indicate a memory problem.

http://aumha.org/a/stop.htm

Paul
 
Back
Top