So my fix is a shader to make sure the worst case conditions can never happen all at once. I would guess all these worst-case events for power consumption within the column driver, combined with probably 'barely passing qa' silicon, means that in edge cases the power sags, something gets reset, and the whole screen fails. It uses more power for grey values (because 255 or 0 are solid on or off, while mid values are typically dithered, wasting energy in the column capacitance). It uses more power during the row sync pulse (because it has to drive all the column lines to the correct voltages for whatever is being displayed). They take in serial data, and my 1920 screen has 4 column drivers, each responsible for 480 columns, so the 481st pixel is the first column that the 2nd column driver deals with. I'm pretty sure the problem is the column drivers (which put data onto the column lines). Eventually I found that if the red or blue pixel in the 481st column and the green pixel in the 482nd column have a difference of brightness of too much, and neither are 255 or 0, the screen dies. Then I erased parts of the frame to find which part caused it. Then I went through a video frame by frame to get to the frame it died on. Notably, greyscale videos never caused the issue. I noticed the screen only died when playing videos and always died at the same point if I rewatched a video.
0 kommentar(er)
