BleepingComputer.com: Computer Crashing (Graphics Card?)

For the past week I've been having problems with my desktop. They have changed and develop over that time, so I'll list what's happened in hopes that somebody will be able to help me out. Running Windows 7, three year-old computer, 3GB RAM, 256MB Dedicated Memory nVidia Video Card, don't know what other details would be useful.

About a week ago, my desktop starting crashing when I played any game for too long -- specifically Heroes of Newerth. The entire screen would freeze, or turn black, and my speakers would repeat the last sound that had played -- usually a brzbrzbrzbrz annoying kind of noise.

If I left the computer off for a while, then tried to play, it would be fine. I assumed this meant there was a heating problem, but upon inspection of my fans everything seemed fine. This went on for a while until a few days ago, when I couldn't play a game for more than 2 minutes and even my desktop would crash after half an hour or so.
Now I can't do anything for more than a few seconds. I'll even get a BSoD occasionally now, making my computer basically unusable. The exception, of course, is being in safe mode -- which I'm in now.

I'm thinking my graphics card is going bad, but by the way my entire computer crashes... I'm not sure. Any help, gentlemen?

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.



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

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.

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

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.

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 21/05/2011 9:45:59 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 20/05/2011 12:24:15 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: 18/05/2011 10:01:18 PM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. 

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {46548b1f-a11e-44e6-8f38-50b4e411b310}

Log: 'Application' Date/Time: 13/05/2011 11:59:33 PM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. 

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {5f241d02-cda2-4247-ae14-a3b6eebd13d6}

Log: 'Application' Date/Time: 13/05/2011 4:14:01 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:13:58 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:46 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:46 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:38 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:38 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:28 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:24 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:24 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0

==================================================
Dump File         : 051211-29936-01.dmp
Crash Time        : 5/13/2011 12:41:57 AM
Bug Check String  : 
Bug Check Code    : 0x00000124
Parameter 1       : 0x00000000
Parameter 2       : 0x8550501c
Parameter 3       : 0xb2000040
Parameter 4       : 0x00000800
Caused By Driver  : halmacpi.dll
Caused By Address : halmacpi.dll+ef3f
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\051211-29936-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 156,056
==================================================

This post has been edited by BarrettomaL: 21 May 2011 - 08:49 PM

Also worth noting that the heat of my nVidia GeForce 8500 GT has raised from 56 degrees Celcius to 69 degrees Celcius in the past 5-10 minutes. Not a good sign, eh?

There are no any recent errors listed.
Are you sure, the VEW log is complete?
Usually there are some system errors listed, unless you didn't have any.

Try to play one of your games and post another screenshot from SIW.

69C for video card is not alarming, yet.

Playing a game right now, no crash yet. Current settings:

WOW!
Shut down that game right away.
You're greatly overheating and you may cause very serious CPU damage.
Your CPU max temp is listed at 60.3C
You go way over.

Get a can of compressed air and clean the computer inside the case.
Check, if all fans are running.

Already beat you to the compressed air. Cleaned the whole thing out, and the only two fans I can see -- one on top of the graphics card, the other attached to one of the desktop's vents -- are both running. No dust, two running fans. But the computer is making a louder humming noise than usual. Don't know what to do. ;\

The inside of the computer smells... warm, too. A bit like burnt metal, but not too bad. Still not crashing, and everything's running normally at the moment.

Present state of affairs:

Shut it down until you solve the issue. It's still over 70C...way too high.
You may need to reapply thermal paste, or/and install some extra fan.

Okay, thanks for the help. I'm shutting it down for the night, probably running off to the store tomorrow to see what I can get for it. Any quick advice on what exactly I should be looking for? I'm no computer novice, but I've never had a heating problem before. Thermal gel? Something like that?

Thank you for your help! I really appreciate it.

See here for the manual: http://www.arcticsilver.com/instructions.htm

Computer crashed again this morning, only a few minutes after turning it on. Here's my VEW log again:

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 22/05/2011 10:02:02 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 20/05/2011 12:24:15 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: 18/05/2011 10:01:18 PM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. 

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {46548b1f-a11e-44e6-8f38-50b4e411b310}

Log: 'Application' Date/Time: 13/05/2011 11:59:33 PM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. 

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {5f241d02-cda2-4247-ae14-a3b6eebd13d6}

Log: 'Application' Date/Time: 13/05/2011 4:14:01 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:13:58 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:46 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:46 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:38 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 4:01:38 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:28 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:24 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:55:24 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:50 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:33 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:50:33 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 13/05/2011 3:49:55 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\PROGRA~1\MICROS~3\Office14\GROOVEEX.DLL". Dependent Assembly Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.08" could not be found. Please use sxstrace.exe for detailed diagnosis.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/05/2011 2:00:54 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: 21/05/2011 9:13:55 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: 21/05/2011 8:40:49 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: 21/05/2011 7:38: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: 21/05/2011 7:30: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: 21/05/2011 7:09:22 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: 21/05/2011 2:52:49 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: 21/05/2011 1:48: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: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device G:\ (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device J:\ (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device I:\ (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device H:\ (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device BARRETT'S I (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 21/05/2011 2:50:52 AM
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Log: 'System' Date/Time: 21/05/2011 2:44:31 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: 20/05/2011 11:44: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: 20/05/2011 1:52:14 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: 20/05/2011 1:45:35 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: 20/05/2011 1:02: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: 19/05/2011 11:37:02 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: 22/05/2011 2:01:49 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:49 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:49 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:37 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The HomeGroup Provider service depends on the Function Discovery Provider Host service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:25 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 22/05/2011 2:01:24 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}

Log: 'System' Date/Time: 22/05/2011 2:01:23 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030}

Log: 'System' Date/Time: 22/05/2011 2:01:21 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}

Log: 'System' Date/Time: 22/05/2011 2:01:15 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC}

Going to try to get some thermal gel soon and see how that works. Unless my problem isn't just heating?