Windows 7: BSOD probably due to Graphics card

gtafreak · 30 Oct 2012

I launched assassin creed revelation and my PC just froze. After restart there was no bios screen but all fans were running and in my mobo only one LED was glowing(D1 was on and D2 was off and my mobo manual said that this is due to memory error). So I cleaned RAM and tried again but same problem. I removed graphics card and it booted successfully and works fine. So I guess the problem is with graphics card(HD4870).

And just a few minutes back I reinserted the graphics card and tried to boot. It didnt boot for a few mins but I just waited and after 3-4mins it booted. But there were some patches of pixels here and there on the screen. And while starting windows it crashed(BSOD). Due to the pixelated screen I could not read the BSOD properly. I again tried booting and again it didnt boot immediately but after a few mins and while loading windows again BSOD. I tried booting again and same result.

While searching google I saw lots of BSOD posted over here. So thought of posting. I think the graphics card is dying. Since the screen is pixelated I don't think the graphics card can be repaired. Or can it be repaired? I will be inclined towards repairing it if possible or else I need to buy a new graphics card. I am uploading the SF_Diagnostic_Tool zip file. Kindly confirm if the problem is with the graphics card alone or whether other components are also affected. Without the graphics card the PC works fine. No BSODs. So I guess only the graphics card is the culprit.

Here are my PC spec(more than 3 yrs old so no warranty for graphics card)
Processor: amd phenom quad 940BE
motherboard: BIOSTAR TFORCE TA790GXB
Ram: Transcend 2x2GB ddr2 800mhz
Graphics card: Powercolor HD4870 1GB
harddisk:Seagate barracuda 1TB and Western digital green 640GB
smps: Corsair VX450

Arc · 31 Oct 2012

Welcome aboard, gtafreak.

It is a stop 0x116.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80061da010, fffff880044caefc, 0, 2}

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

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

It is a display related crash, but not obviously the graphics card is the reason behind it. What you are to do here is to follow the guide STOP 0x116: VIDEO_TDR_ERROR troubleshooting.

Based on my experience, I can say that the display driver you are using it troublesome. The July version.

Code:

lmvm atikmpag
start             end                 module name
fffff880`044c2000 fffff880`04521000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Jul 04 10:40:55 2012 (4FF3D05F)
    CheckSum:         0006086F
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

First you update it. AMD Catalyst.

If still the issue persists, go for the other things.

let us know the results.

gtafreak · 31 Oct 2012

Hi. Thanks for the reply.
I just have a simple question. The drivers come into picture only when Windows 7 starts right?
But with the graphics card connected the PC doesn't even boot for a few minutes. And when it boots after 2-3 mins even the boot screen is blurred. Does the drivers come into picture at the boot screen itself? Since AMD drivers get installed inside Windows 7 I thought it only comes into picture when I enter windows 7.

I usually download drivers from this page by entering my card details here AMD Graphics Drivers & Software
As per this site the latest driver is version 12.6 (which is the one I currently have)

But the site you have given seems to have a even newer version 12.10. How?

Moreover the above installed driver 12.6 was working fine for 3-4 days without BSOD. Only a few days back this issue started.

Arc · 31 Oct 2012

Based on what you have told about the card, you need to stress test the card.
Video Card - Stress Test with Furmark

Let us know the result.

gtafreak · 31 Oct 2012

Ok Thanks again. But with the graphics card inserted I can't go beyond the blurred windows 7 logo at startup. Everytime I am getting this blurred BSOD screen after the windows 7 logo.
But if I remove the graphics card and use the inbuilt graphics then the PC works fine without BSODs and without any screen blurs.

I'll uninstall AMD drivers and insert graphics card and try to see if it is able to go past the windows 7 logo screen. Only if it gets past the screen I can try installing new drivers and furmark right?

edit: Artifacts is a better term than blurring.

Arc · 31 Oct 2012

gtafreak, furmark will make it sure that if the card is really bad or not.

But, as the problems are not occurring using the onboard graphics, I guess you have got it, and your issue is fixed.

Am I right?

gtafreak · 31 Oct 2012

Fixed. Yes the BSODs do not occur anymore but I want to know if it is a irrecoverable hardware fault in the graphics card and whether my only option is to buy a new graphics card for gaming(since it is out of warranty). If you can confirm that then it will save me a lot of hassle inserting reinserting and waiting for it to boot etc

.

Arc · 31 Oct 2012

For the confirmation, furmark test is needed.

gtafreak · 01 Nov 2012

Hey common. How can I try furmark if the graphics card doesn't even allow me to enter windows 7?

Arc · 01 Nov 2012

Then there is no necessity of further testing at all. Just abandon it.

Use the onboard graphics till you are not buying the new card. OK?

And, is there any further troubles?

Windows 7: BSOD probably due to Graphics card

BSOD probably due to Graphics card problems?