Computer Restarting For Unknown Reason/s
<div class="IPBDescription">ALWAYS while performing a function though</div>This is weird... recently formatted and everything went smoothly, BUT.... ... .. .
My computer will restart for no reason, other than I am performing a task such as minimizing a browser, or trying to upload a file. It never restarts if I am afk, afaik.
It does this several times/day. WinXP O/S if it matters.
My computer will restart for no reason, other than I am performing a task such as minimizing a browser, or trying to upload a file. It never restarts if I am afk, afaik.
It does this several times/day. WinXP O/S if it matters.
Comments
nanites again? <img src="style_emoticons/<#EMO_DIR#>/confused-fix.gif" style="vertical-align:middle" emoid="???" border="0" alt="confused-fix.gif" />
<!--QuoteEnd--></div><!--QuoteEEnd-->
Well the real problem is you are asking for an analysis trough the internet. Yet it could be many things, which are not possible to test for trough the internet.
For instance:<ul><li>mem could be bad, and when the Os tries to write something into the memory which is corrupted it can reboot.
Then I'd advice <a href="http://www.memtest86.com/" target="_blank">http://www.memtest86.com/</a>
</li><li>Or it could be hear related asAnarkiThreeXSix said, go download some hardware temp monitor programs (probably included with the motherboard/pc)
</li><li>It could any number of hardware conflicts (mem vs cpu, cpu vs pci-controller, hdd vs mem and the list goes on)
are there any conflicts (start->programs->accessories->system tools->system information in here have a look at shares/conflicts or something)
</li><li>software related, try booting into safemode (for vista, is it still f8 for bootmenu? [edit]--> ACK! you've gone done and put a switch of OS on me!!! XP FTW!!!)</li><li>virus and spyware can kill the OS and make it reboot (most likely a bootsector virus on a fesh format, if it is viral)</li><li>gremlins, I swear!</li></ul>Basically all of the above could help you in determining what could be the cause, then the mighty internet/google can help you resolve it with tutorials. Or someone on here with a similar problem which was solved
check to see if automatic reboot is on
Start -> Settings -> Control Panel -> System -> Advanced Tab -> Settings Button under "Startup and Recovery" -> untick "AUtomatically Restart"
This will make sure the BSODs get shown
to check to see if you ARE getting BSODs go check in this Dir:
C:\Windows\Minidump (or somewhere around there, the folder name is minidump, the file names corespond to dates of crashes)
or Gremlins
or Viri
or Viri infested gremlins!
Edit: Plural of Virus is Viri! (not Virii), yay for having clasics majors for friends!
As for your computer problems, I think you can rule out heat, if it restarts even when you minimize a window, since that's not exactly a tough calculation for the CPU to do, if you know what I mean.
to folow up on Kouji's post about mem.
check to see if automatic reboot is on
Start -> Settings -> Control Panel -> System -> Advanced Tab -> Settings Button under "Startup and Recovery" -> untick "AUtomatically Restart"
This will make sure the BSODs get shown
to check to see if you ARE getting BSODs go check in this Dir:
C:\Windows\Minidump (or somewhere around there, the folder name is minidump, the file names corespond to dates of crashes)
<!--QuoteEnd--></div><!--QuoteEEnd-->
Automatic restart de-selected.
There are some BSODs in there, and one for today.
nothing more then memory
Generaly BSODs are caussed by errors when writting to memory (If I remember correctly).
You can run those mem tests that Kouji posted
and there is always the fun one of just swapping around memory
also as a first try, just unseat and reseat all your memory.
<i>Singular
virus
Plural
viruses or virii or viri
virus (plural viruses or virii or viri)
1. (pathology, microbiology, virology) A core of DNA or RNA surrounded by a protein coat that requires a living cell to replicate — often causes disease in the host organism.
2. (computing) A computer virus.</i>
What are you temps?
Do you have dust buildup which is causing critical components to overheat?
Are you overclocked?
Is your PSU going bad(get out a multimeter or download some software that will read your volts)
Run memtest
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Product: Windows Operating System
ID: 7
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_BAD_BLOCK
<b>Message: The device, %1, has a bad block. </b>
Explanation
The device has a bad block of memory, which Windows attempted to read. The data might be missing or corrupted.
User Action
If this event is logged regularly, replace the hard disk drive.<!--QuoteEnd--></div><!--QuoteEEnd-->
<a href="http://www.techspot.com/vb/topic7602.html" target="_blank">http://www.techspot.com/vb/topic7602.html</a>
Do you have an AMD cpu? I think those restart suddenly when they're a bit too warm -_^
<!--QuoteEnd--></div><!--QuoteEEnd-->
Stop bashing AMD Anarki3x6... The "a bit too warm" that the fail safe usually kicks is about the temperature water boils. Have you never heard of a heatsink?
I agree with Thansal. From what you are describing my instincts tell me it's your RAM chips. Usually just one of them. What measures of ESD protection did you employ, Depot?
Then check your hard drive as Luukas said. What that error means is that you are getting an input-output error to the CPU from either your RAM or while loading data from the HDD into RAM. I'm afraid it's not more specific than that. BSOD's are really low-level so they are really basic and unclear at times.
ESD protection?
My backup computer here (a '99 Dell P-3 450mhz) with a new hd is running SOOOOOooooo..... smoothly.
Chkdsk/r has replaced 3 bad clusters so far.
memory,
nothing more then memory
Generaly BSODs are caussed by errors when writting to memory (If I remember correctly).
You can run those mem tests that Kouji posted
and there is always the fun one of just swapping around memory
also as a first try, just unseat and reseat all your memory.
<!--QuoteEnd--></div><!--QuoteEEnd-->
BSODs are caused by any and everything, from a failed memory operation to the kernel trying to unload itself while performing an operation to the video card being slightly confused about where, exactly, it is on the motherboard. (win95 used to have a BSOD for a busy optical drive). the bluescreen should have some stuff printed on it like "general protection fault" and then a process name or a device id and a complaint about drivers or an "oh my god i think i'm exploding" message of some sort.
The chkdsk/r I'm running now has replaced 3 bad clusters of file data.
does windows complain about a bad shutdown on boot or does it like to pretend nothing happened?
also, last i checked the "bit too warm" mechanism kicks in at about 85C, a little short of the 90C that they can take before the chip decides that it's getting toasty.
it's a decent bit safer than intel's "underclock and pray" method
<!--QuoteEnd--></div><!--QuoteEEnd-->
Oh my goodness! <img src="style_emoticons/<#EMO_DIR#>/wow.gif" style="vertical-align:middle" emoid=":0" border="0" alt="wow.gif" /> Please tell me you know what ESD is...
<a href="http://www.esda.org/esdbasics1.htm" target="_blank">http://www.esda.org/esdbasics1.htm</a>
Too many amperes, or current, hurts us humans. Voltage will DESTROY electronics like capacitors if it is too much. RAM is essentially uber-tiny capacitors. You know how sometimes when you comb your hair, or rub a balloon on somebody's head, etc. and you get that static "zapping"? That's ESD. Those sparks are usually abou 10,000-20,000 volts. May seem extreme, but remember it's very little current. Not that a high enough voltage can't hurt our anatomy, but in an oversimplified nutshell it comes down to this:
Amps hurts us
Volts hurts computers
So. Computer techs get these things called anti-static wrist straps that have a high Ohm resistor in them to allow voltages to ground off their hands freely while not allowing a high current to be grounded in case they touch the wrong wire.
I'm soo sick of stupid people on newegg.com complaining in reviews that they had a DOA (dead on arrival) chip. The chip wasn't DOA, they zapped it by unpacking it in the packing peanuts or getting their hands all over the pins without grounding any static charges off first. Now if you are being causal you may not bother with a wrist strap but at least washing your hands with water and touching the metal case to ground yourself is a not guaranteed solution but definitely helps. In reality only time I bother with a wrist strap is when dealing with RAM chips or adjusting bent pins on a CPU. And I do wash my hands first. Before playing with ESD sensitive parts, especially when you are talking about chips that are over $100 per chip. That'd really suck to ESD zap one of those.
x5 I was aware of the damage static electricity can do, and take precautions to prevent it. Never heard it referred to as "ESD".
<b>From the Event Log (at restart):</b>
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Product: Windows Operating System
ID: 11
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
User Action
Replace the cable.<!--QuoteEnd--></div><!--QuoteEEnd-->
A restart takes me well over 2 minutes... normally does so in less than a minute.
CPU temp is 28/82 and mobo 32/89.5
Edit: or SATA.
I have a bunch of IDE cables lying around anyways; they always seem to come with both the HD and the mobo or something.
<!--QuoteEnd--></div><!--QuoteEEnd-->
I have that with SATA cables.
This just out: I am now getting an error report at restart, and the event log shows,
<b>From the Event Log (at restart):</b>
A restart takes me well over 2 minutes... normally does so in less than a minute.
CPU temp is 28/82 and mobo 32/89.5
<!--QuoteEnd--></div><!--QuoteEEnd-->
Using what? Gotta explain those temps since every program reads differently. I suggest you download coretemp and tell us those temps. It will work on AMD cpus, but maybe not the really older versions.
I'm using the default temp monitor, viewable by going into the setup screen during bootup.