BSOD since started using 2 monitors. Even under no load at all.

Domenique01 · 05 Jan 2013

Hello,

A month ago I build my own system, everything was working fine until I started using a second monitor this week.
I get random BSOD. Sometimes during gaming, but today even while browsing the sevenforums.
It's getting so annoying now that I decided to disable my second monitor.
I had just enough knowledge to build my own system, but when it gets to crashes, I'm helpless.

I’ve read on the internet that it can be 1 of 2 things.
- my drivers (AMD vision engine control centre say's it's up to date)
- my PSU. (if so I'll just buy another one, but I want to be sure before I do)

I've added the SF diagnostic file as attachment, your help would be very much appreciated.
Thanks in advance

DocBrown · 05 Jan 2013

Welcome Domenique01 :)

All of your systems specs would be very helpful. Also the make & model of each of the 2 monitors and any video cards. Thanks

System Info - See Your System Specs

Domenique01 · 05 Jan 2013

I'm sorry I’ve updated my specs.
I was under the impression that the SF diagnostic tool would do that for me.

Thanks for the quick reply!

edit:
additional info, I have 2 Samsung LED Monitor S22B350 21.5.
1 is the S22B350H
the other one is also S22B350 but I'm not sure which type exactly, the differ slightly in model.
One is connected to the graphic card via HDMI, the other one via a HDMI to DVI connector.

This are the exact specs of my graphics card: Club3D PCI-e Radeon HD7850 royalKing 2GB HDMI/DP

koolkat77 · 05 Jan 2013

Welcome to SevenForums and thanks for filling in your specs :)

All your dump files come with BCC 116.

We have a thread on how to troubleshoot it in the best possible ways here:

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Please go through it and let us know if you were able to meet a resolution.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80076c34e0, fffff880040e8768, 0, d}

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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80076c34e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880040e8768, 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+8768
fffff880`040e8768 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`073179c8 fffff880`04545000 : 00000000`00000116 fffffa80`076c34e0 fffff880`040e8768 00000000`00000000 : nt!KeBugCheckEx
fffff880`073179d0 fffff880`04544d87 : fffff880`040e8768 fffffa80`076c34e0 fffffa80`097db950 fffffa80`0994a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07317a10 fffff880`0440ff07 : fffffa80`076c34e0 00000000`00000000 fffffa80`097db950 fffffa80`0994a410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`07317a40 fffff880`04439b75 : 00000000`ffffffff 00000000`000466fb 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07317b20 fffff880`044382bb : 00000000`00000102 00000000`00000003 00000000`000466fb 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07317b50 fffff880`0440b2c6 : ffffffff`ff676980 fffffa80`0994a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07317bf0 fffff880`04437e7a : 00000000`00000000 fffffa80`07b04860 00000000`00000080 fffffa80`0994a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07317d00 fffff800`03162e5a : 00000000`fffffc32 fffffa80`08721b50 fffffa80`06d0db30 fffffa80`08721b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07317d40 fffff800`02ebcd26 : fffff800`0303ee80 fffffa80`08721b50 fffff800`0304ccc0 fffff880`07317e40 : nt!PspSystemThreadStartup+0x5a
fffff880`07317d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+8768
fffff880`040e8768 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
---------
3: kd> lmvm atikmpag
start             end                 module name
fffff880`040e0000 fffff880`0413a000   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

Good luck.