[MisterCorn]

So, I just inherited a fairly nice computer, and all is well and good, except that the computer will be in use, gaming, browsing, etc. and will all of a sudden just be booting up, as if it had been off and I had hit the power button. I don't even get the honor of a bsod.

Checked the error logs, nothing there besides for windows reporting it had not been shut down properly. Installed Speedfan, to watch temps, and I see the gpu (9800gtx+) idles at around 50c, and started up WoW and Frontlines: FoW to see where it went. WoW bumped temps up to about 80c, and FoW brings it to 95c+.

I am thinking heat issue, but then again, it does the same restart sometimes from a fresh startup, after having been off overnight. Maybe a chronic heat problem has fubar'd my card?

Thank you in advance!

[Advertisements]

Post the full specs of the system including PSU brand and wattage.

What are the CPU temps?

Post the temps and voltages from the BIOS.

Have you cleaned the heatsink/fans and vents with a can of compressed air?

[makinu1der2]

Post the full specs of the system including PSU brand and wattage.

What are the CPU temps?

Post the temps and voltages from the BIOS.

Have you cleaned the heatsink/fans and vents with a can of compressed air?

[MisterCorn]

Cooler Master Stacker case
EVGA 132-CK-NF78-A1 LGA 775 NVIDIA nForce 780i SLI ATX Intel Motherboard (http://www.newegg.co...N82E16813188024)
Core2Extreme X9770
4 Corsair 2GB sticks (CM2X2048-8500C5)
GeForce 9800GTX+ EVGA PN 512-P3-N871-AR
Seagate 1.5TB 7200rpm HDD
PSU - Chieftec CFT-750-14C 750W

CPU temps idle around 35c to full load 55c or so, it has a monstrous heatsink/fan on it, as well as massive airflow from the case itself.

I will post the bois info in a few minutes, did this first.

I am a nut for a dust free computer, I spray all my computers at least weekly.


Oh, also, all drivers/DirectX/Windows are updated frequently, latest was this afternoon. OS is Vista64 Ultimate.

Edited by MisterCorn, 17 October 2009 - 11:55 PM.

[MisterCorn]

CPU 42c
BOARD 31c
MCP 55c

CPU CORE 1.23v
CPU FSB 1.08v
MEMORY 1.85v
+3.3 3.22v
+3.3 dual 3.22V
+12 12.08v
+5 5.04v
+VBAT 3v

Is this what you were looking for?

[rshaffer61]

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
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), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.

Thanks to Broni for the instructions

[rshaffer61]

If you have more than one RAM module installed, try starting 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+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.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:



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



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:




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.



The following image is the test results area:



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

[MisterCorn]

So, nothing to say as of yet, have done everything I've been told, now the computer knows it's being watched and won't die... Although now it has locked up, black screen, without restarting, have to power down then turn back on, no errors found on it... Will reply when I have more information.

[rshaffer61]

How did the memory test come out?
Any errors?
How long has it run without a problem now?

[MisterCorn]

I have 4, 2GB sticks of ram. I have run each of them solo for 4 hours each. I have encountered nothing out of the ordinary, gameplay is affected by the drop from 8GB to 2GB, but nothing spectacular.

Should I run Memtest with all 4 sticks in?

It has run for about 3 days now, with no crashes like I described, however, it has learned a new trick. Instead of a simple restart, it will now go blackscreen on me, without restarting, and I have no way of knowing if it is just the display going black of the machine locking up.

Thanks again for the assistance. Very much.

[rshaffer61]

Since individual sticks checked out then I would assume the memory is ok.
Since we have now taken the memory out of the picture and the system seems tobe working correctly then can you tell me for the 3 days has all 8 gigs of memory has been ion the system this full time other then for testing?
Check display properties and see if the display is set to go to a black screen instead of screensaver. Also check to see if it goes into power down mode in the power options.
This may be the issue with that.
II will await your results and response.

[MisterCorn]

I am the opposite of a miser...
I have all options set to stay on indefinitely, except for the hard disks, which sleep after 60 minutes.

Screen Saver is enabled, but it just goes to an Avast scan, with bubbles.

Screen never goes black without other symptoms of a crash. Computer can stay on, without being touched, for 24 hours, and the display won't normally go to sleep.


Oh, also, yes, the full 8GB of ram has been in the entire time besides for each sticks solo time for testing.

Edited by MisterCorn, 20 October 2009 - 04:54 PM.

[rshaffer61]

OK so the system is running correctly now except for the screen problem?
Let's do another check then while it is running correctly.

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
  In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply

[MisterCorn]

One thing that irks me is that the crash reporting had been disabled, which I found out when WhoCrashed installed... Again, inherited computer...

Vino's Event Viewer v01c run on Windows Vista in English
Report run at 21/10/2009 6:29:26 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 02/12/2008 3:04:45 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 3:15:11 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 3:23:28 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 3:27:42 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 3:53:33 AM
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point on volume (Process = C:\Users\Gman\AppData\Local\Temp\{680081B1-2A66-4292-9CCF-9A48DC8587BB}\{C40C3C3D-97CF-44B5-836C-766E374464B3}\dx\DXSETUP.exe /silent; Descripton = ôv; Hr = 0x80070057).

Log: 'Application' Date/Time: 02/12/2008 3:53:52 AM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: AGEIA PhysX v7.09.13 -- Installation terminated

Log: 'Application' Date/Time: 02/12/2008 3:58:07 AM
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Futuremark\3DMark Vantage\benchmark.dll". Dependent Assembly Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis.

Log: 'Application' Date/Time: 02/12/2008 4:03:01 AM
Type: Error Category: 0
Event: 11935 Source: MsiInstaller
Product: Microsoft Office Enterprise 2007 -- Error 1935.An error occurred during the installation of assembly component {97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}. HRESULT: 0x80070BC9. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC80.ATL,version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",processorArchitecture="x86"

Log: 'Application' Date/Time: 02/12/2008 4:04:27 AM
Type: Error Category: 0
Event: 1024 Source: MsiInstaller
Product: Microsoft Office Enterprise 2007 - Update '2007 Microsoft Office Suite Service Pack 1 (SP1)' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft....k/?LinkId=23127

Log: 'Application' Date/Time: 02/12/2008 4:19:09 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 4:39:31 AM
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point on volume (Process = C:\Users\Gman\AppData\Local\Temp\RarSFX0\DXSETUP.exe /Silent; Descripton = ô‡v; Hr = 0x80070057).

Log: 'Application' Date/Time: 02/12/2008 4:43:16 AM
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Log: 'Application' Date/Time: 02/12/2008 4:51:05 AM
Type: Error Category: 0
Event: 12293 Source: VSS
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details GetSnapshotProperties({cda239a9-b9c7-4c81-a167-1137337158b8}) [hr = 0x80042308].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Log: 'Application' Date/Time: 02/12/2008 5:15:32 AM
Type: Error Category: 0
Event: 12298 Source: VSS
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{33068bd9-c025-11dd-82ab-806e6f6e6963}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Log: 'Application' Date/Time: 02/12/2008 5:20:05 AM
Type: Error Category: 0
Event: 12298 Source: VSS
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{33068bd9-c025-11dd-82ab-806e6f6e6963}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Log: 'Application' Date/Time: 02/12/2008 5:20:05 AM
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point on volume (Process = C:\Windows\system32\svchost.exe -k netsvcs; Descripton = Windows Update; Hr = 0x81000101).

Log: 'Application' Date/Time: 02/12/2008 5:21:39 AM
Type: Error Category: 1
Event: 482 Source: ESENT
Windows (2204) Windows: An attempt to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log" at offset 0 (0x0000000000000000) for 131072 (0x00020000) bytes failed after 8 seconds with system error 1117 (0x0000045d): "The request could not be performed because of an I/O device error. ". The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.

Log: 'Application' Date/Time: 02/12/2008 5:21:39 AM
Type: Error Category: 3
Event: 413 Source: ESENT
Windows (2204) Windows: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1022.

Log: 'Application' Date/Time: 02/12/2008 5:21:39 AM
Type: Error Category: 3
Event: 492 Source: ESENT
Windows (2204) Windows: The logfile sequence in "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.

Log: 'Application' Date/Time: 02/12/2008 5:21:39 AM
Type: Error Category: 3
Event: 7040 Source: Microsoft-Windows-Search
The search service has detected corrupted data files in the index. The service will attempt to automatically correct this problem by rebuilding the index.

Context: Windows Application, SystemIndex Catalog

Details:
The content index metadata cannot be read. (0xc0041801)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2008 3:45:08 AM
Type: Information Category: 0
Event: 2 Source: Microsoft-Windows-CertificateServicesClient
Certificate Services Client has been stopped.

Log: 'Application' Date/Time: 02/12/2008 3:58:23 AM
Type: Information Category: 0
Event: 1531 Source: Microsoft-Windows-User Profiles Service
The User Profile Service has started successfully.

Log: 'Application' Date/Time: 02/12/2008 3:58:23 AM
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-Licensing-SLC
The Software Licensing service is starting.

[rshaffer61]

Well it looks like nothing has shown since Feb of last year.
How is the system running now?
Other then the screen problem is everything running the way it should?

[MisterCorn]

Yeah, I don't know why anyone would turn off error logging... It's back on now, so next time, we'll have answers.

Other than the occasional lockup/blackout, it is a sweet machine, and has no other problems.