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.

Photo

Laptop randomly restarts


  • This topic is locked This topic is locked
22 replies to this topic

#1 domi1127

domi1127

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 24 December 2010 - 08:59 PM

So while I'm using my laptop my computer just randomly restarts. My battery is full and its plugged in so I'm really not sure why it keeps doing it. The laptop will restart to a screen that says "Windows Did Not Shut Down Successfully" and let me choose to start Windows normally or in different Safe Modes. I've run scans multiple times but no virus shows up. Its very annoying and any help is apperciated, thanks.

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 24 December 2010 - 11:06 PM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 25 December 2010 - 12:30 AM

Alright here you go...
==================================================
Dump File : 120610-19812-01.dmp
Crash Time : 12/6/2010 1:54:28 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x8652f828
Parameter 4 : 0x83b6fb24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67966
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\120610-19812-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 260,968
==================================================

==================================================
Dump File : 091510-25053-01.dmp
Crash Time : 9/15/2010 1:46:02 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x40af8c51
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x936436f6
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+226f6
File Description : ATI Radeon Kernel Mode Driver
Product Name : ATI Radeon Family
Company : ATI Technologies Inc.
File Version : 8.01.01.921
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\091510-25053-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 144,048
==================================================

==================================================
Dump File : 032310-20560-01.dmp
Crash Time : 3/23/2010 10:54:23 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85b86920
Parameter 4 : 0x83163b24
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\032310-20560-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 234,952
==================================================

==================================================
Dump File : 031810-30950-01.dmp
Crash Time : 3/18/2010 4:02:12 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85b86648
Parameter 4 : 0x83168b24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67a66
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031810-30950-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 234,952
==================================================

==================================================
Dump File : 022810-18298-01.dmp
Crash Time : 2/28/2010 4:02:11 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85786648
Parameter 4 : 0x82f3cb24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67a66
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022810-18298-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 234,952
==================================================

==================================================
Dump File : 022110-17784-01.dmp
Crash Time : 2/21/2010 12:12:53 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85786920
Parameter 4 : 0x82f36b24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67a66
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\022110-17784-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 247,936
==================================================

==================================================
Dump File : 021510-18735-01.dmp
Crash Time : 2/15/2010 2:27:11 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85786920
Parameter 4 : 0x82d3db24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67a66
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021510-18735-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 234,952
==================================================

==================================================
Dump File : 021310-19843-01.dmp
Crash Time : 2/13/2010 3:07:57 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x8572e798
Parameter 4 : 0x82d2bb24
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\021310-19843-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 247,984
==================================================

==================================================
Dump File : 020710-23368-01.dmp
Crash Time : 2/7/2010 2:56:21 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85786648
Parameter 4 : 0x82d6fb24
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\020710-23368-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 247,984
==================================================

==================================================
Dump File : 020310-27955-01.dmp
Crash Time : 2/3/2010 2:10:16 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x8572ed48
Parameter 4 : 0x82d37b24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67966
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\020310-27955-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 234,952
==================================================

==================================================
Dump File : 013110-21949-01.dmp
Crash Time : 1/31/2010 2:55:19 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85736a70
Parameter 4 : 0x82d43b24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67966
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\013110-21949-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 247,984
==================================================

==================================================
Dump File : 012610-18314-01.dmp
Crash Time : 1/26/2010 2:21:57 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 0x00000004
Parameter 2 : 0x00000258
Parameter 3 : 0x85786020
Parameter 4 : 0x82d78b24
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+67966
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\012610-18314-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 235,000
==================================================

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 25 December 2010 - 11:03 AM

There is nothing recent there...

Download System Information for Windows (SIW free version)
No installation required.

After it scans your computer, navigate to Hardware>Sensors and post all info from there.

Posted Image

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 25 December 2010 - 02:15 PM

Yeah thats very weird because it's happened about 4-5 times this week. But couldn't figure how to copy the info so i took a screen shot, heres the info thanks.

Edited by domi1127, 25 December 2010 - 02:16 PM.


#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 25 December 2010 - 05:13 PM

Those look fine for a laptop....

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select:
Application
System


Under Select type to list, select:
Critical (Vista only)
Error


Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#7 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 25 December 2010 - 06:19 PM

Alright here ya go

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 25/12/2010 6:16:47 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/11/2009 8:20:23 PM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (VirusScan 8, from vendor McAfee) was hard-blocked and raised the following: VirusScan 8 has a known compatibility issue with this version of Windows.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 25/12/2010 9:23:19 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
496: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 9:23:19 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
192: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 9:23:19 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
332: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 7:20:56 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
512: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 7:20:56 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
472: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 7:20:56 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
468: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 6:10:06 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 8112

Log: 'Application' Date/Time: 25/12/2010 6:10:06 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 8112

Log: 'Application' Date/Time: 25/12/2010 6:10:06 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second

Log: 'Application' Date/Time: 25/12/2010 7:21:35 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
512: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 7:21:35 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
192: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 7:21:35 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
504: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 3:56:48 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
504: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 3:56:48 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
192: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 25/12/2010 3:56:48 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
196: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 24/12/2010 8:17:13 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
468: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 24/12/2010 8:17:13 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
472: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 24/12/2010 7:25:25 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
196: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 24/12/2010 7:25:25 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
456: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 24/12/2010 7:25:25 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
496: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/12/2010 1:30:09 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 24/12/2010 12:41:41 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 23/12/2010 12:38:12 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 22/12/2010 1:27:44 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 21/12/2010 3:54:27 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 19/12/2010 9:14:35 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 19/12/2010 1:09:27 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 17/12/2010 8:31:09 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/12/2010 9:28:37 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/12/2010 9:05:00 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/12/2010 9:34:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/12/2010 7:33:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/12/2010 10:42:15 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/12/2010 4:33:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/12/2010 6:13:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/12/2010 2:07:46 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/12/2010 6:54:14 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 26/11/2010 5:12:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 25/11/2010 5:34:13 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 24/11/2010 4:23:10 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/12/2010 11:05:25 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 11:05:25 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 25/12/2010 7:58:26 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 7:58:26 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 25/12/2010 7:15:29 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D3DCB472-7261-43CE-924B-0704BD730D5F} and APPID {D3DCB472-7261-43CE-924B-0704BD730D5F} to the user Michael-PC\Michael SID (S-1-5-21-2514709491-1617148195-620187525-1001) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 25/12/2010 7:15:29 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {145B4335-FE2A-4927-A040-7C35AD3180EF} and APPID {145B4335-FE2A-4927-A040-7C35AD3180EF} to the user Michael-PC\Michael SID (S-1-5-21-2514709491-1617148195-620187525-1001) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 25/12/2010 6:43:51 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 6:43:48 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {B2B3C70A-B20F-40B7-90C5-EA7E946C16E0} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 25/12/2010 6:06:09 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 6:06:09 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 25/12/2010 9:52:02 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 9:52:02 AM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 25/12/2010 3:55:27 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Search service hung on starting.

Log: 'System' Date/Time: 25/12/2010 3:52:48 AM
Type: Error Category: 0
Event: 14332 Source: Microsoft-Windows-WMPNSS-Service
Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80004005'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.

Log: 'System' Date/Time: 25/12/2010 3:49:41 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 25/12/2010 3:49:41 AM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 25/12/2010 1:37:00 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.

Log: 'System' Date/Time: 25/12/2010 1:33:34 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {063D34A4-BF84-4B8D-B699-E8CA06504DDE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 25/12/2010 1:33:06 AM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The iPod Service service terminated with the following error: %%-2147417831

Log: 'System' Date/Time: 25/12/2010 1:30:17 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

#8 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 25 December 2010 - 09:30 PM

Unfortunately, critical errors section doesn't give us too many details:

Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


However, there is a lot of errors (couple of them per hour) involving video driver (atikmdag).

Download fresh video driver, uninstall current one and install new one.
See, if it helps any.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#9 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 26 December 2010 - 01:41 PM

Alright I uninstalled the video driver and downloaded the driver. I restarted my computer though and it installed a driver for me, not sure if it was the one i downloaded. But should this fix my problem?

#10 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 26 December 2010 - 02:25 PM

not sure if it was the one i downloaded

See, if you don't have any errors in Device Manager>Display Adapters section.

But should this fix my problem?

I don't know. Run the computer for a while and see how it goes.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#11 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 26 December 2010 - 04:23 PM

Yeah everything seems fine with the installment, and thank you I'll let you know if it works

#12 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 26 December 2010 - 04:24 PM

Cool :)

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#13 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 28 December 2010 - 10:36 PM

Alright so it doesn't randomly restart now, but my computer has froze 3 time since I've installed the driver :\

#14 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,616 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:01:51 PM

Posted 28 December 2010 - 10:47 PM

Post new VEW log.

Also...

Download System Information for Windows (SIW free version)
No installation required.

After it scans your computer, navigate to Hardware>Sensors and post all info from there.

Posted Image

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#15 domi1127

domi1127
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:03:51 PM

Posted 29 December 2010 - 12:03 AM

K here they are, I attached the senosors one again thanks.
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 28/12/2010 11:56:47 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/11/2009 8:20:23 PM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (VirusScan 8, from vendor McAfee) was hard-blocked and raised the following: VirusScan 8 has a known compatibility issue with this version of Windows.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/12/2010 3:48:56 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
504: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 3:48:56 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
196: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 3:48:56 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
192: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 1:42:03 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
196: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 1:42:03 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
516: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 1:42:03 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
332: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 12:15:29 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
512: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 12:15:29 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
372: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 29/12/2010 12:15:29 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
332: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:45:07 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
504: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:45:07 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
372: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:45:07 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
468: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 7:47:20 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
504: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 7:47:20 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
196: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 7:47:20 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
192: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:12:17 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
372: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:12:17 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
332: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:12:17 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
472: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 10:12:16 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
468: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)

Log: 'Application' Date/Time: 28/12/2010 6:50:04 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: LWS.exe, version: 12.10.1113.0, time stamp: 0x4ad63566 Faulting module name: LWS.exe, version: 12.10.1113.0, time stamp: 0x4ad63566 Exception code: 0xc000000d Fault offset: 0x000d2aaa Faulting process id: 0xdd8 Faulting application start time: 0x01cba65b6a12e274 Faulting application path: C:\Program Files\Logitech\Logitech WebCam Software\LWS.exe Faulting module path: C:\Program Files\Logitech\Logitech WebCam Software\LWS.exe Report Id: b25f242a-124e-11e0-aa76-cfece0f055e1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/12/2010 3:26:07 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 28/12/2010 1:36:28 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 27/12/2010 6:58:58 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 26/12/2010 7:51:12 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 25/12/2010 1:30:09 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 24/12/2010 12:41:41 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 23/12/2010 12:38:12 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 22/12/2010 1:27:44 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 21/12/2010 3:54:27 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 19/12/2010 9:14:35 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 19/12/2010 1:09:27 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 17/12/2010 8:31:09 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/12/2010 9:28:37 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/12/2010 9:05:00 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/12/2010 9:34:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/12/2010 7:33:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/12/2010 10:42:15 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/12/2010 4:33:03 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/12/2010 6:13:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/12/2010 2:07:46 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/12/2010 3:32:12 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.

Log: 'System' Date/Time: 29/12/2010 3:26:14 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 29/12/2010 3:26:14 AM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 29/12/2010 3:26:16 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 10:24:30 PM on ?12/?28/?2010 was unexpected.

Log: 'System' Date/Time: 28/12/2010 10:35:37 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 28/12/2010 10:35:37 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 28/12/2010 7:38:44 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 28/12/2010 7:38:44 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 28/12/2010 6:54:27 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.

Log: 'System' Date/Time: 28/12/2010 6:48:49 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 28/12/2010 6:48:49 AM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 28/12/2010 1:41:38 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Update service hung on starting.

Log: 'System' Date/Time: 28/12/2010 1:36:35 AM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 28/12/2010 1:36:35 AM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 28/12/2010 1:36:35 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 8:33:22 PM on ?12/?27/?2010 was unexpected.

Log: 'System' Date/Time: 27/12/2010 7:56:27 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {063D34A4-BF84-4B8D-B699-E8CA06504DDE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 27/12/2010 7:56:02 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The iPod Service service terminated with the following error: %%-2147417831

Log: 'System' Date/Time: 27/12/2010 7:54:01 PM
Type: Error Category: 42
Event: 43029 Source: atikmdag
Display is not active

Log: 'System' Date/Time: 27/12/2010 7:54:01 PM
Type: Error Category: 51
Event: 52236 Source: atikmdag
CPLIB :: General - Invalid Parameter

Log: 'System' Date/Time: 27/12/2010 6:45:53 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {063D34A4-BF84-4B8D-B699-E8CA06504DDE} did not register with DCOM within the required timeout.

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users