Complete red screen problem, graphic card issue?

[chankey007]

This weekend I cleaned the system and put a side panel case fan (bought it due to heating issues), since then I'm facing a issue. I have dual monitors, when I play BF3, sometimes it works fine for hours, and sometimes I get red screen. I checked the cables. Reset the graphic card. Just now I got red screen after playing 15-20 minutes. What's the issue? Graphic card is not faulty as I'm using it since December 2013. There are no broken pins also.

I noticed a broken pin but in this thread they told me it's by design.

So what else could be the reason?

I took a screenshot of the 2nd monitor when 1st monitor was complete red. These are the readings. Do you think graphic card is overheating? Or its RPM is higher than maximum?

Image (Hardware Monitor and AID64): http://i.imgur.com/5SRbQJd.jpg

 

[CraigN]

GPU is at 64C. It's definitely not overheating. That's not a broken pin, that is by design.

The only real way you can isolate that your card *isn't* failing is by testing it with another one. But in the mean time, I would suggest doing a clean uninstall of your graphics drivers (perhaps using Driver Sweeper) and reinstall them and see if that doesn't solve the problem. If not, I would guess your GPU is on it's way out.

 

[chankey007]

GPU is at 64C. It's definitely not overheating. That's not a broken pin, that is by design.

The only real way you can isolate that your card *isn't* failing is by testing it with another one. But in the mean time, I would suggest doing a clean uninstall of your graphics drivers (perhaps using Driver Sweeper) and reinstall them and see if that doesn't solve the problem. If not, I would guess your GPU is on it's way out.

The max value of GPU's temp in that image is 67C.

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

 

[CraigN]

I was reading it off my phone and I just glanced, my bad 😛

That's good, I'm not familiar with AID64 so I can't say for sure there, but I can't think of any reason CPU-Z would be causing that issue. Either way, glad you're not facing it anymore.