Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Help with Kernel Panics Since Updating to 10.13.4
- Thread starter MacGarage
- Start date
- Sort by reaction score
Unfortunately, Disk Utility only gives me APFS options to reformat when I go to erase the SSD drive.
I do have the clone booted up on an HFS+ drive and will run that and see what happens.
Other than Disk First Aid, there does not appear to be a way to rebuild the disk's directory other than to reformat.
I was wondering if I boot into 10.12 and reformat, what would the HFS+ reformat do to the SSD in 10.13.4?
I do have the clone booted up on an HFS+ drive and will run that and see what happens.
Other than Disk First Aid, there does not appear to be a way to rebuild the disk's directory other than to reformat.
I was wondering if I boot into 10.12 and reformat, what would the HFS+ reformat do to the SSD in 10.13.4?
Last edited:
Make sure View > Show All Devices is set enabled - this is NOT the default view. Click on the top level physical disk. Should be able to hit ERASE and change drive format and partition table easily there.
Up and running with HFS+ formatted SSD and 10.13.4. Hopefully, this will do the trick...thanks!
Just a short update:
After about week of reformatting to HFS+, I have had zero kernel panics.
I did have one freeze waking up from sleep in one week. There was no error report. I did look at the console log and noticed that the IO Kit was mentioned a lot:
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: caller = /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: Version 2
Apr 23 07:45:22 Mac-Pro loginwindow[111]: version = 2
Apr 23 07:45:22 Mac-Pro loginwindow[111]: isModernOS = 1
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Add phase named "IOKit Boot", progress 58.007812, delayInSeconds 0
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: Clearing phase info
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Add phase named "loginwindow Boot", progress 41.992188, delayInSeconds -1
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Connection = 0x62c000115210, callers = (
"<IASUPCaller: 0x62c000026620>",
"<IASUPCaller: 0x608000025620>"
After about week of reformatting to HFS+, I have had zero kernel panics.
I did have one freeze waking up from sleep in one week. There was no error report. I did look at the console log and noticed that the IO Kit was mentioned a lot:
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: caller = /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: Version 2
Apr 23 07:45:22 Mac-Pro loginwindow[111]: version = 2
Apr 23 07:45:22 Mac-Pro loginwindow[111]: isModernOS = 1
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Add phase named "IOKit Boot", progress 58.007812, delayInSeconds 0
Apr 23 07:45:22 Mac-Pro Installer Progress[82]: Clearing phase info
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Add phase named "loginwindow Boot", progress 41.992188, delayInSeconds -1
Apr 23 07:45:22 Mac-Pro loginwindow[111]: Connection = 0x62c000115210, callers = (
"<IASUPCaller: 0x62c000026620>",
"<IASUPCaller: 0x608000025620>"
Yes...I also had unplugged an unused USB hub.
I have a USB Bluetooth dongle that I have to use but have that plugged in. This only happened one time in the past week.
I had a similar issue upgrading to High Sierra. Often I would not even see the panic log, the system just blew up and rebooted. It did appear to be related to APFS, since APFS disk activity seemed to accelerate crashes.
In the end it turned out to be an unknown preference in my account! In all my years I have never run across this.
The fix was to go into another account (I have an "Admin" on every one of my systems for resolving issues) and renaming my home directory. Logging back in created a fresh home directory without deleting the old info. I set up just the basics (mail, messages, etc.) and ran for a while. After I determined that there were no more crashes, I slowly added in Application Support and other files, but stayed away from preferences, any Services, and plug-ins. I downloaded those fresh.
Tedious, but rock stable ever since.
In the end it turned out to be an unknown preference in my account! In all my years I have never run across this.
The fix was to go into another account (I have an "Admin" on every one of my systems for resolving issues) and renaming my home directory. Logging back in created a fresh home directory without deleting the old info. I set up just the basics (mail, messages, etc.) and ran for a while. After I determined that there were no more crashes, I slowly added in Application Support and other files, but stayed away from preferences, any Services, and plug-ins. I downloaded those fresh.
Tedious, but rock stable ever since.
I have been having the same problem everyone else is writing about in Apple Support communities and all over the internet. I have sent 4 files x2 separate times to Apple engineering (4 gigs each time) and they have finally determine it is the embedded Raideon Pro Vega 64 video card which part of the motherboard (not plug in video card). I have new motherboard on order that is going to be replaced. I have also read about folks getting their iMac Pro replaced and the same problem happening with clean "Macs" with no additional software or peripherals (I am assuming Apple did not know with these folks that the GPU was the issue). My take is that Apple has found the problem and they probably had to get AMD to fix the GPU in their video card, so now the new motherboard and hopefully new AMD Raideon Pro Vega 64 card are fixed. I will let you know. If you are not sending large files to Apple to review (what I did) you may be wasting a lot time with all these theories out there. My reason for posting is, if everyone does what I did (send crash files to Apple), we may all get to the bottom of this quicker. I not certain this is the fix until I get the new motherboard with new embedded video card and the problem (kernel crashes) goes away. My kernel crashes happen now nonstop. that is another question, why did the frequency increase so much if it was always a hardware issue.