Originally Posted by Beatwolf
Interesting, some time ago when i posted about this no one knew how to fix this. How do you know what to set the pixel clock to?
I know by reading the way i have learned a few things(sorry couldn't resist). There has been a good deal of material in this thread regarding this but it has been recent(maybe earlier than some time ago?). If you search "front porch" or "custom timings"there is a good deal of info regarding lowering the resulting side effects of overclocking and how to effectively lower the pixel clock to lighten these side effects in the thread now. Some good starting points would also be to search in the catleap thread, this thread and take a look at the CRU thread as well(since it is the primary and most effective tool for doing this).
Essentially you need to know what each monitor timing setting actually does and how it effects the overclock(mainly the total pixel count but other do apply). With this you can benchmark the pixel clock in a negative since gauging the resulting image stability using some of the several previously mentioned test tools(powerstrip, UFOtest, refreshrate multitool). This will help to lessen the overall stress of data going over the cable which is what causes overclock side effects in PLS panels(very probably all panels to a certain degree).
After knowing a bit of what you are doing it is very easy and only takes a little time and effort(unless you start trying different cables, ports, drivers, etc) and will result in significantly less predominant side effects(no more panel uniformity issues, color retention, flickering, the occasional green line)
So do a search, read, test and let us know how it turns out.