[l3th4l]

Hello there, sadly it's me once again. So short story : I got my "new' PC not so long ago (used, not new), and it just turns off randomly while playing a game (League of Legends to be precise, haven't tried other game). The shutdowns are at random times, now it turned off trice in 10~ minutes, rejoined the game everytime it shut down. I have the newest drivers, the problem started to happen only few days ago. PC specs:
x2 Athlon 6000+
4gb ram (only 3.25gb usable, too lazy to install 64 bit)
Asus Radeon HD4850 GPU
PSU Codegen 400W PSU
M57SLI-S4 mobo (Only 1 GPU in)
That's pretty much all you need I believe, if you need any thing else jusk ask. Oh and also the temps are a-ok, it used to overheat but I took away one side of the comp and the GPU heat dropped down by 20C~, double checked now, no overheating. I'm leaning towards hardware issue for some reason, PSU to be more exact, also the PSU is REALLY loud sometimes, it sounds like some metal plate is loose and it keeps hitting the side of it really fast so the sound is real annoying, didn't find anything loose from the first look though, haven't taken it apart yet.
Thanks in advance.

Edited by l3th4l, 16 November 2011 - 09:22 AM.

[Advertisements]

PSU Codegen 400W PSU

I suspect this is your problem. Does the issue happen any other time other then playing a game?


Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

[rshaffer61]

PSU Codegen 400W PSU

I suspect this is your problem. Does the issue happen any other time other then playing a game?


Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

[l3th4l]

Temps are more than OK as I already said, says only fan 1 is spinning, 2136rpm. Here's the pic :

Spoiler

Don't have to treat me as a complete newbie, probably already have all the software you'll ask me to download, been facing other problems and posted here before.
And yeah, heard that codegen PSUs ain't the best, it was the one PC came with though, have a 420W PSU on my old comp ([bleep] brand as well), but it doesn't have a PCI-e connector. Going to the city in saturday, gonna buy a molex->PCI-E cable if PSU is the issue, would be nice to get it sorted out by then.
Like 5th edit: And no, PC doesn't restart when idle.

Edited by l3th4l, 16 November 2011 - 01:35 PM.

[rshaffer61]

Don't have to treat me as a complete newbie, probably already have all the software you'll ask me to download, been facing other problems and posted here before.

I'm sorry where did I treat you as a newbie? The instruction I post are what we use for everyone regardless of their technical skills or lack of.

You stated:

Oh and also the temps are a-ok, it used to overheat but I took away one side of the comp and the GPU heat dropped down by 20C~, double checked now, no overheating

Taking off one side of the case would indicate a heating issue which in most cases would indicate a airflow problem.
The GPU falling in temperature -20 doesn't give me the actual temperature so I was only asking for a visual reference. I also have only started with the diagnostic part and since you did not post what you have as far as programs I can only summarize you didn't try them.
Since the system shuts down I would suspect some type of Event being entered in the event log so can you please provide the following.

• 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) 15 11 2011
  In the To: boxes type today's date (presuming the crash happened today) 15 11 2011
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply




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

http://www.resplendence.com/downloads

[l3th4l]

WhoCrashed :

Spoiler

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 10/27/2011 4:50:53 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82C4F161)
Bugcheck code: 0x116 (0xFFFFFFFF85BEF008, 0xFFFFFFFFA287F294, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown VIDEO_TDR_ERROR




On Thu 10/27/2011 3:44:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102711-15265-01.dmp
This was probably caused by the following module: disk.sys (disk+0x0)
Bugcheck code: 0x116 (0xFFFFFFFF85DBF008, 0xFFFFFFFF91B3F294, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\disk.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: PnP Disk Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

^ The dates are completely wrong?
VEW :

Spoiler

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 11/17/2011 2:45:04 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 11/17/2011 12:15:12 PM
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: 11/16/2011 3:36:56 PM
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: 11/16/2011 3:06:45 PM
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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 11/17/2011 12:22:32 PM
Type: Information Category: 0
Event: 1005 Source: Microsoft-Windows-CEIP
Customer Experience Improvement Program data was successfully consolidated into files that will be sent to Microsoft for analysis. These files will be sent only if the user has opted to join the Windows Customer Experience Improvement Program.

Log: 'Application' Date/Time: 11/17/2011 12:21:28 PM
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.

Log: 'Application' Date/Time: 11/17/2011 12:21:27 PM
Type: Information Category: 0
Event: 16384 Source: Microsoft-Windows-Security-SPP
Successfully scheduled Software Protection service for re-start at 2011-11-20T12:23:27Z. Reason: GVLK.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 11/16/2011 3:05:13 PM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
The content source <csc://{S-1-5-21-3034654938-501922219-2623031665-1000}/> cannot be accessed.

Context: Application, SystemIndex Catalog

Details:
The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d)


Log: 'Application' Date/Time: 11/15/2011 10:57:36 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.

Log: 'Application' Date/Time: 11/15/2011 3:58:53 PM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5448) - Version or flavor did not match with repository: Microsoft.Security.ApplicationId.PolicyManagement.Cmdlets

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/16/2011 3:35:01 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/16/2011 3:04: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: 11/16/2011 3:01:28 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: 11/17/2011 12:13:27 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 11/16/2011 3:35:12 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: cdrom

Log: 'System' Date/Time: 11/16/2011 3:35:06 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 17:26:19 on ?16/?11/?2011 was unexpected.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/17/2011 12:43:59 PM
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The WinHTTP Web Proxy Auto-Discovery Service service entered the running state.

Log: 'System' Date/Time: 11/17/2011 12:40:41 PM
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The Application Information service entered the running state.

Log: 'System' Date/Time: 11/17/2011 12:31:41 PM
Type: Information Category: 0
Event: 7036 Source: Service Control Manager
The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/17/2011 12:13:13 PM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-HAL
Initialization of the High Precision Event Timer failed due to a BIOS configuration problem. The operating system will use another available platform timer in lieu of the High Precision Event Timer. Contact your system vendor for technical assistance. Initialization status: 0x1.

Log: 'System' Date/Time: 11/16/2011 10:04:04 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 11/16/2011 3:34:57 PM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-HAL
Initialization of the High Precision Event Timer failed due to a BIOS configuration problem. The operating system will use another available platform timer in lieu of the High Precision Event Timer. Contact your system vendor for technical assistance. Initialization status: 0x1.

EDIT: And yes, it was probably an airflow issue CCC says the idle temps are 37-45c, they NEVER reach 90c while gaming, it used to shut down at 93c when it overheated before. The temps are even below the normal temps for the ASUS hd 4850 from the benchmarks I've read.

Edited by l3th4l, 17 November 2011 - 06:51 AM.

[rshaffer61]

WhoCrashed show 2 crashes, both caused by your display driver just a little over a hour apart. I would suspect this was a heat issue which you have stated that has been taken care of.

Next please do the following.


Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[l3th4l]

10/27/2011 Is pretty long time ago, got this pc around that time, must've fixed the heating issue back then. Going to do the test in few minutes.
EDIT: I'm using Win 7, not sure where I can find the winlogon (here's one I found, there's also one under "microsoft" but that one is empty), here's a screenshot

Spoiler

Edited by l3th4l, 17 November 2011 - 08:05 AM.

[rshaffer61]

Since you are using Win7 try these instructions.

Tutorial for running chkdsk in Vista\Win 7 located HERE.