Graphic card pin broken, what to do?

chankey007

Distinguished
Feb 22, 2010
247
1
18,695
I cleaned my PC this weekend on Saturday. Then I played BF3 whole night, then next morning while playing it I got red screen (with no message, complete red). I restarted and all went fine, no red screen since then.

Now today while playing game the screen crashed, blurred lines (only on monitor 1, monitor 2 was fine). Then I checked the graphic card. One pin is broken.

m1HCuQo.jpg


What should I do? Will it cause any problems? I don't have confirmed data but I think it only fails if play games and dual monitor is on.
 
Pins shouldn't break like that, even with the tightness of the pcie slot. Look into RMA if possible with seller, or failing that try the gpu manufacturer. Definitely looks to me like a manufacturer defect.

Your 2 other options being 1) suffer with a single monitor, 2) buy a new card.
 


See this image: http://content.hwigroup.net/images/products/xl/147441.jpg

I think here also it's not present, so it means there is nothing to worry, it came like that only? If anyone has HD 7850 2GB, then please confirm.
 


Phew! I even called the Flipkart support (from where I purchased the product last year 😛)

BTW do you have any idea why I'm facing the mentioned issues then? It used to work fine till I cleaned case this weekend.
 


The card may be defective and may needs replacement. The symptoms you mentioned are all signs of graphics card failure. If you bought the card form flipkart less than a month, you can ask them for replacement otherwise sent the card for warranty

 


Is there any kind of test which I can do to confirm that there is issue with graphic card?
 
Well, my bad, I've never seen a short pin like that, but honestly, that's the last thing I've ever looked for on a gpu physically. So it comes down to either a hardware failure of some sort or a driver issue. Try running Kombustor, or Furmark. If anything will punish a gpu its one of them. If it crashes check the windows event logger, under Admin tools, that may give you a better clue.
 


OK, BTW I think it was coming from either AID64 or CPU-Z (I read on some forums that these might be causing the issue), so I uninstalled them and didn't face the issue this morning (played about 1 hour).