PG42UQ strange problems black screen/freeze screen randomly

[tuanny87]

on firmware .31 got random black screen in the middle of game will not turn back on until i unplug power and replug. also had a random screen freeze in the middle of a game. and could not turn off or anything until i unpled. this all happen on overlock off @ 120 mhz since 138 mhz would not even wake up the screen sometimes when it goes to sleep.
also my rog logo randomly turned green looked in the manual but didnt see anything anout green logo not sure what does that mean?
hope they fix all these problem on the next firmware update or will have to return this monitor.

[Loremaker]

Greeny_SA wrote:
I've been doing testing on mine for the last few days and have some results. It would be great if someone else who has the same problem could run the same tests and see if they can replicate my results. Â* But... I think it might just be a matter of turning it off rather than leaving it on standby. If anyone else can check theirs, that would be great.

At the end of the day I turn off my PC, but wait 15 Minutes before turning of the monitor with the remote, then I turn off power completely.
I have newer seen the pixel refresh popup… tbh I am not sure whether pixel refresh is actually running. Should the led indicator on the monitor blink orange for 6+ minutes? I have seen it blink orange for a few seconds after turning of the PC.Â*

[Greeny_SA]

Loremaker wrote:
At the end of the day I turn off my PC, but wait 15 Minutes before turning of the monitor with the remote, then I turn off power completely.
I have newer seen the pixel refresh popup… tbh I am not sure whether pixel refresh is actually running. Should the led indicator on the monitor blink orange for 6+ minutes? I have seen it blink orange for a few seconds after turning of the PC.Â*

Was timing it to the exact same time as pixel refresh so I'm pretty confident that's what's going on when it goes black.

And on that note - It's been 1 week of just turning the screen off fully with the remote after using it all night, and it hasn't re-triggered the black screen once. So *touch wood*, I think that's what the problem was, at least for mine.

Would be great if some other people with the same issue could test that though and confirm. - Just turn it off off with the remote overnight.

[AustinT]

I tried that and it did not help anything. We shouldn't have to do that anyways.

[AustinT]

Adding my voice to choir...

Wish I had found this forum thread earlier, but I too have this issue on PG48UQ.
I contacted ASUS support about it, and after performing all the troubleshooting steps & even trying multiple computers/blu-ray players; ASUS had me send it back to them with an RMA. FedEx ended up smashing the monitor on the way, but FedEx took responsibility and ASUS fixed the screen. However, they didn't even attempt to fix the original issue. They didn't even watch the video of this issue I created.

Really frustrating and it seems like this issue isn't bubbling up to the right people yet, as either they are pretending they don't know about the issue or the people who should be informed have not yet.

I really hope the fix is just a FW change.

[Jiaszzz_ROG]

Hello, @AustinT .

We apologize for any inconvenience this may cause.
After completing the repair, has the problem you described been eliminated?
Please check the top right corner of the screen and kindly share the details requested in the PM inbox.

Thank you.

[AustinT]

Hello @Jiaszzz_ROG 

No, the problem wasn't eliminated for me and it doesn't sound like anyone else. If you look at the Amazon reviews and a professional reviewer on Youtube (https://www.youtube.com/watch?v=06TIUcfjA5o&lc=UgxshZu55zuTNIiLwqN4AaABAg.9oaagAj5Afv9oapcTHpRbf&ab_... Look at his comments. He didn't see the issue until after the video was made) you can see literally everyone is experiencing it who has made a review. 

I will continue this conversation in the PM inbox.

[Jiaszzz_ROG]

Hello, @AustinT .

I have updated the reply in the PM.
If possible, please share a detailed record of the video when the problem occurred, so that we can better understand the actual behavior of the situation.

Thank you.

[AustinT]

Sure, you'd be the first person to actually view it. I can tell via Youtube Analytics no one else has, even though I mentioned it multiple times in the RMA.

https://youtu.be/CaqPKyaJvTo

What happens before this: Literally nothing. I can be gaming, or I can have not touched my computer for a few minutes with nothing open. Or it can be playing a movie via my Blu Ray player.

[Doctor_Headlock]

Thought I would add my two cents to the discussion. I have the 48 inch version and I personally don't think it's an auto pixel cleaning issue as I've had it happen long before the 4 hour window, and sometimes even the same as the 42 inch version where the screen will switch off for a few seconds before coming back on again. Also, restarting my computer causes the display to come back when the monitor does shut off for what seems like indefinitely. That wouldn't happen if a pixel clean was happening as no cables are being unplugged. My guess? A firmware issue for sure, perhaps it is the firmware deciding it is time for a pixel clean, running the cut the display command with no pop up and not actually running the routine. Plus, I discovered that if you leave it for a minute it does come back, rather than the full six minutes as described from the cleaning routine. Plus, I've pulled the plug numerous times when the monitor has become unresponsive with no damage at all to the screen, which you would expect there to be if it was indeed doing a pixel clean.

[AustinT]

You make a good point, if it was "Pixel Cleaning", we wouldn't expect it to occur within a time period so close to previous manual "pixel cleaning" or previous "screen deactivation" (or whatever we want to name this issue...). Also, what I see when I activate the "pixel cleaning", the indicator LED turns blinking orange; whereas when the "screen deactivation" occurs, it just stays red as normal. 

So perhaps our hypothesis there is incorrect. How much longer until ASUS at least acknowledges the issue?
I really hope its just a FW fix and not a recall.