rebooting on own?

[Mark G.]

Have a machine running XP Pro and it has had issues for some time. This is
an AMD based machine that my wife mostly uses. Isn't overly loaded as far as
software is concerned and does have all recent patches and no viruses to
speak of.

Anyhow, quite often, this machine will look up or will simply reboot on its
own. This happens whether there is a user at the station or not. Just
random! Kind of strange behavior and I am trying to figure out what is
causing it. Was thinking of just reloading the OS or doing a repair, but
beforeso, I started to wonder if it was beyond that and maybe a hardware
issue causing it? Could it be? Could this be a sign of a faulty power
supply? I have had power supplies act up before, but not necessarily in this
fashion. What are your thoughts on that? Any thoughts on what to check?
Would hate to reload or repair just ot have the behavior continue. Any
thoughts to the best fix to this?

Thanks much for any and all help you all can give me. Hope I can get it
figured.

 

[DL]

Look at Event Viewer for any clues

 

[kim]

Right click Mycomputer select properties>Advanced tab>Startup and recovery
settings and uncheck Automaticly restart. Then you will be able to see the
error message on the BSOD. Check your fans are working and not cloged with
dust causing it to over heat and reboot.

 

[HeyBub]

Have a machine running XP Pro and it has had issues for some time.
This is an AMD based machine that my wife mostly uses. Isn't overly
loaded as far as software is concerned and does have all recent
patches and no viruses to speak of.

Anyhow, quite often, this machine will look up or will simply reboot
on its own. This happens whether there is a user at the station or
not. Just random! Kind of strange behavior and I am trying to figure
out what is causing it. Was thinking of just reloading the OS or
doing a repair, but beforeso, I started to wonder if it was beyond
that and maybe a hardware issue causing it? Could it be? Could this
be a sign of a faulty power supply? I have had power supplies act up
before, but not necessarily in this fashion. What are your thoughts
on that? Any thoughts on what to check? Would hate to reload or
repair just ot have the behavior continue. Any thoughts to the best
fix to this?
Thanks much for any and all help you all can give me. Hope I can get
it figured.

Heat can sometimes cause this symptom. Check the fans?

 

[Jim]

Have a machine running XP Pro and it has had issues for some time. This is
an AMD based machine that my wife mostly uses. Isn't overly loaded as far as
software is concerned and does have all recent patches and no viruses to
speak of.

Anyhow, quite often, this machine will look up or will simply reboot on its
own. This happens whether there is a user at the station or not. Just
random! Kind of strange behavior and I am trying to figure out what is
causing it. Was thinking of just reloading the OS or doing a repair, but
beforeso, I started to wonder if it was beyond that and maybe a hardware
issue causing it? Could it be? Could this be a sign of a faulty power
supply? I have had power supplies act up before, but not necessarily in this
fashion. What are your thoughts on that? Any thoughts on what to check?
Would hate to reload or repair just ot have the behavior continue. Any
thoughts to the best fix to this?

Thanks much for any and all help you all can give me. Hope I can get it
figured.

Dust inside the system , causing overheating ?

 

[Mark G.]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up, but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else. There were a couple of errors, but nothing that
seemed to point at why this is happening. With that said, I went and check
to see what was runnign on startup and shut down some things (there weren't
a lot of startup items to begin with), but even at this point, this machine
is looking up. I would say it looks up more than it actually reboots itself.
I had thought it was a screen saver thing as it does look up frequently
while in screen saver mode, but I do recall from the past that this doesn't
seem to be the culprit as it will lock up when in use as well. Just always
seems to lock up in screen saver mode too. So any other suggestions? Also,
any chance that if a hard drive failure is happening that this could be the
case too? Disk appears healthy, but I know it is old. Don't want to replace
anythign I don't have too. Am just trying to figure this all out. I
appreciate any more help you all can provide!

 

[westom]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up, but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else. There were a couple of errors, but nothing that
seemed to point at why this is happening.

First, you are asking because you don't know what is causing
problems. Those errors that mean nothing to you could identify the
problem.

Meanwhile, normal is for a defective supply to run a computer for
months - with rare crashes. Supply was always defective. Only way to
know if a power supply (or other parts of the power ‘system’) is good
is to measure voltages with a multimeter. What to measure is in "When
your computer dies without warning....." starting 6 Feb 2007 in the
newsgroup alt.windows-xp at:
http://tinyurl.com/yvf9vh
Connector chart to locate each color:
http://www.hardwarebook.net/connector/power/atxpower.html

In your case, most important voltages will be on the purple, red,
orange, and yellow wires. Measured when the system is multitasking to
all peripherals simultaneously. For example, playing complex graphics
(ie a movie), while downloading from the internet, while playing sound
loudly, while searching the disk drive, while connected to USB devices
that draw power, etc. Now you are ready to measure voltages that must
exceed 3.23, 4.87, and 11.7 VDC. And report those numbers here since
they include other facts not always apparent.

Now the entire power supply 'system' is known good or bad - without
doubts. Only then move on to other suspects.

Of course, if it is a Dell or HP, then it comes with comprehensive
hardware diagnostics for free. Provided just for solving problems
such as yours. If not, you must work harder.

Dust and heat must never be a reason for your problem. In fact,
that computer must work just fine in a 100 degree F room with large
balls of dust inside. Having said that, heat is a diagnostic tool.
Too many want to cure a problem found by heat, instead, by eliminating
normal and perfectly acceptable heat. Once the power 'system' is
known good, then better techs use heat (a 100 degree room or hairdryer
on highest heat settings) to find that defect while executing
comprehensive hardware diagnostics.

You are on the right track. Fix or replace nothing until the
problem is first identified. That includes viewing those event logs
and Device manager. Others who never learned techniques will assume a
power supply is good only because the computer boots. Do not know
that supply is only part of a larger power 'system'.

Start by confirming the integrity of that power supply system. Only
then move on to the few and other suspects.

 

[Paul]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up, but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else. There were a couple of errors, but nothing that
seemed to point at why this is happening. With that said, I went and check
to see what was runnign on startup and shut down some things (there weren't
a lot of startup items to begin with), but even at this point, this machine
is looking up. I would say it looks up more than it actually reboots itself.
I had thought it was a screen saver thing as it does look up frequently
while in screen saver mode, but I do recall from the past that this doesn't
seem to be the culprit as it will lock up when in use as well. Just always
seems to lock up in screen saver mode too. So any other suggestions? Also,
any chance that if a hard drive failure is happening that this could be the
case too? Disk appears healthy, but I know it is old. Don't want to replace
anythign I don't have too. Am just trying to figure this all out. I
appreciate any more help you all can provide!

You can run the stress test provided by the mersenne.org Prime95 program.
When prompted, indicate you're stress testing. This version of program,
starts a test thread per CPU core. A thread will stop on the first error
detected. One reason for an error to occur, is marginal memory operation.
Or an overclocked CPU. The program does an arithmetic calculation with a
known answer, and any errors are either caused by a defective CPU (unlikely),
or marginal memory. For the memory, sometimes even a slight voltage boost
in the BIOS, is enough to fix it. (Not something you're likely to find
in a HP/Dell/Gateway etc.) I've had this program stop in as little as
10 seconds, when an overclocked CPU was under test.

http://majorgeeks.com/Prime95_d4363.html

While the test is running, you can monitor the CPU temperature with Speedfan.
It understands the hardware monitor on a number of motherboards. Due to the
lack of standards though, the answers may not always be what you'd expect.
(I have some motherboards here, where a voltage measurement with a multimeter,
show power supply voltages to be exactly correct, while the built-in measurement
is off quite a bit.)

http://www.almico.com/speedfan438.exe

You're aiming for a CPU temperature of 65C or less, while Prime95 is running.

In addition to the direct symptoms (whether Prime95 errors out almost
immediately), you're also looking for indirect symptoms. Does the
machine freeze while that test is running ?

Fixing freezing problems is not easy, because they leave so few symptoms
to work with. In at least one case, a freeze was caused by a certain
network chip driver, and usually after about half an hour of system operation.
But that is the only case I know of, from several years ago, where it was
an actual bug in a piece of software causing it. More of the time, you might
only find it by replacing stuff.

Paul

 

[Leythos]

Start by confirming the integrity of that power supply system. Only
then move on to the few and other suspects.

For the cost of a Multi-Meter and your own time to go buy one you could
have purchased a spare PSU to test with.

Having looked at the PSU voltages, there is little they will tell you
while the computer is actually working, and you're not going to be
monitoring the DVM when he shuts-down most likely.

A PSU, a cheap one, 600W, can be purchased for as little as $40 for
testing with....

 

[Mark G.]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up, but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else. There were a couple of errors, but nothing that
seemed to point at why this is happening. With that said, I went and check
to see what was runnign on startup and shut down some things (there weren't
a lot of startup items to begin with), but even at this point, this machine
is looking up. I would say it looks up more than it actually reboots itself.
I had thought it was a screen saver thing as it does look up frequently
while in screen saver mode, but I do recall from the past that this doesn't
seem to be the culprit as it will lock up when in use as well. Just always
seems to lock up in screen saver mode too. So any other suggestions? Also,
any chance that if a hard drive failure is happening that this could be the
case too? Disk appears healthy, but I know it is old. Don't want to replace
anythign I don't have too. Am just trying to figure this all out. I
appreciate any more help you all can provide!

 

[Anna]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There
was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up,
but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else. There were a couple of errors, but nothing that
seemed to point at why this is happening. With that said, I went and check
to see what was runnign on startup and shut down some things (there
weren't
a lot of startup items to begin with), but even at this point, this
machine
is looking up. I would say it looks up more than it actually reboots
itself.
I had thought it was a screen saver thing as it does look up frequently
while in screen saver mode, but I do recall from the past that this
doesn't
seem to be the culprit as it will lock up when in use as well. Just always
seems to lock up in screen saver mode too. So any other suggestions? Also,
any chance that if a hard drive failure is happening that this could be
the
case too? Disk appears healthy, but I know it is old. Don't want to
replace
anythign I don't have too. Am just trying to figure this all out. I
appreciate any more help you all can provide!

Mark:
You've gotten a fair number of responses to your query, many of which (I
believe) have given you some insights into what exactly is causing your
problem(s) and indicating potential strategies to pursue re diagnosing and
resolving those problems. Anyway, since the problem(s) apparently still
exist let me suggest the following...

1. First of all, I'm assuming you're working with a desktop machine. I don't
recall if you identified the machine but I'll proceed on that basis.

2. Since you've apparently been "inside" your computer case - "There was
some dust, but I took care of that" (and I really don't want to know how you
"took care of that"), I'll assume you know your way around the various
components in the machine.

3. So do this. Unplug your AC cord and uninstall all connected components
except your power supply, processor & heatsink, RAM, graphics card (if any),
monitor, mouse & keyboard connections. Work *only* with those foregoing
components connected - no HDD(s), no optical drive, no floppy drive, no
sound card - no other peripheral/external devices connected.

4. Power on the machine and let it run for at least 1/2 - 1 hour during
which time you can access the BIOS settings and go from one screen to
another and in the process determine that all BIOS settings are appropriate
to your system. Check the temps with the BIOS hardware monitor settings to
see all is normal. If no untoward events during this period it should give
you some assurance there's no hardware issue involved here affecting the
machine's basic components (although this process is not completely
definitive).

5. On the other hand if the machine does lock up during this process you'll
know there's a hardware issue causing your problem.

6. Assuming all seems well hardware-wise, if you haven't already done so
(and you should have at the time your problem(s) began) check out your HDD
with the diagnostic utility you can (usually) download from the disk's
manufacturer. (I note you say the "disk appears healthy" but I don't know
how you've arrived at that conclusion).

7. If it appears your problem(s) are not hardware-related, then reinstall
the boot HDD and the optical drive and proceed on the basis that the
problem(s) are software-related - possibly a corrupted OS. (We're assuming
you're confident that your system is malware-free, right?)

8. At this point try the usual "fixes" on the basis you're dealing with a
corrupted OS.
a. Try the sfc /scannow and/or chkdsk/r commands.
b. Assuming you're working with a non-branded OEM XP OS installation CD or
retail version of same, run a Repair install of the OS.

Before attempting any of the above first ensure that you copy any important
files from your HDD to some removable media. Better yet would be to clone or
image the contents of your HDD to another drive.
Anna

 

[westom]

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up, but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else.

Power up or reboot is performed by a power supply controller. Its
inputs include power switch, a signal from the power supply, CPU
requests, requests enabled from selected peripherals via BIOS, and
those voltages. Easiest and a common reason for restarts means
measuring voltages, as posted previously. Even Anna's procedure is a
more laborious attempt to maybe obtain what the meter could have
identified definitively in 30 seconds - without disconnecting
anything.

Posted previously:

Start by confirming the integrity of that power supply system.
Only then move on to the few and other suspects.

Maybe its this or maybe its that. Or obtain voltage numbers
definitively reduce that list of suspects - so that the next reply can
provide something useful. Rmember - power supply is only one
component of the power supply system. Those numbers report on all
those components - in but a minute.

Viewing event logs confirms the OS does not cause nor knows what is
causing a reset. If anything in the startup was a problem, it would
appear in those system logs. Move on to what actually performs power
resets - the power supply controller and its various inputs. Start by
confirming integrity of the entire power supply system - a minute of
labor and disconnecting nothing.

Normal is for a defective supply to run a computer for months - with
rare crashes. Supply was always defective. Only way to know if a
power supply (or other parts of the power ‘system’) is and was good -
definitively - is to measure voltages with a multimeter.

 

[Mark G.]

I have no earthly idea how to go about checking the power supply controller.
Remember, as I was saying, it tends to lock up more than anything else.
Right now it won't even get post posting. Although I have tried anything to
get past it yet as that just started happening earlier this evening. I do
have a plan for that part and with it, it may give me "some" answers" or
additional things to check or whatever. As far as power and what is
happening here, power supplies can last 1 day or 10 years. Just all depends.
It could also be a combination of things like OS needs to be reinstalled to
rid any bugs, worms, viruses, etc...and then also a problematic power supply
Again though, I won't to try and just get it fixed, but in this case, I may
have to try a few things. I mean, if the OS reinstall address the locking
up, but the rebootsd still happen, then replace the power supply? When you
mention the "controller", what on the motherboard do I look for? And laslty,
my other thought is to try benchmarking a few things like the memory.
Running something like memtest to see what it reports. My concern there is
that it will lock up in the process of trying to complete the benchmark.
LOL. Any more suggestions, ideas, systematic approaches to this that more of
you can chime in on? I really appreciate the insight and input thus far!

Thanks for all the responses. I went inside the machine to check fans and
they all seem to be working fine. Temps don't seem to be an issue. There
was
some dust, but I took care of that. I also, as recommended went into the
event viewer and browsed to see what was going on right after a lock up,
but
I didn't see anything whatsoever that seemed to explain it. I also viewed
events from the past fews days and most of the items were 'information'
rather than anything else.

Power up or reboot is performed by a power supply controller. Its
inputs include power switch, a signal from the power supply, CPU
requests, requests enabled from selected peripherals via BIOS, and
those voltages. Easiest and a common reason for restarts means
measuring voltages, as posted previously. Even Anna's procedure is a
more laborious attempt to maybe obtain what the meter could have
identified definitively in 30 seconds - without disconnecting
anything.

Posted previously:

Start by confirming the integrity of that power supply system.
Only then move on to the few and other suspects.

Maybe its this or maybe its that. Or obtain voltage numbers
definitively reduce that list of suspects - so that the next reply can
provide something useful. Rmember - power supply is only one
component of the power supply system. Those numbers report on all
those components - in but a minute.

Viewing event logs confirms the OS does not cause nor knows what is
causing a reset. If anything in the startup was a problem, it would
appear in those system logs. Move on to what actually performs power
resets - the power supply controller and its various inputs. Start by
confirming integrity of the entire power supply system - a minute of
labor and disconnecting nothing.

Normal is for a defective supply to run a computer for months - with
rare crashes. Supply was always defective. Only way to know if a
power supply (or other parts of the power ‘system’) is and was good -
definitively - is to measure voltages with a multimeter.

 

[westom]

I have no earthly idea how to go about checking the power supply controller.
Remember, as I was saying, it tends to lock up more than anything else.
Right now it won't even get post posting.

Of course you do. Your solution was posted:

Easiest and a common reason for restarts means
measuring voltages, as posted previously.

That requested information would have answered your question and
maybe 15 others. You don't know why measuring provides immediately
useful answers. Explaining why would be tedious.

Appreciate that your speculations (such as an OS problem) is
unreasonable. Furthermore, if your problem is in a power supply
'system', then reloading the OS can only mean a defective power system
AND a defective OS. One thing that can make all others act
defectively is the power system. Until that 'system' is on a list of
known good items, everything else only results in a 'maybe' answers.

But again, get a useful and definitive (without doubt) answer. That
means first providing numbers as requested back on 7 May. I cannot
post anything useful - cannot even discuss the power supply controller
- without those essential numbers. Get those numbers. Then answering
questions on the power supply controller is easy. Without first
doing those few minutes of data collection, the answer is just too
difficult.

Forget speculation about the OS causing your problem. Disk drive
is also completely irrelevant to your symptoms. Why can be explained
later with the appropriate numbers.. If the power 'system' is
defective, then reloading an OS could also create a defective OS -
exponentially complicate your problems. Also discussed was a need
for simple information such as event logs and Device Manager, computer
manufacturer, etc.

Requoting what was so important in a previous post, start by
confirming integrity of the power supply system. Only then move on
to the few and other suspects. Want to know why? That would become
obvious once essential information (requested in the 7 May post) is
provided.

 

[Mark G.]

I am not sure how ti check the voltage nor what all is involved with the
"controller". I do have a volt meter, but again, just not sure what exactly
to check here. Is it possible to explain at least that?

I believe I did post the manufacturer. It is a MSI AMD board.

After this posting issue, I am starting to think it is a memory (bad memory)
issue anyhow. As many times as I have had power supply failures over the
last 20 years, typically it wouldn't cause a posting issue like this, but
bad memory can.

I have been kind of slow I going through the motions with this, but again,
if you or someone can explain exactly what I need or I should say "how" to
check "what" with a voltage meter, then I could try that route.

Thanks much.

I have no earthly idea how to go about checking the power supply
controller.
Remember, as I was saying, it tends to lock up more than anything else.
Right now it won't even get post posting.

Of course you do. Your solution was posted:

Easiest and a common reason for restarts means
measuring voltages, as posted previously.

That requested information would have answered your question and
maybe 15 others. You don't know why measuring provides immediately
useful answers. Explaining why would be tedious.

Appreciate that your speculations (such as an OS problem) is
unreasonable. Furthermore, if your problem is in a power supply
'system', then reloading the OS can only mean a defective power system
AND a defective OS. One thing that can make all others act
defectively is the power system. Until that 'system' is on a list of
known good items, everything else only results in a 'maybe' answers.

But again, get a useful and definitive (without doubt) answer. That
means first providing numbers as requested back on 7 May. I cannot
post anything useful - cannot even discuss the power supply controller
- without those essential numbers. Get those numbers. Then answering
questions on the power supply controller is easy. Without first
doing those few minutes of data collection, the answer is just too
difficult.

Forget speculation about the OS causing your problem. Disk drive
is also completely irrelevant to your symptoms. Why can be explained
later with the appropriate numbers.. If the power 'system' is
defective, then reloading an OS could also create a defective OS -
exponentially complicate your problems. Also discussed was a need
for simple information such as event logs and Device Manager, computer
manufacturer, etc.

Requoting what was so important in a previous post, start by
confirming integrity of the power supply system. Only then move on
to the few and other suspects. Want to know why? That would become
obvious once essential information (requested in the 7 May post) is
provided.

 

[Mark G.]

I am not sure how ti check the voltage nor what all is involved with the
"controller". I do have a volt meter, but again, just not sure what exactly
to check here. Is it possible to explain at least that?

I believe I did post the manufacturer. It is a MSI AMD board.

After this posting issue, I am starting to think it is a memory (bad memory)
issue anyhow. As many times as I have had power supply failures over the
last 20 years, typically it wouldn't cause a posting issue like this, but
bad memory can.

I have been kind of slow I going through the motions with this, but again,
if you or someone can explain exactly what I need or I should say "how" to
check "what" with a voltage meter, then I could try that route.

Thanks much.

I have no earthly idea how to go about checking the power supply
controller.
Remember, as I was saying, it tends to lock up more than anything else.
Right now it won't even get post posting.

Of course you do. Your solution was posted:

Easiest and a common reason for restarts means
measuring voltages, as posted previously.

That requested information would have answered your question and
maybe 15 others. You don't know why measuring provides immediately
useful answers. Explaining why would be tedious.

Appreciate that your speculations (such as an OS problem) is
unreasonable. Furthermore, if your problem is in a power supply
'system', then reloading the OS can only mean a defective power system
AND a defective OS. One thing that can make all others act
defectively is the power system. Until that 'system' is on a list of
known good items, everything else only results in a 'maybe' answers.

But again, get a useful and definitive (without doubt) answer. That
means first providing numbers as requested back on 7 May. I cannot
post anything useful - cannot even discuss the power supply controller
- without those essential numbers. Get those numbers. Then answering
questions on the power supply controller is easy. Without first
doing those few minutes of data collection, the answer is just too
difficult.

Forget speculation about the OS causing your problem. Disk drive
is also completely irrelevant to your symptoms. Why can be explained
later with the appropriate numbers.. If the power 'system' is
defective, then reloading an OS could also create a defective OS -
exponentially complicate your problems. Also discussed was a need
for simple information such as event logs and Device Manager, computer
manufacturer, etc.

Requoting what was so important in a previous post, start by
confirming integrity of the power supply system. Only then move on
to the few and other suspects. Want to know why? That would become
obvious once essential information (requested in the 7 May post) is
provided.

 

[westom]

I am not sure how ti check the voltage nor what all is involved with the
"controller". I do have a volt meter, but again, just not sure what exactly
to check here. Is it possible to explain at least that?

A wire connects power supply to the motherboard. It has colored
wires and a connector that looks like this:
http://www.hardwarebook.net/connector/power/atxpower.html

On the meter, select 20 VDC. Touch the black probe to any black
wire in the connector or to the metal chassis. Touch the red probe to
the purple wire where that wire enters the nylon connector. Read a
number on the meter. This is the first step described in "When your
computer dies without warning....." starting 6 Feb 2007 in the
newsgroup alt.windows-xp at:
http://tinyurl.com/yvf9vh

Record that number to post here. The same procedure describes
measuring voltages on the green and gray wires both before and when
power switch is pressed.

Then power the system up. Maximize the load by accessing numerous
peripherals simultaneously. Multitask complex graphics to the video
card (ie play a movie), while downloading from the internet, while
searching the hard drive, while playing a CD, while outputting loudly
to speakers, while searching a floppy disk, .... Now measure
voltages on any one of the red, orange, and yellow wires where those
wires enter the nylon connector.

The post those three digit numbers here as described in:
http://tinyurl.com/yvf9vh

 

[Leythos]

After this posting issue, I am starting to think it is a memory (bad memory)
issue anyhow. As many times as I have had power supply failures over the
last 20 years, typically it wouldn't cause a posting issue like this, but
bad memory can.

If you've had power supply failures, "as many times", then you really
have a bad environment - I can count the number of bad PSU's I've had on
1 hand, in 30 years....

If you already know your environment is trashed, why not get a UPS to
control the power to the computer, also purchase a new QUALITY PSU for
the computer, and then rebuild it.

If it's crashed as many times as you say, you've most likely trashed
something in the OS/Apps, not to mention all the problems you're going
to continue to have because of bad power....