Freeze when Lid Open Dual monitor

Question

Level 1

10 points

Freeze when Lid Open Dual monitor

MBP Pro 15-inch, 2016 w Touch Bar
High Sierra 10.13.3
Intel Core I7, 16 GB Ram
Radeon Pro 450 2 GB

Hello everyone, I am facing an issue on my MBP when I use a dual monitor setup.

I use a 24'' QHD Monitor as a Main Monitor. Consequently, I keep the lid of my MBP closed most of the times.

Although, when I need to work, I usually open the lid of the laptop and use both displays in order to gain more space (obviously). Well, when I do that, it happens (not always, but often) that the Mac Freezes completely and I need to force a reboot. The two monitors shut down, the touch bar is still visible but not interactable.

I'm desperate, what could it be?

Have a nice day and thank you in advance.

MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.3), null

Posted on Feb 17, 2018 8:10 AM

Reply

Answer 1

Top-ranking reply

ShadowX24 Author

Level 1

10 points

Apr 4, 2018 1:27 PM in response to ShadowX24

Hello everyone, after such a long time of testing I can confirm installing a fresh copy of the OS solved my issue. No problems so far.

This can be closed, goodbye.

Reply

Answer 2

Joseph_S.

Community Specialist

Feb 18, 2018 8:37 AM in response to ShadowX24

Hi ShadowX24,

I understand that you generally use your MacBook Pro connected to an external display while in closed-display mode, but it stops responding when you open the display and you have to force it to restart to get it to work again. I'm happy to provide some help for this issue.

Based on what you've described, I recommend that you reset your SMC and NVRAM. Each of these can help with settings and display related issues:

How to reset the System Management Controller (SMC) on your Mac - Apple Support
How to reset NVRAM on your Mac - Apple Support

Thanks for using the Apple Support Communities. Cheers!

Reply

Answer 3

Feb 19, 2018 3:06 PM in response to ShadowX24

I started to use external monitor just a month ago, but, according to my colleagues, everything was fine on Sierra 10.12.5.

It is definetely not monitor or connection issue, cause some of us using direct USB-C, some USB-C-TO-HDMI with a variety of different monitors.

I suppose there is a bug in kernel extension. You can search google for "An Unpatched Kernel Bug", there is an interesting article...

Also, I'm pretty sure reinstall of OS will not help. But you can try upgrading to 10.13.4 beta or downgrading to Sierra. Unfortunately, I cant try that, cause it's my main work machine.

Reply

Answer 4

Feb 20, 2018 8:20 AM in response to ShadowX24

Hello! Do you face interface freezes when errors are occuring?

So... well... i see the following possible solutions (it depends on the problem's nature):

1. Some of MPB 15 2016 are affected (have physically failed GPUs).

So, the only things we can do: go to apple support and replace logicboard for the new one (if your warranty is not ended)

2. Practically all MBP 15 2016 are affected (have physically failed GPUs).

Recall should occur. But it can take years...

3. High Sierra kernel extension bug (Software/drivers related problem).

Wait for the fix.

Reply

Answer 5

Feb 20, 2018 3:48 PM in response to ShadowX24

Your Mac was designed to operate with the display open.

The point is was trying to make earlier was that closed display mode is not trivial. If you insist on asking for it to operate with the display closed, which normally puts it to sleep. MANY exceptions to "normal" operation must be invoked, and you will simply have to deal with them.

One of them appears to be the re-evalauation of what displays are connected. This happens in a very special way on a Mac.

To get a Mac display to become active, you need the Mac to query the display, and the display to answer with its name and capabilities. Otherwise, no data will be sent to the display.

This query is only sent at certain times:

• at startup

• at wake from sleep

• at insertion of the Mac-end of the display-cable, provided everything on that cable is ready-to-go

• on invoking Option-(Detect Display) button in Displays preferences

If your display does not respond for any reason, the display will remain dark. Many of todays multiple-input displays do not pay close enough attention, and they may miss the query from the Mac, and the Mac will then not send them data. you may be able to improve this by telling your display to focus on the Mac connection, or by using the port the display refers to as the Computer port.

Reply

Answer 6

Feb 20, 2018 8:36 AM in response to ShadowX24

To use your computer in closed-display mode, there are a number of complex ceremonies you need to follow exactly, or anything could happen to you -- restarts, shutdowns, unexpected sleep, and non-functional displays are likely:

Use your Mac notebook computer in closed-display mode with an external display - Apple Support

.

Reply

Answer 7

Feb 19, 2018 3:27 PM in response to ShadowX24

Well, just a few minutes ago I tried the following:

1. I've opened the lid (I was working in clamshell mode). Nothing happened.

2. I've unplugged the monitor. Nothing happened.

3. I've plugged the monitor back and closed the lid. Nothing happened.

4. I've opened the lid and got plenty of repeating errors in console:

сбой	02:21:25.055575 +0300	kernel	virtual void IOAccelFIFOChannel2::restart(): GPURestartSkipped stampIdx=1
сбой	02:21:25.055576 +0300	kernel	void IOAccelEventMachine2::restart_channel(): GPURestartEnd stampIdx=1 type=2
сбой	02:21:25.055582 +0300	kernel	void IOAccelEventMachine2::hardwareErrorEvent(): setting restart type to 2 (channel 16)
сбой	02:21:25.055584 +0300	kernel	void IOAccelEventMachine2::hardwareErrorEvent(): GPURestartDequeued stampIdx=16 type=2
сбой	02:21:25.155866 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.257063 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.358323 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459222 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459350 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459524 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459652 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459741 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.459873 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460046 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460165 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460255 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460333 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460451 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460557 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460649 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460765 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460846 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460928 +0300	kernel	virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
сбой	02:21:25.460931 +0300	kernel	void IOAccelEventMachine2::restart_channel(): GPURestartSkipped stampIdx=16 type=2
сбой	02:21:25.460933 +0300	kernel	void IOAccelEventMachine2::restart_channel(): no channel associated with stamp_idx 16 (type 2)

So, sometimes it hangs completely, sometimes it causes these errors.

Moreover, errors are repeating every 5-10 seconds and laptop freezes for a while.

Can you try the same?

Reply

Answer 8

Feb 19, 2018 2:19 PM in response to ShadowX24

I have exactly the same issue on MBP 15 2016 (Radeon 455).

Moreover, I have colleagues who have the same issue on these laptops (also Radeon 455). We all are running HS 10.13.3. Music continues to play, but touch bar freezes and MBP becomes unresponsive. Hard reset is the only way...

Reply

Answer 9

Feb 20, 2018 1:23 PM in response to Grant Bennet-Alder

Official apple support page says:

Opening the internal display while in closed-display mode

Opening the display on your Mac notebook while it's in closed-display mode will have different results based on the operating system you're using.

OS X Lion 10.7 and later

If you open the lid of your supported Mac notebook computer running OS X Lion 10.7 and later while in closed-display mode, the display flickers to a blue screen after a few moments, and then both displays become active. Close the lid to return to closed-display mode.

So, nothing wrong should happen if i open the lid while working in clamshell mode. Or I'm not right?

Reply

Answer 10

ShadowX24 Author

Level 1

10 points

Feb 20, 2018 2:54 PM in response to AYaskevich

Hello AYaskevich.

I formatted my mac this evening, installed a clean 10.13.3. I haven't installed any software yet and, using Console app and trying to replicate the steps you've provided me yesterday, those errors did NOT show up. There are still a few like the ones I'm attaching in the picture. I'll test for a while, hoping the issue won't come back, and let you know in both cases.

Reply

Answer 11

Feb 19, 2018 3:50 PM in response to ShadowX24

Sure, It's console app, just select Errors and Faults:

Reply

Answer 12

Feb 20, 2018 4:43 PM in response to ShadowX24

Hello ShadowX24!

Thank you in advance! I'll wait for news from you

Can you list briefly what software do you use (was installed)?

Reply

Answer 13

ShadowX24 Author

Level 1

10 points

Feb 19, 2018 12:42 PM in response to ShadowX24

The issue persists. I noticed that the mac is not freezed, only the signal video is messed up. What could it be? I tried to wait for 1 minute and the screen becomes like this. Cursor is visible if I move the mouse.

Reply

Answer 14

ShadowX24 Author

Level 1

10 points

Feb 19, 2018 2:38 PM in response to AYaskevich

I'm backupping right now my data so I can install a fresh copy of 10.13.3, I'll let you know if something changes, even though I'm pretty sure it won't.

So I'm starting to think it's not a monitor / connection issue but a MBP issue.

PS: Did you notice if prior to 10.13.3 the issue was there? I can sincerely not remember.

Reply

Answer 15

ShadowX24 Author

Level 1

10 points

Feb 19, 2018 3:16 PM in response to AYaskevich

Very well, I can't update as well because I need this machine to be stable for work.

Can you link the article of the kernel bug you were talking about?

And, is it possible to reproduce the problem? I've tried in my ways but I just can't.

Reply

Freeze when Lid Open Dual monitor

Similar questions