Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
To all of you that are suffering from this problem, these kernel panicks are almost always caused by 3rd party kernel extensions UNLESS you have a hardware failure.

To see the 3rd party installed kernel extensions, open Terminal and type:
Code:
kextstat | grep -v apple

You will see the 3rd party extensions listed there. I suggest that you go thru the regular uninstallation procedures of all the software that are related to those extensions. If you don't know the software that is responsible from that extensions OR if the kernel extensions is still there even after the installation, I suggest that you go ahead and manually remove the .kext folder from your system. The steps are as follows:

The kernel extensions are stored in 2 locations. Either
/Library/Extensions
or
/System/Library/Extensions

Once you located the 3rd party .kext folder in either of these paths, remove the extensions by typing the following command:
Code:
sudo rm -R type_the_name_of_the_3rd_party_kext_file.kext/

of course by replacing the word type_the_name_of_the_3rd_party_kext_file with your .kext file's name.

Once you removed the kernel extensions, reboot your computer and enjoy. If you are still facing with issues, then you have a hardware problem and need to send your device in for repair. Oh, you're welcome.
To all of you that are suffering from this problem, these kernel panicks are almost always caused by 3rd party kernel extensions UNLESS you have a hardware failure.

To see the 3rd party installed kernel extensions, open Terminal and type:
Code:
kextstat | grep -v apple

You will see the 3rd party extensions listed there. I suggest that you go thru the regular uninstallation procedures of all the software that are related to those extensions. If you don't know the software that is responsible from that extensions OR if the kernel extensions is still there even after the installation, I suggest that you go ahead and manually remove the .kext folder from your system. The steps are as follows:

The kernel extensions are stored in 2 locations. Either
/Library/Extensions
or
/System/Library/Extensions

Once you located the 3rd party .kext folder in either of these paths, remove the extensions by typing the following command:
Code:
sudo rm -R type_the_name_of_the_3rd_party_kext_file.kext/

of course by replacing the word type_the_name_of_the_3rd_party_kext_file with your .kext file's name.

Once you removed the kernel extensions, reboot your computer and enjoy. If you are still facing with issues, then you have a hardware problem and need to send your device in for repair. Oh, you're welcome.

This solved it for me. Had issue that after sleep, I could wake my iMac 27-late2017 (macOS High Sierra 10.13.4), get login screen and after entering the password it would freeze. Turned out to be Bitdefender 6.12.0.2 that caused this issue. After removing bitdefender the issue was solved.
 
Had a nice time with almost a month of uptime, and then suddenly the problems kept coming back. Replaced top case with battery + motherboard through Apple Certified Repair Center, but the problems persisted Flickering is also back. Everything seems to be happening when I try to wake the machine from sleep/clamshell down.

MacBook Pro 15 from 2016 (450 Radeon), and I usually get a reboot without error message upon wake when disconnected from external screen, its late and typing the command for uptime confirms that a reboot has happened. Flickering happens every other day upon sleep when not used with external monitor.

 
Had a nice time with almost a month of uptime, and then suddenly the problems kept coming back. Replaced top case with battery + motherboard through Apple Certified Repair Center, but the problems persisted Flickering is also back. Everything seems to be happening when I try to wake the machine from sleep/clamshell down.

MacBook Pro 15 from 2016 (450 Radeon), and I usually get a reboot without error message upon wake when disconnected from external screen, its late and typing the command for uptime confirms that a reboot has happened. Flickering happens every other day upon sleep when not used with external monitor.


Hadn't seen this thread before - looks pretty much like the problem I'm having (second video, *no* external monitor). This is on a

MacBook Pro (15-inch, 2016)
Processor 2.7 GHz Intel Core i7
Memory 16 GB 2133 MHz LPDDR3
Graphics Radeon Pro 455 2048 MB
Intel HD Graphics 530 1536 MB


running
macOS High Sierra
Version 10.13.4

Since you hadn't mentioned what you did to get rid of the flickering: I opened System Preferences -> Energy Saver and unchecked/checked "Automatic graphics switching".

I have also noticed that the screen flashes up all pink sometimes when the MBP wakes up from sleep. Not sure if this is in any way related.

Today I was looking at a Video using VLC (3.0.3) in full screen mode. I tapped on the touch bar to activate the escape key, tapped again after the touch bar "woke up" and got a kernel panic (not the first time this has happened in this exact use case!):

Anonymous UUID: 9E5B9C83-037C-AE1A-BAF7-9619AEE62CCA

Mon Jun 4 21:50:42 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff800ac9a005): "Graphics firmware encountered an exception: 0xd, from EIP = 0x159e5\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.32.48/Common/GLKernel/Intel/skl/sched3/IGGuC.cpp:800
Backtrace (CPU 0), Frame : Return Address
0xffffff81f71c3c10 : 0xffffff800a66e166
0xffffff81f71c3c60 : 0xffffff800a796714
0xffffff81f71c3ca0 : 0xffffff800a788a00
0xffffff81f71c3d20 : 0xffffff800a620180
0xffffff81f71c3d40 : 0xffffff800a66dbdc
0xffffff81f71c3e70 : 0xffffff800a66d99c
0xffffff81f71c3ed0 : 0xffffff800ac9a005
0xffffff81f71c3f30 : 0xffffff800ac98772
0xffffff81f71c3f70 : 0xffffff800ac97dac
0xffffff81f71c3fa0 : 0xffffff800a61f4f7

BSD process name corresponding to current thread: kernel_task

Mac OS version:
17E202

Kernel version:
Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64
Kernel UUID: 7134F18E-AAC2-3C5B-B2C4-ABB799B4B9DF
Kernel slide: 0x000000000a400000
Kernel text base: 0xffffff800a600000
__HIB text base: 0xffffff800a500000
System model name: MacBookPro13,3 (Mac-A5C67F76ED83108C)


Since someone mentioned 3rd party kexts: I had been using VirtualBox earlier today.
 
Since someone mentioned 3rd party kexts: I had been using VirtualBox earlier today.

Same happened to me and a technician at a Apple Certified Repair Shop could replicate the error even with a clean install. Got a refund, my money back, so now I am using my MacBook 12 until something better ships in October. I have also ordered a Surface Book 2 and will try out their new quad core 13.5" before taking a final decision.

I have also noticed that the screen flashes up all pink sometimes when the MBP wakes up from sleep. Not sure if this is in any way related.

Mine went green when waking up. Usually after some use. Mine started with 10.13.4. Have you tried 10.13.5 ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.