computer reboots suddenly

My computer reboots frequently- suddenly and unexpectedly, even if I not work on computer at the moment. What can be the reason? Is this PC Power
supply problem? Or room power supply?
I looked at event system logs(eventvwr.exe), there are 2 main errors
repeated: Event ID: 17 and 29.
Is there some connection with PC rebooting or not? If so, how I can correct
problem?

 

What is the source?

 

what do you meant?

 

What are the details of the errors? Double click on the event to see them. Also, right click on my computer, choose properties>advanced and click the settings button by startup and recovery. Under system failure, uncheck the line that says automatically restart. After doing this, if windows is crashing, instead of restarting you should get a blue screen with the details of the error.

 

Today it works normally, it seems. But yesterday there are was few rebooting
unexpected. Also, there was a problem with internet connection yesterday.

main errors log
------------------------------------

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:11:16
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:11:16
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------------

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:11:32
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:11:32
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:26:32
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 30 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:26:32
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 29 minutes. NtpClient has no source of accurate time.

-----------------------
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 2005.02.08.
Time: 18:37:50
User: N/A
Computer: NIK
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000166, 0x00000002, 0x00000000, 0x804e59c3). A dump was saved in: C:\WINDOWS\Minidump\Mini020805-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:38:21
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
---------------------------

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:38:21
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:38:36
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:38:36
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----------------
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2005.02.08.
Time: 18:39:33
User: N/A
Computer: NIK
Description:
The Remote Access Connection Manager service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 18:53:36
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 30 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 18:53:36
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 29 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 2005.02.08.
Time: 19:23:36
User: N/A
Computer: NIK
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 60 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------------
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 2005.02.08.
Time: 19:23:36
User: N/A
Computer: NIK
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 59 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

What did you find out?

I've been experiencing the sudden reboot problem too. Did you find a resolution?
Thanks.

 

Note to anyone reading this thread - you will see one very good reason why it helps us help you when you specify your general location

The w32time errors will not cause a system crash. In fact, other than not being able to update your PC's time by getting a time tic from a time server, it will have zero effect on the system.

Still, no sense in letting that particular error keep showing up so I'd suggest one of two things:
1. configure your PC to look for an internet time server that exists and if you are on dial-up, to do so at a time when you will probably be on line
2. stop and disable the w32time service

How-to
2. Click on start, on run, key in services.msc and ok. When the services list displays, locate "windows time ", right-click it and click Stop, right-click again and click Properties then set startup to disabled.

1. I think you are UK based and if so, pick any time server from the list below. Closest to you is good. US users should google search for internet time servers and pick a US based one in their area.

1.1. (I like doing this from a cmd prompt) Click on start, on run, key in cmd and click OK.

1.2 From the cmd prompt (and substitute any server name for the one I show in the example) you want to point your PC to the proper server, stop time service, start time service.

Code:

net time /setsntp:ntp1.uk.uu.net

net stop w32time

net start w32time

And a list of UK time servers

Code:

British Isles

• Dublin, Ireland: School of Mathematics, 
Trinity College 
ntp.cs.tcd.ie; ntp.maths.tcd.ie; ntp.tcd.ie
Service Area: Ireland and U.K.  

• Glasgow, Scotland: Strathclyde University 
ntp.cs.strath.ac.uk 
Service Area: U.K., Europe, and any  

• Cambridge, U.K.
ntp0.uk.uu.net; ntp1.uk.uu.net; 
ntp2.uk.uu.net 
Service Area: UUNET (formerly known in the 
U.K. as PIPEX) and U.K.  

• Manchester, England: University of Manchester
ntp2a.mcc.ac.uk; ntp2b.mcc.ac.uk;
ntp2c.mcc.ac.uk; ntp2d.mcc.ac.uk 
Service Area: U.K.  

• Buckinghamshire U.K.: Wibble U.K., Aylesbury
tick.tanac.net
Service area: U.K.  

 

kenton - re: your rebooting issue, you probably are looking at
- bad house current and that will need a UPS to correct
- failing or indequate power supply and that would need a replacement
- heat build up (not likely if symptoms are as you describe)

Can you give more detail?

 

This one is the source of the problem.

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 2005.02.08.
Time: 18:37:50
User: N/A
Computer: NIK
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000166, 0x00000002, 0x00000000, 0x804e59c3). A dump was saved in: C:\WINDOWS\Minidump\Mini020805-02.dmp.

Have a look at Joe's instructions on this page.
http://www.windowsbbs.com/showthread.php?t=33471
Download the tools he's linked to and run that dump through them. I don't know if it's best to start a new thread or continue on here. I guess if it were me I'd start a new one as Joe says with memory dump in the title. That way somebody who knows how to read the dump will be more apt to spot it. One of the mods will merge the thread back with this one if they think it appropriate. Maybe Newt will see this before you post again and be able to tell you which way to go.

 

Good catch Zander. I looked at the first half-dozen w32time errors and didn't closely examine the rest. Missed that bug check completely.