Kevin has provides a good list of possible reasons. That
would be the short list. Without details, one can only
speculate. IOW your first step, long before trying to fix
anything, is to get the basic facts. What does Device Manager
and the system (event) log report? Did you execute
comprehensive hardware diagnostics provided free by a
responsible computer manufacturer? If he is not so
responsible, then you must download those diagnostics from
component manufacturers and third party sources. Especially
important are the results of memory and disk drive
diagnostics.
Now we move on to verifying integrity of subsystems. The
one subsystem that can cause all of you symptoms is the power
supply system - including power off for no reason. It is a
system of three components; not just a power supply.
Integrity can be confirmed in but two minutes as demonstrated
in two previous posts: "Computer doesnt start at all" in
alt.comp.hardware on 10 Jan 2004 at
http://tinyurl.com/2t69q
"I think my power supply is dead" in alt.comp.hardware on 5
Feb 2004 at
http://tinyurl.com/yvbw9
Two articles that provide useful pictures (but no reason to
disconnect power supply as shown) are:
http://techrepublic.com.com/5102-10586-5566528.html www.ochardware.com/articles/psuvolt/psuvolt.html
Your voltages must measure in the upper 3/4 limits as
provided in chart in that second discussion "I think my
power..."
Having confirmed power supply integrity and then done same
with hardware diagnostics, only then move on to software
suspects. But this being most important. Do not try to fix
anything - especially software - until the specific defective
hardware is identified or until hardware integrity is
confirmed. Rushing to fix things can result in more damage
and a more complex problem.
David Cho wrote:
After my laptop crapped out, I had to resort to my desktop as a backup.
The problems I have experienced are
- the computer powers off and restarts without warning. It powers off.
Not a blue screen of death, but it powers off
- When it restarts, (this does not necessarily follow the previous
issue), it runs chkdisk and finds all kinds of problems.
Now unto the relevance to this group.
- I have seen IIS errors that I had never seen
- Upon running some .NET code, I get an error complaining about some
assembly missing. the assembly name looks quite random (erwet_iuuq.dll
missing, for example)
- VS.Net keeps crashing, asking me for a debug option which includes
using VS.NET. Debug VS.NEt using VS.NET?
One would think reinstalling the OS. But how do you explain the
computer POWERING OFF out of the blue?