BSOD occurring intermittently (usually during browsing)

jjim26 · 11 Dec 2012

Since early November I have been getting the BSOD occasionally. It usually happens when I am browsing the internet. When the BSOD occurs, it displays on the monitor for a few seconds and my computer restarts. After installing all the MS updates the BSOD appeared to have stopped. But I got it today.

The web browsers I use are Firefox and IE9. I usually have both browsers open at the same time. However I don't recall the BSOD happening when I have firefox open only.

I also scan my computer for virus/malware about once a week so I am doubtful it a virus/malware issue.

I appreciates any help.

I hope I did the dump file correctly.

koolkat77 · 11 Dec 2012

Hi,

Update video card drivers to their latest, hopefully it should resolve this issue.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800b0ca010, fffff880017aa768, 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+8768 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800b0ca010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880017aa768, 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+8768
fffff880`017aa768 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0236d1c8 fffff880`0467f000 : 00000000`00000116 fffffa80`0b0ca010 fffff880`017aa768 00000000`00000000 : nt!KeBugCheckEx
fffff880`0236d1d0 fffff880`0467ed0a : fffff880`017aa768 fffffa80`0b0ca010 fffffa80`0b19cd50 fffffa80`0902c410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0236d210 fffff880`04725f07 : fffffa80`0b0ca010 00000000`00000000 fffffa80`0b19cd50 fffffa80`0902c410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0236d240 fffff880`04753d5a : fffffa80`ffffffff 00000000`0015203d fffff880`0236d390 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0236d320 fffff880`04739bb1 : fffffa80`090a0000 ffffffff`feced300 00000000`00000002 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0236d360 fffff880`0473caaf : 00000000`0005b849 00000000`00000000 00000000`00000000 fffff8a0`0fa796c0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`0236d460 fffff880`0473b1a0 : fffff8a0`0fa796c0 00000000`00000000 fffffa80`090a0000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`0236d4a0 fffff880`0473b0f6 : 00000000`00000000 00000000`00000001 fffffa80`090a0000 fffff880`04739a1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`0236d630 fffff880`04744642 : fffffa80`08c6ba80 00000000`00000001 00000000`00000001 fffff800`03284a32 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`0236d6a0 fffff880`047443eb : fffff8a0`0fa796c0 00000000`00001000 fffffa80`08c6ba80 fffff8a0`0fa796c0 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`0236d6f0 fffff880`04743d8f : fffff8a0`0fa796c0 fffffa80`090a0c80 00000000`00000000 fffffa80`090a0c80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`0236d750 fffff880`0473776c : fffffa80`090a0000 fffffa80`090a0000 fffffa80`090a0c80 fffffa80`090a0000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`0236d790 fffff880`04734133 : 00000000`00000000 00000000`00000000 00000000`0000002a fffffa80`090a0000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`0236d7d0 fffff880`0474e65d : 00000000`00000000 fffff8a0`0ccf8fd0 fffffa80`00000000 fffffa80`0a6ec580 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`0236d9a0 fffff880`0474e398 : fffff800`00b96080 fffff880`0474dd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0236db90 fffff880`0474de96 : 00000000`00000000 fffffa80`0856fbf0 00000000`00000080 fffffa80`0902c410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0236dbc0 fffff800`03525e5a : 00000000`fffffc32 fffffa80`08c65b50 fffffa80`051d3040 fffffa80`08c65b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0236dc00 fffff800`0327fd26 : fffff800`03401e80 fffffa80`08c65b50 fffff800`0340fcc0 4f2b7a52`676a6161 : nt!PspSystemThreadStartup+0x5a
fffff880`0236dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+8768
fffff880`017aa768 4055            push    rbp

SYMBOL_NAME:  atikmpag+8768

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f7e4294

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`017a2000 fffff880`017fc000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Apr 06 07:10:44 2012 (4F7E4294)
    CheckSum:         0005A52D
    ImageSize:        0005A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Go through STOP 0x116: VIDEO_TDR_ERROR troubleshooting for more information on the bug check.

Also disable hardware acceleration on the browsers.

Hope this helps.

jjim26 · 11 Dec 2012

I updated my video driver through steam less than a week ago. I tried updating it right now through Microsoft auto update and it is current. So it may not be a video driver issue.

What do you mean by disable hardware acceleration on the browsers? How do I do that?

koolkat77 · 11 Dec 2012

Here: http://www.askvg.com/how-to-disable-...-font-problem/

Go through the 116 troubleshooting thread.

jjim26 · 11 Dec 2012

I disabled the hardware acceleration.

Looking over the 116 troubleshooting thread I did all the software related fixes. If the disable hardware acceleration doesn't fix it I probably have a faulty or failing GPU.

Could an improperly installed GPU cause the BSOD? I.E. the GPU not fitting in the PCIE slot properly or correctly?

koolkat77 · 11 Dec 2012

jjim26 said:

I disabled the hardware acceleration.

Looking over the 116 troubleshooting thread I did all the software related fixes. If the disable hardware acceleration doesn't fix it I probably have a faulty or failing GPU.

Could an improperly installed GPU cause the BSOD? I.E. the GPU not fitting in the PCIE slot properly or correctly?

Probably.

Try re-seating it.