BSoD and Screen Resolution problem when Upgrading to new Graphics Card

Xen12 · 16 Sep 2013

First of all, I apologize if I opened this thread in the wrong Section.

Onto the problem~

After installing War Thunder, I realized I needed to upgrade to a newer version of my Graphics card. So I opened Device Manager and went to upgrade the graphics driver, but said It's up to date, so I go to the AMD website ( I have a ATI Radeon HD Series Graphic card, which is supported by AMD ) to download a new one, I enter the correct information here which gives me this to which I download the first one, all's fine and dandy, but once I reboot, the Screen resolution is much bigger, and moments later I'd receive a BSoD. So is there anything I'm missing? Much appreciated

Arc · 17 Sep 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Xen12 · 17 Sep 2013

I've done as instructed and ran the SF diag tool, should I upload the zipped folder to pastebin/dropbox?

Arc · 18 Sep 2013

Post it here .... follow Screenshots and Files - Upload and Post in Seven Forums

Xen12 · 18 Sep 2013

Here you go Attachment 286435

Arc · 19 Sep 2013

It is a stop 0x116, which is a graphics/display related BSOD. As you have installed the latest version (till date), we cannot blame the driver itself as the source of the issue before having some other tests done.

And BTW, WHQL 13.9 is also out there: AMD Catalyst

It Appears to be an old (3-4 years) branded desktop. What is the wattage of your PSU? Let us know. Are you using the stock PSU?
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

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.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
_______________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e9b8010, fffff88004ad8cf0, 0, 2}

Unable to load image 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+acf0 )

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: fffffa800e9b8010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004ad8cf0, 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+acf0
fffff880`04ad8cf0 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`071e19c8 fffff880`05153054 : 00000000`00000116 fffffa80`0e9b8010 fffff880`04ad8cf0 00000000`00000000 : nt!KeBugCheckEx
fffff880`071e19d0 fffff880`05152d5e : fffff880`04ad8cf0 fffffa80`0e9b8010 fffffa80`0a98d010 fffffa80`0a9f9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`071e1a10 fffff880`04a0ff13 : fffffa80`0e9b8010 00000000`00000000 fffffa80`0a98d010 fffffa80`0a9f9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`071e1a40 fffff880`04a39cf1 : 00000000`ffffffff 00000000`0006416e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`071e1b20 fffff880`04a38437 : 00000000`00000102 00000000`00000000 00000000`0006416e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`071e1b50 fffff880`04a0b2d2 : ffffffff`ff676980 fffffa80`0a9f9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`071e1bf0 fffff880`04a37ff6 : 00000000`00000000 fffffa80`0a98d010 00000000`00000080 fffffa80`0a9f9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`071e1d00 fffff800`03562bae : fffffa80`0a572c60 fffffa80`079f5b50 fffffa80`06d09040 fffffa80`08ca8200 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`071e1d40 fffff800`032b58c6 : fffff880`031d5180 fffffa80`079f5b50 fffff880`031dffc0 fffff880`0610a3b0 : nt!PspSystemThreadStartup+0x5a
fffff880`071e1d80 00000000`00000000 : fffff880`071e2000 fffff880`071dc000 fffff880`09845d70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+acf0
fffff880`04ad8cf0 4055            push    rbp

SYMBOL_NAME:  atikmpag+acf0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5154e9d9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Xen12 · 19 Sep 2013

Alrighty,

Here is the screenshot of Speccy after a few hours.

And heres Attachment 286534

Attachment 286535

Also, the average temperature of the cpu is normally are 50-58, I rarely see it go to above 80%, I've been monitoring it with Temp Core. But I'll stick with Speccy since it's much better.

Also, WHQL 13.9? What's that? ( I'm new to this driver thingy, sorry

)

EDIT: Forgot the PSU wattage, minimum psu is 489W, recomended PSU Wattage is 539W

Arc · 19 Sep 2013

What is the wattage of your own PSU? How much it is more than the recommended?

13.9 WHQL is the latest version of ATI display driver, released yesterday.

The GPU goes to 98 degrees within 5 minutes ..... it may be a critical information. How long did you run furmark? What happened when it was running? Did it cause any problem there? Did it stop itself or you stopped it manually?

Do you know how to dismantle a PC? Dont start dismantling it it is unfamiliar to you. :) Just let us know that you know it or not.

Xen12 · 19 Sep 2013

Attachment 286562 here is the PSU wattage

I was running Furmark for about a 1 minute till I heard a beeping ( from the program furmark, the fans were on at that moment) and then I manually stopped it. I do know how to dismantle a PC but I'm not familiar with what the motherboard, Graphic cards, and processor look like

Arc · 19 Sep 2013

We want to know the wattage of your own PSU. Of how many watts it is?

Suppose this one ... it is of 720 watts.