Windows 7: BSOD randomly, mostly while playing saints row the third

Arc · 20 Dec 2012

Quote: Originally Posted by bluesaber27

ok, i'll try to give you as much information as i can.
My gpu is the amd radeon hd 7850 by gigabyte radeon. It is 2gb GDDR5. It is about 5 months old. Model number GV-R785OC-2GD. It is pci express 3.0, is 256 bit, and supports direct x 11.

Very good information, Nice GPU

Enter into the priority settings of the games those are problematic. Reduce the priority, textures etc to low or medium .... see if it can minimize this issue.

bluesaber27 · 20 Dec 2012

i don't really understand what you mean by priority settings, do you mean the priority settings of the program when you go on windows task manager?

Arc · 20 Dec 2012

No, the settings of the particular game .... all the priorities are there ... you need to minimize those.

bluesaber27 · 21 Dec 2012

okay, so i reduced the graphics settings on modern warfare 2 and my PC still crashed, but it lasted longer than before. Also this is the first time this happened, but windows said it was a blue screen, even though i didn't see a blue screen. I'll attach my dump files just in case. Hopefully, we're getting close to the solution to the problem
Edit: also sometimes my ati driver just stops working, it says it in a little bubble on my task bar.

Arc · 21 Dec 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8007483010, fffff88003249db8, 0, 0}

*** 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+8db8 )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8007483010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003249db8, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+8db8
fffff880`03249db8 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`065ba350 fffff880`033125f7 : fffffa80`07483010 00000000`00000024 fffffa80`09990940 fffff880`03312298 : watchdog!WdDbgReportRecreate+0xa3
fffff880`065ba870 fffff880`03312a2e : 00000000`00001000 fffff8a0`0da89bf0 00000000`00000008 00000000`00004000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`065ba8c0 fffff880`03313ce2 : fffffa80`07483010 fffffa80`07483010 fffffa80`09990940 fffffa80`0ab01410 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
fffff880`065ba960 fffff880`0592ef07 : fffffa80`07483010 00000000`00000000 fffffa80`09990940 fffffa80`0ab01410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`065ba990 fffff880`0595cd5a : fffffa80`ffffffff 00000000`0002f67f fffff880`065baaf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`065baa70 fffff880`0592a29e : fffffa80`0ab01410 ffffffff`feced300 fffffa80`09990940 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`065baab0 fffff880`05956e7a : 00000000`00000000 fffffa80`09990940 00000000`00000080 fffffa80`0ab01410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`065babc0 fffff800`03530e5a : 00000000`0401bd99 fffffa80`0abb1b50 fffffa80`066c3040 fffffa80`0abb1b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`065bac00 fffff800`0328ad26 : fffff800`0340ce80 fffffa80`0abb1b50 fffff800`0341acc0 4537376c`582b464b : nt!PspSystemThreadStartup+0x5a
fffff880`065bac40 00000000`00000000 : fffff880`065bb000 fffff880`065b5000 fffff880`065b9e30 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+8db8
fffff880`03249db8 ??              ???

SYMBOL_NAME:  atikmpag+8db8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5064f994

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03241000 fffff880`032b7000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Sep 28 06:42:52 2012 (5064F994)
    CheckSum:         00071DC9
    ImageSize:        00076000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Mini Kernel Dump does not contain unloaded driver list
2: kd> lmvm atikmpag
start             end                 module name
fffff880`03241000 fffff880`032b7000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Sep 28 06:42:52 2012 (5064F994)
    CheckSum:         00071DC9
    ImageSize:        00076000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Mini Kernel Dump does not contain unloaded driver list

As it is showing a stop 0x117 now, it is a graphics related error, and for it, it is to follow STOP 0x116: VIDEO_TDR_ERROR troubleshooting

BSOD randomly, mostly while playing saints row the third-videodriverhascrashed.png

Something like this?

If after installing the latest driver it occurs still, plan to RMA / replace the GPU. In more than 90% of cases, it is hardware error.

bluesaber27 · 21 Dec 2012

yeah, that's what's happening to my pc. I'll try downloading the amd beta driver, and if that doesn't work i guess i'll have to rma, i hope it's covered by warranty

bluesaber27 · 23 Dec 2012

Is this stop 0x117 causing my pc to go black when playing games as well?
Edit: is there a way to make sure it's my gpu first?

Arc · 24 Dec 2012

Yes there is a way ... either you use the onboard graphics, or replace the graphics card with another one. If the situation is the same, it is not the GPU but anything else. But if the situation is better, it the the GPU.

In my best assumption, it is the GPU that is causing the problem in your case.

bluesaber27 · 24 Dec 2012

if my gpu passes furmark after an hour, does this mean it's not the gpu? cause it's passed furmark 2 times before, i did the tests a few months ago. Btw Merry Christmas, Arc!

Arc · 24 Dec 2012

The error that you confirmed is too random to be caught by a furmark test. So I am not sure that it will be caught by the furmark test.

Windows 7: BSOD randomly, mostly while playing saints row the third

BSOD randomly, mostly while playing saints row the third problems?