Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Win XP will not shutdown, always does a restart instead


  • Please log in to reply

#1
KenPC

KenPC

    Member

  • Member
  • PipPip
  • 43 posts
hi ... I am unable to shut down Win XP (with SP2 and SP3 installed plus all of the current Microsoft updates) using the "shutdown" mouse click button on my HP m1160n desktop (AMD Athlon 3400 64-bit processor, 2GB RAM, 200GB disk). The only way I can power down is to push the power button and hold it for about 5 seconds. Additionally, when ever I do a shutdown (restart) I get a message that says "The system has recovered from a serious error" that also asks if I want to send a dump to Microsoft. Yesterday I installed the "new" Microsoft "fix-it center" to see if that would resolve anything, but no improvement. In antisipation of the next step, I downloaded VIEW.EXE and have attached the log below. Any help would be greatly appreciated.

Vino's Event Viewer v01c run on Windows XP in English
Report run at 10/06/2010 16:15:02

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/06/2010 12:02:34
Type: error Category: 0
Event: 15 Source: MatSvc
The scheduled MATS task encountered a failure when collecting configuration data. hr=0x803C0101 .

Log: 'Application' Date/Time: 10/06/2010 12:02:33
Type: error Category: 0
Event: 9 Source: MatSvc
The MATS service encountered a failure when diagnosing problems. hr=0x803C0101 SAP folder: C:\Program Files\Microsoft Fix it Center\SAPFolder\Scheduled\DDA435FA-6E05-4DBF-80FE-C4EBE882E798.18

Log: 'Application' Date/Time: 10/06/2010 10:53:43
Type: error Category: 0
Event: 15 Source: MatSvc
The scheduled MATS task encountered a failure when collecting configuration data. hr=0x803C0101 .

Log: 'Application' Date/Time: 10/06/2010 10:53:42
Type: error Category: 0
Event: 9 Source: MatSvc
The MATS service encountered a failure when diagnosing problems. hr=0x803C0101 SAP folder: C:\Program Files\Microsoft Fix it Center\SAPFolder\Scheduled\DDA435FA-6E05-4DBF-80FE-C4EBE882E798.18

Log: 'Application' Date/Time: 10/06/2010 10:40:58
Type: error Category: 0
Event: 15 Source: MatSvc
The scheduled MATS task encountered a failure when collecting configuration data. hr=0x803C0101 .

Log: 'Application' Date/Time: 10/06/2010 10:40:56
Type: error Category: 0
Event: 9 Source: MatSvc
The MATS service encountered a failure when diagnosing problems. hr=0x803C0101 SAP folder: C:\Program Files\Microsoft Fix it Center\SAPFolder\Scheduled\DDA435FA-6E05-4DBF-80FE-C4EBE882E798.18

Log: 'Application' Date/Time: 09/06/2010 15:21:32
Type: error Category: 0
Event: 15 Source: MatSvc
The scheduled MATS task encountered a failure when collecting configuration data. hr=0x803C0101 .

Log: 'Application' Date/Time: 09/06/2010 15:21:32
Type: error Category: 0
Event: 9 Source: MatSvc
The MATS service encountered a failure when diagnosing problems. hr=0x803C0101 SAP folder: C:\Program Files\Microsoft Fix it Center\SAPFolder\Scheduled\DDA435FA-6E05-4DBF-80FE-C4EBE882E798.18

Log: 'Application' Date/Time: 09/06/2010 09:32:01
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application OUTLOOK.EXE, version 11.0.8312.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: The specified server cannot perform the requested operation.

Log: 'Application' Date/Time: 08/06/2010 18:03:33
Type: error Category: 0
Event: 8 Source: crypt32
Failed auto update retrieval of third-party root list sequence number from: <http://www.download....uthrootseq.txt> with error: This operation returned because the timeout period expired.

Log: 'Application' Date/Time: 08/06/2010 09:30:58
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application OUTLOOK.EXE, version 11.0.8312.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Log: 'Application' Date/Time: 07/06/2010 12:32:48
Type: error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 252568984

Log: 'Application' Date/Time: 07/06/2010 12:32:48
Type: error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 252568984

Log: 'Application' Date/Time: 07/06/2010 12:32:48
Type: error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 59 Source: SideBySide
Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80U.DLL. Reference error message: The operation completed successfully. .

Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 59 Source: SideBySide
Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system. .

Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 32 Source: SideBySide
Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.

Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 59 Source: SideBySide
Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80U.DLL. Reference error message: The operation completed successfully. .

Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 59 Source: SideBySide
Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system. .

Log: 'System' Date/Time: 10/06/2010 16:14:25
Type: error Category: 0
Event: 32 Source: SideBySide
Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 59 Source: SideBySide
Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80U.DLL. Reference error message: The operation completed successfully. .

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 59 Source: SideBySide
Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system. .

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 32 Source: SideBySide
Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 59 Source: SideBySide
Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80U.DLL. Reference error message: The operation completed successfully. .

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 59 Source: SideBySide
Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system. .

Log: 'System' Date/Time: 10/06/2010 16:08:05
Type: error Category: 0
Event: 32 Source: SideBySide
Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.

Log: 'System' Date/Time: 10/06/2010 12:03:02
Type: error Category: 0
Event: 10010 Source: DCOM
The server {209500FC-6B45-4693-8871-6296C4843751} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 10/06/2010 12:02:31
Type: error Category: 0
Event: 10010 Source: DCOM
The server {209500FC-6B45-4693-8871-6296C4843751} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 10/06/2010 12:02:28
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000007e, parameter1 c0000005, parameter2 8062e37e, parameter3 ba4e3bc8, parameter4 ba4e38c4.

Log: 'System' Date/Time: 10/06/2010 12:02:24
Type: error Category: 0
Event: 10016 Source: DCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 10/06/2010 10:54:24
Type: error Category: 0
Event: 10010 Source: DCOM
The server {209500FC-6B45-4693-8871-6296C4843751} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 10/06/2010 10:54:24
Type: error Category: 0
Event: 10010 Source: DCOM
The server {3A185DDE-E020-4985-A8F2-E27CDC4A0F3A} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 10/06/2010 10:53:35
Type: error Category: 0
Event: 10016 Source: DCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 10/06/2010 10:53:26
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000007e, parameter1 c0000005, parameter2 8062e37e, parameter3 ba4dfbc8, parameter4 ba4df8c4.
  • 0

Advertisements


#2
silverbeard

silverbeard

    Trusted Tech

  • Member
  • PipPipPip
  • 791 posts
Hi Ken,

Try going to Start> right click on My Computer and go to Properties. Go to the Advanced go to Startup and Recovery. In the section labeled System Failure uncheck the three boxes. Under Write debugging information set the drop down to none.

This should take it out of the automatic restart mode.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP