BSOD while playing State of Decay

[Slade00]

Hello I was playing state of decay and my computer screen went black and my sound started looping. My computer turned it self on and off. This was the error code I got in the event viewer. Could this be a graphics card issue? Also the crash minidump is located in my .Rar


The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa8016b974e0, 0xfffff8800fde12bc, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\Windows\Minidump\120513-12651-01.dmp. Report Id: 120513-12651-01.

 

[Slade00]

Anyone?

 

[Slade00]

Do I need to give more information?

 

[YoYo155]

Welcome to SF Slade00, please don't bump the thread for one it has only been up for three hours
a second reason is its against the rules and a third (which you should feel mostly affecting you)
is the fact that is appears as if the thread is being handled already and it doesn't show up in the unanswered threads list.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.

A TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that something
has went terribly wrong in the kernel which forced the machine to crash.

"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. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

• Read the full post.

:ar: Please roll-back your nVidia drivers to a known stable release:

   Note

- Don't install GeForce Experience -

​

Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

:ar: Reset the BIOS back to default:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

If any component is overclocked reset it back to stock speeds!

​

What is the make, model and age of your PSU?
Fill out this form and post back the result:

• Power Supply Calculator

: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: Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

:ar: This will help you to determine where the issue is origination from (if any):

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Post back with the results.