BSOD After Installing Two New (Dual Monitors)

JeffreyJames · 10 Dec 2012

SF Diagnostics Tool File Uploaded As Requested.

System was fine. Decided to buy and run dual monitors to increase productivity. Everything was fine until Then. I gave the old monitor I was using to my brother so they are two new ones. HP 2311xi.

I run a HP Pavillion h8-1234 PC
AMD Six-Core FX-6120 Processor
16gb ram

Video card that I installed several months ago (with no problems)
(GIGABYTE) AMD Radeon HD 7850.

One monitor plugged into HDMI and one plugged into DVI-I slot. Only two digital slots on the video card.

All the sudden this BSOD starts. Any help would be much appreciated. Not getting much done as you would imagine.

Only thing new besides that I can think of is after reboot a screen briefly appears during boot that says RAID on it among many other things. Thanks for any help!

-JJ

koolkat77 · 10 Dec 2012

Welcome to SevenForums.

Looks like it was caused due to outdated video card drivers:

Code:

................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800d9714e0, fffff88004ac99e0, 0, d}

*** 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+79e0 )

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: fffffa800d9714e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004ac99e0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+79e0
fffff880`04ac99e0 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`167c1888 fffff880`05b33000 : 00000000`00000116 fffffa80`0d9714e0 fffff880`04ac99e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`167c1890 fffff880`05b32d87 : fffff880`04ac99e0 fffffa80`0d9714e0 fffffa80`1034dc00 fffffa80`10340010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`167c18d0 fffff880`04b26f07 : fffffa80`0d9714e0 00000000`00000000 fffffa80`1034dc00 fffffa80`10340010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`167c1900 fffff880`04b50b75 : 00000000`ffffffff 00000000`00010eb5 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`167c19e0 fffff880`04b4f2bb : 00000000`00000102 00000000`00000003 00000000`00010eb5 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`167c1a10 fffff880`04b222c6 : ffffffff`ff676980 fffffa80`10340010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`167c1ab0 fffff880`04b4ee7a : 00000000`00000000 fffffa80`0d609bf0 00000000`00000080 fffffa80`10340010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`167c1bc0 fffff800`02f1ee5a : 00000000`fffffc32 fffffa80`1033fa00 fffffa80`0cd4a210 fffffa80`1033fa00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`167c1c00 fffff800`02c78d26 : fffff880`009f2180 fffffa80`1033fa00 fffff880`009fd040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`167c1c40 00000000`00000000 : fffff880`167c2000 fffff880`167bc000 fffff880`0bcc0d70 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`04ac99e0 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+79e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8

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`04ac2000 fffff880`04b17000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Feb 15 08:13:12 2012 (4F3B14B8)
    CheckSum:         00051BFD
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

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