chrome, no matter what website, while scrolling or watching a video or anything moving tears. it happens at the top third or slightly below center or bottom third, and it's not the same as in games with v-sync off where it tears all over the place, its constantly in the same spot after several seconds or minutes it will switch places, sometimes even fixing its self and behaving like it should.... for the same amount of time that it would till it shifts again. i thought it might be my screen but it happens on my second monitor, and not in other programs(Waterfox, IE, Yandex), i thought it might be the hdmi to dvi cable, refer to previous answer, I've updated drivers, I've updated flash, I've disabled flash, I've enabled and disabled various hardware/software rendering options in chrome flags and restarted about twice as many times, I've forced v-sync on chrome in Nvidia panel and restarted, I've restarted my computer, I've checked for chrome updates, I've tried having fewer tabs, I've spent many dollars on this msi 980 ti and about 1700 on this system in total, I've combated other problems with audio on this board (drivers from Asus website=bad, generic from realtek chips website=good), I've spent 3(not full)days on this and chrome is still tearing about as bad as I'm tearing my hair out on this, I've done everything I can think of... other than a reinstall of chrome, history is too important, already had a scare of loosing it once, barely got it back, or a reinstall of OS, and f that everything else is fine and that's kinda scorched earth stuff. any ideas? I fix computers with my Father for business so us not finding a solution doesn't happen often, but I'm willing to admit defeat here. (as long as somebody comes up with something that will fix it that I haven't looked at already, otherwise the battle is still on)
edit 1: side note, I've had this system since November 2015 and this problem just popped up about the same time I started working on it plus however long it took to annoy me enough to want to fix it
edit 1: side note, I've had this system since November 2015 and this problem just popped up about the same time I started working on it plus however long it took to annoy me enough to want to fix it
Facebook
Twitter
Instagram