|
I was playing Overwatch when my third monitor turned into this garbled mess, and hard locked my computer.  I'm running that monitor off of Intel integrated graphics, and according to the Intel Driver Update Utility, I have the latest version (15.40.25.4463). Is there something else I should be checking? It only affected that monitor and not the other two hooked up to my 6870. CPU: i5-6500 GPU: HD 6870 RAM: 16GB DDR4 2400 SSD: Samsung 840 EVO HDD: 1TB Samsung Drive + 2TB WD Green
|
#
?
Jul 21, 2016 02:12
|
|
|
|
| # ? May 6, 2024 22:12 |
|
|
have you tried switching the cables that connect your monitor to the computer? what else have you tried already?
|
|
#
?
Jul 21, 2016 03:28
|
|
|
What you describe is pretty much classic graphics card failure in my (admittedly somewhat limited) experience, but your post is missing a lot of info. Like what were you doing on the 3rd monitor when it did that? What happened after you rebooted? How old is that MoBo? What, if anything, have you done to troubleshoot the problem? Stuff like that. A good thing to do in my opinion, assuming this problem repeats itself, would be to connect one of the other monitors to the integrated graphics and the 3rd to the 6870 and see what happens. If it happens on the 3rd again, it's the monitor. If the other, it's either the cable or (far more likely) the graphics chipset.
|
|
#
?
Jul 22, 2016 01:26
|
|
|
And also what is the make / model of the motherboard?
|
|
#
?
Jul 22, 2016 12:25
|
|
|
Motherboard is a H110M-Pro-VD, about a month old. I wasn't doing anything actively on the monitor. It just had battlenet, steam, and foobar on it. The first time it happened (under similar circumstances), I upped the ram dedicated to my igpu to 256 MB, and updated the Intel graphics driver. I took the picture the second time it happened. I haven't tried swapping cables, but I am trying a VGA cable instead of DVI like I was using, and nothing has happened yet. I tried running memtest, and I ended up getting some errors during the Hammering Rows part:  I think my RAM could be the source of my problem, so I'm going to RMA it, and go from there. Thanks for the troubleshooting ideas.
|
|
#
?
Jul 26, 2016 03:05
|
|