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

Computer Randomly Freezing Up When Gaming


  • Please log in to reply
22 replies to this topic

#1 Oninuva

Oninuva

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 11 August 2011 - 10:44 AM

Hi guys my computer has been freezing up a lot lately when playing World of Warcraft. I tried replacing the graphic card, previously I had a 8800GT so I swapped it out for a 250 GTS but still having problems.

Computer Specs:

Intel E8400 3.0ghz
4GB RAM
nvidia 250gts
460watts powersupply
asus p5n-e sli

I've been running with speedfan on to monitor temperature and the peak is around 60C with average around 54C. Any ideas to how I could diagnose the problem? I can't seem to recreate the crash, but it will crash randomly during the game, and CPU usage can get close to 100% even when running such an old game. Thanks!

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 11 August 2011 - 07:49 PM

I've been running with speedfan on to monitor temperature and the peak is around 60C with average around 54C

While idle?
Max temp for your CPU is listed at 72.4C.

My Website

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

 


#3 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 12 August 2011 - 01:43 PM

Idle is at 40C

#4 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 12 August 2011 - 01:48 PM

I think it's too hot though even at Idle? Room is air conditioned and I have even tried opening the case have a fan blow cold air into it but it's still really hot.

#5 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 12 August 2011 - 02:27 PM

Get a can of compressed air and clean well inside (while computer off), paying extra attention to all fans.

My Website

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

 


#6 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 13 August 2011 - 07:51 AM

Did that last night and started it up but computer still froze as soon as I started up the game, no longer than 5 minutes in. When it freezes I can still see everything on the screen but there is just no response to anything. If there as any music or sound playing then the speakers will make a weird buzzing sound until I restart or shut off the computer. Temperature was at 55C when it crashed this time.

#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 13 August 2011 - 10:39 AM

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

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

 


#8 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 13 August 2011 - 01:22 PM

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 13/08/2011 2:19:46 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 13/08/2011 6:19:09 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0xabc Faulting application start time: 0x01cc59e57e256ad0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: bca6ba70-c5d8-11e0-bf1d-0060085a576a

Log: 'Application' Date/Time: 13/08/2011 5:21:28 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1588 Faulting application start time: 0x01cc59dd6e987f10 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: ad8b2650-c5d0-11e0-9e8f-001fc63849fb

Log: 'Application' Date/Time: 13/08/2011 12:41:05 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1590 Faulting application start time: 0x01cc59b6435e1160 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 8206ee00-c5a9-11e0-bf86-001fc63849fb

Log: 'Application' Date/Time: 13/08/2011 3:22:00 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1214 Faulting application start time: 0x01cc596827924530 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 67839f90-c55b-11e0-8061-001fc63849fb

Log: 'Application' Date/Time: 13/08/2011 3:11:32 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x139c Faulting application start time: 0x01cc5966b23a01c0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: f1552060-c559-11e0-bf30-001fc63849fb

Log: 'Application' Date/Time: 12/08/2011 6:37:42 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1504 Faulting application start time: 0x01cc591eea74bdc0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 2969c660-c512-11e0-9f2a-001fc63849fb

Log: 'Application' Date/Time: 12/08/2011 6:28:01 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x16b0 Faulting application start time: 0x01cc591d8fe39c60 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: cf283c00-c510-11e0-bb1a-001fc63849fb

Log: 'Application' Date/Time: 12/08/2011 2:02:59 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x15ac Faulting application start time: 0x01cc58f889db2560 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: c8cdcca0-c4eb-11e0-bf89-001fc63849fb

Log: 'Application' Date/Time: 12/08/2011 3:01:41 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x10b0 Faulting application start time: 0x01cc589c27a87660 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 6690ec40-c48f-11e0-bc56-0060085a576a

Log: 'Application' Date/Time: 12/08/2011 12:16:08 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1548 Faulting application start time: 0x01cc588506be30a0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 4646ce80-c478-11e0-bf29-0060085a576a

Log: 'Application' Date/Time: 11/08/2011 6:24:57 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x12a8 Faulting application start time: 0x01cc5853f89fa660 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 371b48e0-c447-11e0-bc70-001fc63849fb

Log: 'Application' Date/Time: 11/08/2011 4:02:33 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\program files\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 11/08/2011 4:02:06 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 11/08/2011 3:39:51 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1588 Faulting application start time: 0x01cc583ce62e5d30 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 268b71b0-c430-11e0-bb86-001fc63849fb

Log: 'Application' Date/Time: 11/08/2011 3:23:34 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x158c Faulting application start time: 0x01cc583aa0edcbe0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: e02f0080-c42d-11e0-be61-001fc63849fb

Log: 'Application' Date/Time: 11/08/2011 12:40:36 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0xeb4 Faulting application start time: 0x01cc57bf46c83630 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 86c74c30-c3b2-11e0-bb23-001fc63849fb

Log: 'Application' Date/Time: 10/08/2011 10:55:53 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x1264 Faulting application start time: 0x01cc57b0a683b5e0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: e59ed480-c3a3-11e0-bbe1-001fc63849fb

Log: 'Application' Date/Time: 10/08/2011 3:37:02 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x114c Faulting application start time: 0x01cc57735779ee70 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 95277350-c366-11e0-bfbc-001fc63849fb

Log: 'Application' Date/Time: 10/08/2011 3:36:38 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x178c Faulting application start time: 0x01cc57734a123ad0 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 88dd8bc0-c366-11e0-bfbc-001fc63849fb

Log: 'Application' Date/Time: 10/08/2011 3:26:04 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Faulting module name: daemonu.exe, version: 1.1.34.0, time stamp: 0x4d9e7788 Exception code: 0xc000000d Fault offset: 0x0005af13 Faulting process id: 0x15f4 Faulting application start time: 0x01cc5771d0aae760 Faulting application path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Faulting module path: C:\Program Files\NVIDIA Corporation\NVIDIA Updatus\daemonu.exe Report Id: 0f5d4980-c365-11e0-bcad-001fc63849fb

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/08/2011 6:16:43 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/08/2011 3:19:39 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: 12/08/2011 6:35: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: 12/08/2011 6:25:41 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: 12/08/2011 2:59: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: 12/08/2011 12:13:39 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: 11/08/2011 6:22:32 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: 11/08/2011 3:37:25 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: 11/08/2011 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: 10/08/2011 10:53:41 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: 10/08/2011 7:31:42 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: 10/08/2011 4:29:44 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: 10/08/2011 3:34:10 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: 10/08/2011 3:23:39 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: 10/08/2011 4:20:30 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: 10/08/2011 12:53:19 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: 09/08/2011 12:19:36 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: 09/08/2011 12:01: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: 08/08/2011 6:10:33 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/08/2011 4:11: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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/08/2011 6:19:10 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 13/08/2011 6:18:06 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 13/08/2011 6:16:57 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:15:28 PM on ?8/?13/?2011 was unexpected.

Log: 'System' Date/Time: 13/08/2011 5:49:54 PM
Type: Error Category: 0
Event: 12 Source: Microsoft-Windows-HAL
The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.

Log: 'System' Date/Time: 13/08/2011 5:21:29 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 13/08/2011 5:20:24 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 13/08/2011 12:41:06 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 13/08/2011 12:40:02 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 13/08/2011 3:22:00 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 13/08/2011 3:20:54 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 13/08/2011 3:19:52 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 11:17:05 PM on ?8/?12/?2011 was unexpected.

Log: 'System' Date/Time: 13/08/2011 3:11:33 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 13/08/2011 3:10:28 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 12/08/2011 6:37:43 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 12/08/2011 6:36:38 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 12/08/2011 6:35:31 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:33:42 PM on ?8/?12/?2011 was unexpected.

Log: 'System' Date/Time: 12/08/2011 6:28:02 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 12/08/2011 6:26:57 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 12/08/2011 6:25:55 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:24:34 PM on ?8/?12/?2011 was unexpected.

Log: 'System' Date/Time: 12/08/2011 2:03:00 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).


Here are the results, thanks!

#9 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 13 August 2011 - 01:42 PM

Since it happens only during gaming, Event: 41 Source: Microsoft-Windows-Kernel-Power error may indicate some hardware issue.

Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287 (or http://www.bleepingcomputer.com/forums/index.php?showtopic=28744&hl=hard+drive+diagnostic)
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), to make the CD bootable.
For Toshiba hard drives, see here: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic

Note : If you do not know how to set your computer to boot from CD follow the steps HERE

===========================================================================

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

My Website

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

 


#10 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 13 August 2011 - 10:13 PM

Alright I did the diagnostics and got

Disposition Code = 0x00


So I believe the hard drive is OK? My computer starts fine with one stick of RAM as well.

#11 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 13 August 2011 - 10:17 PM

I suggest you run your computer with 1 RAM stick at a time for a few hours and see what happens.

My Website

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

 


#12 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 13 August 2011 - 10:45 PM

Alright should I try running any games? Or leave it idle.

#13 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 13 August 2011 - 11:40 PM

You can try some games.

My Website

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

 


#14 Oninuva

Oninuva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:01:51 AM

Posted 14 August 2011 - 04:57 PM

Alright running with one stick of ram, I had the game running for a couple of hours and no crash/freeze at all. Tried the other stick as well and same results, the first stick the pc was on a game for 3 1/2 hours, now this one is at 1 1/2 hours.

Would it be possible that the 2nd ram slot is damaged?

#15 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,759 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:09:51 PM

Posted 14 August 2011 - 05:09 PM

Try to put each RAM stick (one at a time) in the 2nd slot.

My Website

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

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users