10.13.4 Screen flicker after coming out of sleep

[lockerc18]

Having a problem after installing 10.13.4. When the system comes out of sleep, the display will often (but not always) flicker pretty rapidly in a seemingly random pattern. It won't stop until I close the lid and let it sit for a while, and then reopen it. This is on a 2017 MBP. I've never had this problem before. Without specific evidence, I think this a problem with the .4 update, and is not a hardware issue.

Anyone else see this problem?

 

[skelmi]

Same issue, had to restart and haven't been able to repeat the flickering. Maybe a problem with the integrated display driver? Also noticed full-screen videos in safari flickering when using volume controls etc.

 

[LogiLink]

Same problem here, MBPro 2017

 

[Trio2]

Same here - MBP 2017

 

[lockerc18]

It happened again just now. So, I closed Firefox, and it stopped. No clue if there's a bug in FF someplace, but that seems to have stopped the flickering, at least for now.

 

[lockerc18]

It happened again just now. So, I closed Firefox, and it stopped. No clue if there's a bug in FF someplace, but that seems to have stopped the flickering, at least for now.

Well, it just happened again, and FF was not active. So, it's not FF. I still don't think it's a hardware bug, either. I am convinced that it's a bug in the new release of 10.13.4. Stinks.

 

[lockerc18]

Well, it just happened again, and FF was not active. So, it's not FF. I still don't think it's a hardware bug, either. I am convinced that it's a bug in the new release of 10.13.4. Stinks.

Another data point... it just happened AGAIN. I found that it will stop if I move the cursor around. But when I release the cursor, it starts up again. I can close FF (and Safari) and that doesn't have an effect. Move the cursor, and as long as I move that, it does. I might need to contact the Genius bar about this one.

 

[lockerc18]

Another data point... it just happened AGAIN. I found that it will stop if I move the cursor around. But when I release the cursor, it starts up again. I can close FF (and Safari) and that doesn't have an effect. Move the cursor, and as long as I move that, it does. I might need to contact the Genius bar about this one.

OK, I think this might be the last post on this. I reset the PRAM and that seems to have fixed this. I don't know what the specifics are of what's kept in PRAM, but evidently something in that munged up the display when waking up. I haven't seen this issue for a while now.

 

[317342]

I'm seeing this, too. Any ideas of this is fixed in (upcoming) 10.13.5?

 

[knguyench]

The same, I don't next release is fixed? Late 2013 (MBPr)

 

[lockerc18]

OK, I think this might be the last post on this. I reset the PRAM and that seems to have fixed this. I don't know what the specifics are of what's kept in PRAM, but evidently something in that munged up the display when waking up. I haven't seen this issue for a while now.

As it turns out, no, this wasn't a fix. The problem still happens.

I saw a thread on a different site

https://www.tonymacx86.com/threads/...060-glitching-after-waking-from-sleep.220670/ , see post #1

that seemed to help. There was evidently a problem with the video driver. They were talking about a GTX1060 GPU, not the Intel HD Graphics 360 I have in my MBP. I don't know if the drivers are the same for both, but I suspect there's some similarity.

Anyway, one of the posters suggested that the problem can be temporarily corrected if you define a corner hotspot which puts the screen in sleep mode. When the screen flashes, just cursor over to that and let the screen sleep, then move the cursor back someplace else and the screen wakes up with no flashing. I tried it, and that does work on my system. It's not a fix per se, but at least it works for now.

I just installed 10.13.5 and that didn't fix the problem, so I hope there's a new driver included in Mojave.

 

[317342]

Has anyone tried it in 10.13.6 beta?

 

[Painter2002]

Having a problem after installing 10.13.4. When the system comes out of sleep, the display will often (but not always) flicker pretty rapidly in a seemingly random pattern. It won't stop until I close the lid and let it sit for a while, and then reopen it. This is on a 2017 MBP. I've never had this problem before. Without specific evidence, I think this a problem with the .4 update, and is not a hardware issue.

Anyone else see this problem?

Is it like a static/snow like screen glitch? If so, this is a major issue it appears that many people are having since 10.13.4. I started a thread about it and seems that many people have this issue too.

Thread: macbook-pro-2017-monitor-static-after-waking-from-sleep.2113498

 

[lockerc18]

Is it like a static/snow like screen glitch? If so, this is a major issue it appears that many people are having since 10.13.4. I started a thread about it and seems that many people have this issue too.

Thread: macbook-pro-2017-monitor-static-after-waking-from-sleep.2113498

No. The entire screen goes black for an instant, less than a second, then comes back on. It will do this in irregular cycles lasting less than a second forever if I don't put the system back to sleep again.

 

[erpoujfadslfewp123]

Has anyone tried it in 10.13.6 beta?

Hi,
yeah I tried with 10.14 - unfortunately no difference..

 

[lockerc18]

Hi,
yeah I tried with 10.14 - unfortunately no difference..

I have to admit, I had forgotten about this thread. I haven't seen this flickering since June. I don't know what happened. No complaints. Maybe there was a fix in 10.13.6 for this.

 

[the.marvian]

got the same issue here with my mac pro 13 2018 touch bar. os high sierra

 

[Lenones]

I have similar issues on MBP 13, 2018. My MBP started to discharge in sleep mode very quickly (for 8 hours at 35% minimum) and when you open the cover the screen flickers. And in sleep mode mac began to turn on the keyboard backlight. I visited the service center (twice), they said that there are no problems, and you come up with everything and the video is not proof. Maybe someone has already found a solution? Please share, a very unpleasant phenomenon, and the technical support.