I have a computer that usually reboots once a day with Event ID 1003. Below is the info from the event log. This is a Windows XP Pro computer logging into a 2003 domain. Any suggestions?
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/20/2009
Time: 8:30:03 AM
User: N/A
Computer: DCTEMP4
Description:
Error code 1000000a, parameter1 00013e48, parameter2 00000002, parameter3 00000001, parameter4 80701a16.
For more information, see Help and Support Center at http://go.microsoft.com/fw
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 31 33 65 34 38 2c 20 013e48,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 37 30 01, 8070
0050: 31 61 31 36 1a16
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
My experience has been that random reboots are normally caused by hardware problems and usually due to overloading a weak power supply. However, when that happens, you normally don't get an event written to the event logs because the computer does a "hard" reboot before it gets an opportunity to write anything to the logs.
With that being the case, I would actually take a look at the software side first. According to the following link, you "might" be dealing with some type of malware:
http://support.microsoft.c
I would first take a look at your task manager and make sure you recognize the processes that are running and that there's not anything funky in there. I would also recommend downloading/running superantispyware. I've found that this app will catch a lot of things that even a good AV apps won't.
That might not be the solution, but maybe it'll rule the malware possibility out for now.
Also, does it reboot at exactly the same time every day? Does it every reboot twice in one day?
You could also see if there's a dump of the state of your system at the time it crashed.
The dumps are normally located in c:\windows\minidump\
or %systemroot%\minidump\
If there is, can you paste the latest dump(s) in the "Attach Code Snippet" box and i'll take a look. You'll need to rename single minidump files first with a .txt extension, (do not rename the contents of the file). Alternatively zip them before attaching, and rename the .zip to .txt for the attaching (the upload).
You may need to disable auto restart:
Right click My Computer > Properties > Advanced > Startup and Recovery Settings and uncheck Automatically Restart.
Another possibility is motherboard failure ... capacitor failure being the main cause of mobo failure. See the capacitor plague:
http://en.wikipedia.org/wi
Then, if still unresolved, try a new preferably larger capacity power supply.
I don't think it is heat related because it usually only does it once a day and is usually in the morning.
I have not done any driver or BIOS updates since originally putting the machine together.
Memtest86 was the first thing I tried. I ran it through multiple passes one night with no errors.
I will check the processes for culprits.
Where would I change the system recovery parameters?
Right click My Computer > Properties > Advanced > Startup and Recovery Settings and remove check from Automatically Restart box.
Look here: http://www.pchell.com/supp
Here is an article: http://support.microsoft.c
Ok, further search narrowed the possible cause of the problem to:
1)McAfee
2)Bad RAM (run stress check)
3)VideoCard drivers
4)AMD and SP3 on XP problem: http://www.techsupportforu
From your minidump it could well be a driver problem. You could see if the Verifier.exe command shows which drivers are not verified >
How to Use Driver Verifier to Troubleshoot Windows Drivers:
http://support.microsoft.c
Before launching Driver Verifier please read the article below, in particular the comments in paragraph 3 noting which ''settings' to avoid.
Using the Microsoft Driver Verification Tool:
http://www.codeproject.com
Basically you set it to verify all drivers, then you reboot.
You'll possibly get a BSOD at this point, & hopefully the dump file analysis will point to the driver that is the problem(assuming of course that a driver is the real cause!).
Start > Run > then type verifier.exe (no quotes).
Info: Verifier.exe is located in the %WinDir%\System32 folder.
The Driver Verifier operation is described quite clearly here>
"Troubleshooting drivers with XP's hidden Driver Verifier Manager":
http://articles.techrepubl
Took another look at the problem and found these instructions for the Drive Verifier. Please note that although they're written for Vista & Windows 7, they're suitable for XP.
For XP you simply do this>
START > Run > cmd > then type VERIFIER
Then follow the verifier instructions:
http://www.techsupportforu
If you get a dump file from c:\windows\minidump, zip it up & post it here of course.
I ran the driver verifier with all drivers selected and the system rebooted with no BSOD.
I don't have and McAfee products installed. This PC used to have McAfee site advisor on it but it was uninstalled months ago.
The processor is an Intel dual core 3.2 GHz.
The video card is a nvidia GeForce4 MX 4000 with driver version 6.14.10.6693.
I ran a check disk with both options selected. Nothing was logged in the event viewer. This is a Western Digital hard drive. It seems like a hard drive problem would show up more often than this problem is. Are there any good hard drive tools that can be run from Windows? If not I will run mfg tools locally in the morning.
I hate to be potentially dragging you off course, but have you tried running superantispyware yet? The only reason I recommend this is because it's easy and just takes a couple of minutes to run. I would consider this "low hanging fruit" and do it just to eliminate it as a possible cause. In the same vein, how did the processes in task manager look?
When McAfee was removed months ago, conceivably it was not completely uninstalled.
You could try running this Uninstaller >
http://www.wikihow.com/Uni
Another idea is to run Process Explorer v11.33
http://technet.microsoft.c
See if there's any offending file. If it is a svchost.exe, then Select the Services Tab.
You can see what services are in that svchost.exe.
Then Select the Threads tab, and see what .exe or .dll is using the CPU. You can select it by double clicking it.
On the infection theme it's also worth downloading then updating Malwarebytes' Anti-Malware:
http://www.malwarebytes.or
When updated, reboot into Safe Mode by selecting F8 at bootup & run a scan.
If still no good i suggest you install and run Trend HijackThis 2.02:
http://majorgeeks.com/Tren
Create a folder where you would like the HijackThis file to reside and run it from there, not from the Desktop or a temporary folder.
Run the scan & save the logfile. Then click the "Attach Code Snippet" box, paste the logfile into the "Code Snippet" page and then we can get it analysed.
If you haven't had the opportunity of visually checking the mobo there's still the possibility of capacitor failure, particularly the capacitors adjacent to the CPU.
While you are there you could inspect the CPU/heatsink assembly (thermal paste?)
Also worth considering borrowing(?) a new preferably larger capacity power supply, if issue remains unresolved.
I checked the mobo and found no defective caps.
I also pulled the heat sink and cleaned it then replaced it with fresh thermal paste.
HiJack This report attached below.
I did also run the process explorer but I'm not sure what I'm looking for. The help file that extracted with the program is not functional.
Ok, thanks ..
This guide might be useful ... scroll to the Video references>>http://forum.sys
Or details, with pics >
http://ask-leo.com/
Checking your HJT logfile ...
Your HijackThis log looks very clean!
If you recognise these, no problem. Otherwise you can 'fix' them with HJT >>
O17 - HKLM\System\CCS\Services\T
O17 - HKLM\Software\..\Telephony
O17 - HKLM\System\CS1\Services\T
This doesn't guarantee you have no infection, HijackThis is simply a guide as to what we can use next. But at this point i see no reason to run the powerful ComboFix, although you may like to try the safe & popular Malwarebytes.
Is the machine still rebooting after applying the fresh thermal paste?
If yes, another suggestion is to try Autoruns. It's a system Startup utility with which you can view and change all the processes that windows normally load at bootup >
Autoruns for Windows v9.53:
http://technet.microsoft.c
Right-click on icon then select "run as administrator".
Let it scan (status is shown on lower-left of screen).
Select "Everything" tab.
See if you can spot any rogue entries.
If there are, delete them or disable them by un-checking the appropriate box.
Then there's that earlier suggestion of a new, preferably larger PSU ...
Business Accounts
Answer for Membership
by: Steelers4lifePosted on 2009-08-20 at 07:56:37ID: 25143303
Is it possible the machine is over heating ? Coupld be the CPU over heating ? I would run hardware diagnostics and make sure it is not a hadware issue.