Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Playing games on Steam, error 0x00000116


10 Mar 2014   #1

Windows 7 Professional
 
 
BSOD Playing games on Steam, error 0x00000116

I'm getting blue screens when playing games on steam. The games I've noticed it on are:
Skyrim
Loadout
Sleeping Dogs
DmC Devil May Cry
Shadow Warrior

According to BlueScreenView the cause for the last few crashes is dxgkrnl.sys, and has previously been atikmpag.sys. As far as I know the drivers for my graphics card and motherboard are up to date, and I'm excluding my Steam folder from F-Secure's real-time scanner.

Thanks for any help!



Attached Files
File Type: zip SF_10-03-2014.zip (2.95 MB, 3 views)
My System SpecsSystem Spec
.

10 Mar 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Hi Proto325.

Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 13.9 WHQL only.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results.
-------------------------------------------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007c04290, fffff880042fed88, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+bd88 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007c04290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880042fed88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+bd88
fffff880`042fed88 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`027d5888 fffff880`044ee140 : 00000000`00000116 fffffa80`07c04290 fffff880`042fed88 00000000`00000000 : nt!KeBugCheckEx
fffff880`027d5890 fffff880`044ede4a : fffff880`042fed88 fffffa80`07c04290 fffffa80`0796d590 fffffa80`08d24410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`027d58d0 fffff880`04594f13 : fffffa80`07c04290 00000000`00000000 fffffa80`0796d590 fffffa80`08d24410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`027d5900 fffff880`045becf1 : 00000000`ffffffff 00000000`00069318 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`027d59e0 fffff880`045bd437 : 00000000`00000102 00000000`00000000 00000000`00069318 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`027d5a10 fffff880`045902d2 : ffffffff`ff676980 fffffa80`08d24410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`027d5ab0 fffff880`045bcff6 : 00000000`00000000 fffffa80`07928d50 00000000`00000080 fffffa80`08d24410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`027d5bc0 fffff800`033182ea : 00000000`fffffc32 fffffa80`08e6db50 fffffa80`066bfb30 fffffa80`08e6db50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`027d5c00 fffff800`0306c8e6 : fffff800`031f6e80 fffffa80`08e6db50 fffff800`03204cc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`027d5c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bd88
fffff880`042fed88 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bd88

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

Followup: MachineOwner
---------

1: kd> lmvm atikmpag
start             end                 module name
fffff880`042f3000 fffff880`04393000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013 (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
11 Mar 2014   #3

Windows 7 Professional
 
 

According to the power supply calculator my power supply should be about 300w, and mine is 550w, so that should be fine. The stress test ran without issue, and temperature leveled out at about 80 C.
I don't really know what temperature everything should be, but here's the Speccy screenshot.
I've installed the older drivers now, will report back once I've tested some of the games.
UPDATE: After playing Loadout for about an hour the PC froze, as if it were going to blue screen, but the blue screen never came. After I restarted I checked the minidump and now the driver responsible is ntoskrnl.exe.


Attached Images
 
Attached Files
File Type: zip SF_11-03-2014.zip (2.77 MB, 2 views)
My System SpecsSystem Spec
.


15 Mar 2014   #4

Windows 7 Professional
 
 

Bumping with new crash report files from a few days after following the instructions given, any additional help would be greatly appreciated.
My System SpecsSystem Spec
16 Mar 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

The latest BSOD as per post #3 is a stop 0x124.
Code:
BugCheck 124, {0, fffffa8007d8b8f8, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------
It is a hardware issue, apparently. And a stop 0x124 followed by a stop 0x116 highly indicates to failing graphics hardware.

Do you have another GPU to test with? Or use onboard graphics to observe if the BSODs are still occurring or not.

Stress test the CPU.
Hardware - Stress Test With Prime95

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
My System SpecsSystem Spec
17 Mar 2014   #6

Windows 7 Professional
 
 

Stresstest and Memtest turned up clean.
How do I switch to onboard graphics? There doesn't seem to be any option for that in Catalyst Control Centre. Do I just uninstall my AMD graphics drivers?
My System SpecsSystem Spec
17 Mar 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

You have to remove the display output from the GPU's end and plug it in the motherboard's display output.
My System SpecsSystem Spec
17 Mar 2014   #8

Windows 7 Professional
 
 

None of the games that have been causing BSODs will play on the onboard graphics, and I don't have any other GPUs around either.
My System SpecsSystem Spec
Reply

 BSOD Playing games on Steam, error 0x00000116




Thread Tools



Similar help and support threads for2: BSOD Playing games on Steam, error 0x00000116
Thread Forum
BSOD playing games or otherwise, error 0x00000116 BSOD Help and Support
BSOD while playing games, error 0x00000116 BSOD Help and Support
BSOD playing games 0x00000116 error Gaming
BSOD playing flash games error 0x00000116 BSOD Help and Support
BSOD playing games, error 0x00000116 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:37 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33