Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Computer Automatically Restart

  • Please log in to reply
1 reply to this topic

#1 kecik


  • Members
  • 13 posts
  • Gender:Female
  • Local time:01:44 PM

Posted 21 January 2008 - 05:45 AM

I put this in the forum of Operating System-> windowsXP, and there was a suggestion to post in this topic, so now I do it.
My computer automatically shut down & restart. "Problem caused by Device Driver". It happened not so often, once or twice a day. I open the device management, there are nothing "strange".
I openned the log event :
Event Type : Error
Event Source: System Error
Event Category: (102)
Event ID : 1003
Date 1/9/2008
Time : 3:03:10 PM
User : N/A
Computer: UTENTE
Error code 100000d3, parameter1 bf800130, parameter2 00000002, parameter3 00000001, parameter4 806ff84a.

For more information, see Help and support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 53 79 73 74 65 6d 20 45
0008: 72 72 6f 72 20 20 45 72
0010: 72 6f 72 20 63 6f 64 65
0018: 20 31 30 30 30 30 30 64
0020: 33 20 20 50 61 72 61 6d
0028: 65 74 65 72 73 20 62 66
0030: 38 30 30 31 33 30 2c 20
0038: 30 30 30 30 30 30 30 32
0040: 2c 20 30 30 30 30 30 30
0048: 30 31 2c 20 38 30 36 66
0050: 66 38 34 61

According to microsoft documents, this symptoms might came from spywares: Msupd5.exe and reloadmedude.exe.
I tried to follow the instructions but I could not find the files from the malwares in windir\system32\drivers.
And the restart still go on. Frustrated, I open the CPU and clean inside (it was really dirty). After one day, it happened again.
I have Symantec Endpoint 11, daily full scan, daily live update.

Following the suggestion in the forum, I did online scanning with Trendmicro and it found:
Also vulnerability: MS 06-003; MS06-012;MS06-027;MS06-028;MS06-033; MS06-037; MS06-048; MS06-054; MS06-056; MS06-058; MS06-059; MS06-060; MS07-047

Then I did "clean".

The problem still happenned.
Is that problem from those malwares (virus or anyother names)? Might there be still another virus?
Or how to correct this restart behaviour?

Thank you.

BC AdBot (Login to Remove)


#2 quietman7


    Bleepin' Janitor

  • Global Moderator
  • 51,759 posts
  • Gender:Male
  • Location:Virginia, USA
  • Local time:08:44 AM

Posted 21 January 2008 - 08:48 AM

"Event ID: 1003"

The symptoms you describe could be malware related or they could be due to hardware or overheating problems caused by a failed processor fan, bad memory (RAM), failing power supply, underpowered power supply, CPU overheating, motherboard, video card, faulty drivers, BIOS and firmware problems, dirty hardware, etc. If the computer is overheating, it usually begins to restart on a more regular basis. If your not finding any malware then its sounds like one of the latter problems.

Some video cards run so hot that they have their own cooling system. If the fan fails, the video processor will not be far behind and your system may start crashing. If that is the case see "Illustrated How to Replace an AGP Video Card" and "10 things to know before buying a video card".

In Windows XP, the default setting is for the computer to reboot automatically when a fatal error or crash occurs. You should be able to see the error by looking in the Event Log. Read "How To Use the Event Viewer Applet". You can then gather more information doing a search of the Event ID number at:
"MonitorWare EventID Database"
"Windows Security Log Events".
"Events and Errors Message Center".

Note: Windows 2000 users should see "Windows Restarts Continuously with Blue Screen" and "Gathering Blue Screen Information After Memory Dump in Windows 2000".

An easy way to use Event Viewer is to create a log as follows:
  • Click Start > Run and type: eventvwr
  • press Ok or Enter.
  • In the right pane, right-click on "Applications", select save log file as, and save the log to your desktop as app.csv
  • In the right pane, right-click on "System", select save log file as, and save the log to your desktop as sys.csv
  • You can use Notepad to open each .csv file and search for any problems.
A free tool you can use to view your event logs is WinAudit.
  • After download, double-click WinAudit.exe to launch.
  • Under "To audit your computer...", click the Here link.
  • WinAudit will start examining your computer and generate a System Overview Profile.
  • Under Categories in the left pane, select Error Logs.
  • There will be three sub-categories: Application Errors, Security Errors and System Errors.
  • From there, scroll down the list to view the logs.
  • You can click the "Save" button at the top to save a report in .html format.
An alternative is to turn off the automatic reboot feature so you can actually see the error code/STOP Message when it happens - this is also known as the Blue Screen Of Death (BSOD).

To change the recovery settings and Disable Automatic Rebooting, go to Start > Run and type: sysdm.cpl
Click Ok or just press WINKEY + Pause/Break keys to bring up System Properties.
  • Go to the Advanced tab and under "Startup and Recovery", click on the "Settings" button and go to "System failure".
  • Make sure "Write an event to the system log" is checked and that "Automatically restart" is UNchecked.
  • Click "OK" and reboot for the changes to take effect.
Doing this won't cure your problem but instead of crashing and restarting you will get a blue diagnostic screen with an error code and other information that will allow you to better trace your problem. You can use Google to search the error code or use the links below to investigate and troubleshoot.

"Extract troubleshooting info from Windows XP BSOD error messages".
"How to Find BSOD Error Messages".
"Events and Errors Message Center".
"Windows XP Professional Error Messages".
"Troubleshooting Windows Stop Messages".

Other Troubleshooting Tools:

Download and run Motherboard Monitor 5. If Motherboard Monitor's seems to be reporting high temperatures for your CPU check to see what your max CPU temp is from here.

You can also use NextSensor to check temperature and voltage or SpeedFan to monitor voltages, fan speed, SMART status, and temperatures. SpeedFan can help you investigate the reasons for an unpredictable reboot or for a failing hard disk as well as whether you are likely to experience temperature related issues.

There are suggestions for troubleshooting power supply, video card, CPU, RAM, MB and hard drive here and here.

You can use BurnInTest to stress test the CPU, hard drives, RAM, CD-ROMs, CD burners, DVDs, sound cards, graphics, network connection, printers, video playback. This utility works on all Windows versions to include Vista (32-bit & 64-bit).

Another option is to use Microsoft's Online Crash Analysis. The Windows Memory Diagnostic tests the RAM for errors with a comprehensive set of diagnostic memory tests or you can test your RAM with either of the following tools:

Memtest86+ and follow the instructions to Diagnose with Memtest86+.
Once a bootable disk is made, just leave it in the drive and reboot your computer. However, before rebooting, you need to enter the BIOS setup and make sure that the Boot Order is set so that your first boot device is either the floppy drive or the CD-ROM drive, depending on which type of disk you made. If necessary, change the boot order, save your changes, and exit Setup. When the machine restarts it should boot from your Memtest disk, and the program will start automatically.

Download ISO images for creating a bootable Memtest86 CD-ROM or an installable from Windows/DOS to create a bootable floppy disk or usb flash drive. Read the directions under Technical Info and allow Memtest86 to run through the entire battery of tests for at least 4 full passes (or let it run overnight). Any errors indicate that there is likely a problem with your physical memory (RAM).

Note" If you need to replace your RAM and unsure what type you current have, then use the Crucial System Scanner.

Finally, look for problem entries in Device Manager and check if updates are available for your drivers.
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users