XP randomly reboots itself
5 min read
Your noises and symptoms bring to mind a heat issue. How old is the computer and do you ever clean it inside?
As to errors:
To discover the type of Errors the machine has encountered recently, use Event Viewer.
- Go to Start - Run type eventvwr.msc then Press Enter.
- When the Event Viewer opens, there will be two panes.
The left pane is for event categories (Application, Security, and System).
The right pane is for event messages (Information, Warning, and Error). (We want to find errors.) - Left-click the Application category in the left pane and check for any error messages in the right pane.
You want to find the one(s) that occurred at the same time your system encountered the problem you have posted about. - Repeat the previous step for each category, or until you find an appropriate error to investigate.
- Double-click the error message to bring up the information.
- Click the third button on the right side of the information window (copies information)
- Paste the information here
Also turn off the auto restart function:
How to turn off Auto Restart in XP
Right click on My Computer
Select Properties
Select the Advanced tab then the Startup & Recovery section
Select the Settings button
Uncheck "Automatically restart" and then click Apply
This will give you a Blue Screen with the error message rather than restarting the computer.
Write down the error detail then use the reset button on the computer to restart.
Basic information about these errors can be found here:
Troubleshooting Windows STOP Messages
0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers.
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high.
So we have some memory or driver issue but it is hard to place.
Any new hardware or software? Any new drivers?
I would suggest getting some canned air and cleaning out the inside of the case. Usefull info here:
http://forums.whatthetech.com/Maintenance_…SD_t103649.html
The next step would be to run MemTest:
http://www.memtest.org/
Also if the problem persists please repost all new Error Codes.
If anything I've suggested is in the least bit confusing do not hesitate to ask for clarification.
One final initial response is to run Check Disk.
Go to start Run… cmd
Then type chkdsk /r
You will be told the volume is in use > do you want to run at reboot?
Say yes (Y) and reboot.
Note this might take an hour to run on reboot. Just let it run till it tells you it is finished.
.
Hmmm, neither of Rich's links work for me. Try these:
MemTest86+
Windows Memory Diagnostic
I note Windows Memory Diagnostics has an easy to follow guide on their home page, and an excellent MemTest86+ tutorial can be found here.
I would note folks tend not to let the testers run through several passes. I let them run overnight.
Also Check Disk will take some time if run properly. Did it run on a reboot? Was it run as Administrator?
If not verify the command was chkdsk C: /r (assuming C: is the system drive).
You might also try this approach:
http://windowshelp.microsoft.com/Windows/e…c41f811033.mspx
Also if you recieve more errors please post them.
Tutorial here:
http://icrontic.com/articles/diagnose_with_memtest86
Give either a try.
Ask AI
AI can make mistakes. Check the cited posts. Archived advice can be out-of-date
Don't include personal information. Questions and selected public posts go to OpenAI. About Ask AI