computer reboots on its own

gj,

Just some suggestions:

New hardware could be causing "heat related" issues. (Motherboard chipset fans, heatsink, other fans, etc.) Have you tried removing the case cover, pointing a fan at the "inards" and running the computer for a while?

Is the power supply sufficient for the hardware you have installed. (400 watts, maybe more)

Depending on the amount of background programs you have running, they could be causing conflicts with each other. First, make sure that you have all the current audio, video, etc. drivers for the new operating system. Next, shut down all the unnecessary programs in "msconfig" and "services" by using the instructions and information at the links below:

http://www.pacs-portal.co.uk/startup_content.php

http://www.blackviper.com/WinXP/servicecfg.htm

Hope this helps.

Grif

1. The article [Q308427] states that an "event" is any significant occurrence in the system or in a program that requires users to be notified or an entry be added to one of three logs. The Event Log Service records application, security, and system events in Event Viewer that can help identify and diagnose the source of current system problems, or help predict potential system problems.

2. The article [Q314084] describes how to gather more information about an error message that appears on a blue screen but may not provide conclusive answers and may only point you to another problem. Using Pstat.exe, a Resource Kit utility run from the command line, you are given a picture of the processes and drivers that are currently running. By using the starting address in the "LoadAddr" column, you can match the exception address to the driver name nearest and is most likely the driver that called the exception.

3. Access the TechNet "Windows XP Events and Errors" page and enter either the "Source" or the "Error Code". -- the two most important items of information concerning an Event.

This is what the event log had to say about the shut downs. Any suggestions?

Details
Product: Windows Operating System
ID: 6009
Source: EventLog
Version: 5.2
Symbolic Name: EVENT_EventLogProductInfo
Message: Microsoft (R) Windows (R) %1 %2 %3 %4.

Explanation
The user restarted or shut down the computer by clicking Start or pressing CTRL+ALT+DELETE, and then clicking Shut Down. The message displays the Windows product information for the computer logging the message, including the product name, version, build number, service pack number, and operating system type.

Since my #3 reference does not turn up anything for either the source or ID, I'd have to assume this is nothing more than a simple event. There isn't anything I can find written about it for WinXP, but you might check the article [Q196452] for WinNT. Microsoft hasn't caught up with all the XP stuff yet, it appears.

I agree with the other posters suggestions and should be looked at.

Further, I suggest if you have a new system to verify in the bios what the "overtemp" setting is at and make sure its proper for your needs, but default is OK. Depending on where you locate your system can cause reduced air circultation if stuffed in a desk or just in general poor air circulation is available. Also, in the bios make sure that "remote wake-up" is OFF or atuned to your needs. Thus a telephone ring or electrical spike could cause the system to reboot as well as heat overtemp, these are common areas to check. Verify the cpu heatsink/fan is properly mounted. If you brought a separate HSF, that it is rated for that cpu installed.

good luck -----Willy

you don't say whether you are on cable, dsl, or satellite, or some other type of 'always on' type modem service, but I had this same problem with my satellite service modem. Their tech support had me right click my Local Connection 6 icon in Networks, choose Properties, Advanced...this normally is where the XP firewall is listed as being on or off. If it's turned on, go to the settings tab at the bottom, then click Add and enter your isp name (mine is Starband), your computer name, and in the tcp/ip area put in the port numbers you get from your isp for both lines, and in the UDP area do the same if you need them. (When I'm at winmx.com I have to enter their port numbers instead in the tcp/ip area by adding winmx to the list twice or I have difficulty connecting to anybody there and vice versa) so make sure the port numbers you enter are the correct for what you need. Once you do this, you can reboot the computer to make everything take effect.

My computer stopped rebooting once I entered the Starband port numbers of 1880 for UDP.

TONI