Solved PC hangs and stutters sound while playing games. Overheat?

[dukethedj]

So a few minutes ago, I was playing NFSMW on My PC. It was running on High. Everything was normal except that the metal chassis on the PC is hot. I thought it was just my rear intake fan just blowing hot air out of the open DVD drive bay cover I took out for air flow, so I just kept playing. A few minutes later, the PC just hangs and I am forced to do a cold restart witch I hate doing. Anyone know what the problem is? Overheat? Should I change something? (PS: I did NOT Overclock anything.)

 

[YoYo155]

Hi duke .
Well over heating can be tested, don't let the temperatures 85°C if they do stop the test(s).
:ar: Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
     Note

  It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.

:ar: Please upload the MSINFO32 file:

rb:Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.

Attach the file in your next post.

:ar: Please export and upload your system event log:

1. rb: Start → type eventvwr → hit Enter.
2. Toggle open the triangle to the left of Windows Logs, right-click on System and choose Save All Events As...
3. 
4. A dialogue box will pop up asking you to name the file and select the save directory, name the file the same as your Seven Forums user-name and save it to the desktop.
5. A second dialogue box will appear asking you to select the Display Information, select Display information for these languages and check the box next to English (if you don't have English automatically offered check the box at the bottom to display additional languages - Show all available languages and check English).
6. 
7. Wait a few moments until the cursor returns to normal. The file will now be on your desktop (given it's the directory it was saved to) UserName.evtx, next to it there will be a folder called LocaleMetaData select both the .evtx file as well as the folder and compress them using Winrar / 7zip and attach it in your next post.

 

[matts6887]

it does in fact sound like your system is boiling over so to speak. How many fan(s) does your system have and what rpm are they running at? Please post according to the pictures above so we can see what temps etc the system is running at.

 

[dukethedj]

I have one rear 120 mil fan and I have no idea what it is running at, the AMD stock 90 mill cooler for the processor (No idea what it is running at), one 120 mil fan for the power supply (again, no idea) and one 90 mil fan for the video card. (It is running at 4680 RPM)

 

[YoYo155]

Thanks for the files .
The images are very small but I can make out that Prime95 was parked (not stressing)
and that the CPU is at 49.5°, the GPU is at 53° and that the images are the same.

 

[dukethedj]

Thanks for the files .
The images are very small but I can make out that Prime95 was parked (not stressing)
and that the CPU is at 49.5°, the GPU is at 53° and that the images are the same.

Hm..... Weird. I do remember taking two pictures. And I also remember running the CPU test.. Strange. So it is not an overheating problem?

 

[YoYo155]

Hm..... Weird. I do remember taking two pictures. And I also remember running the CPU test.. Strange. So it is not an overheating problem?

I can't know if the test didn't run or at least the proper data was presented, please try again .

I went through the event log and found several points of interest.
You are experiencing (or at least experienced) a couple of TDR events.

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.

Warning    28/12/2013 02:26:01    Display    4101    None
Warning    28/12/2013 02:13:13    Display    4101    None
Warning    27/12/2013 07:17:18    Display    4101    None
Warning    27/12/2013 07:10:44    Display    4101    None
Warning    27/12/2013 07:04:37    Display    4101    None
Warning    27/12/2013 07:04:15    Display    4101    None

Display driver nvlddmkm stopped responding and has successfully recovered.

In your case it didn't bugcheck the machine but it doesn't mean that you should accept its presence.

You also have a couple these entries.

Error    03/01/2014 00:11:13    HAL    12    None
Error    01/01/2014 00:24:26    HAL    12    None
Error    30/12/2013 02:51:58    HAL    12    None

The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

Are any of those dates ring a bell with new hardware of some sort?
Anything really a USB, a PCI-e etc'..

Also you had a couple of 0x7E bugchecks, please post the file from this tutorial.

• http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[dukethedj]

Hm..... Weird. I do remember taking two pictures. And I also remember running the CPU test.. Strange. So it is not an overheating problem?

I can't know if the test didn't run or at least the proper data was presented, please try again .

I went through the event log and found several points of interest.
You are experiencing (or at least experienced) a couple of TDR events.

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.

Warning    28/12/2013 02:26:01    Display    4101    None
Warning    28/12/2013 02:13:13    Display    4101    None
Warning    27/12/2013 07:17:18    Display    4101    None
Warning    27/12/2013 07:10:44    Display    4101    None
Warning    27/12/2013 07:04:37    Display    4101    None
Warning    27/12/2013 07:04:15    Display    4101    None
 
Display driver nvlddmkm stopped responding and has successfully recovered.

In your case it didn't bugcheck the machine but it doesn't mean that you should accept its presence.

You also have a couple these entries.

Error    03/01/2014 00:11:13    HAL    12    None
Error    01/01/2014 00:24:26    HAL    12    None
Error    30/12/2013 02:51:58    HAL    12    None
 
The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

Are any of those dates ring a bell with new hardware of some sort?
Anything really a USB, a PCI-e etc'..

Also you had a couple of 0x7E bugchecks, please post the file from this tutorial.

• http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

I ran the test again and I got the same data


12/27/13 That's when I added my new video card and processor. Failed on the fan speed changing (EVGA Precision X (I did not overclock it) (TDR)
1/1/14 is when I started getting problems

30/12/13 is when I tried to do a Skype Call and the stinking drivers for the webcam (Logitech Pro 9000) Always gives me a bluescreen when the webcam software is opened

 

[dukethedj]

Ok. I found out that it was not a hardware problem. This happens when I leave DreamScene Activator running for a while. I turned it off and it is now working problem free.