Macbook Air M1 - Kernel Error code 86

Same error. Solved by terminating apps I installed last through Activity Monitor. One by one. Turned out AdGuard was causing this error for me.

My understanding is, that all Apple Computer with Apple Silicon processors (including the M1) do not have a SMC controller anymore. This is something that is only used with the Intel ones. It seems that macOS Big Sur is not 100 % compatible with the new processor and is still running a task that can't be completed. This should be fixed in an upcoming update.

Yes, the specific VPN (not want to identify it here) has client GUI and run in Rosetta.

The VPN provider has promised to provide new build for the ARM architecture soon. So I am just using back to Windows pc for the required VPN connection and kindly wait for the new build. That's why not check this msg in Mac in time, not bad excuse but still sorry for so late response.

Said above, this Mac Kernel error message still hope can be addressed soon. It is too frequent and messing all other console messages.

Do you have a no questions asked return policy in your country? It's like 14 days. Return it and get a new one. This does not seem to be a common problem, so you would have a low probability in getting another one with this issue.

R

UPDATE: I have since done a clean install of MacOS Big Sur 11.0.1 and nothing has changed. The Console Log shows the same "Failed to write (code) to SMC. Error code 86." about five times per second. (Do M1 Mac's even HAVE an SMC? Apple seems insistent that they don't... which might explain the failure to write to it.) Meanwhile I'm running the Intel version of the same MacOS Big Sur on a MacBook Air and this error has not appeared anywhere in the logs.

My bigger concern however is that my USB-C external SSD continues ejecting abruptly and the M1 Mac Mini occasionally crashes & reboots during sleep. I believe this is related to the USB-C driver because the error logs sent to Apple always mention a USB error. And -- so far -- plugging the same SSD into the USB-A port hasn't been ejected.

I'll keep experimenting as I anxiously wait the next version of Big Sur to fix all these problems.

Are you using a VPN "app" GUI? If so, is it running in Rosetta?

My earlier contributions here perhaps linked-together two unrelated issues...

1) I have learned my "unstable" ORICO TCM2-C3 USB-C 3.1 Gen-2 external drive had very old Realtek RTL9210B-CG firmware from March 2020 which has since been updated several times. Including specific fixes for Mac compatibility. I was able to find a Windows 10 app to flash the firmware to the current version and it has been flawless ever since. It was not easy to determine this and most purchasers probably would have just returned it and bought something else. But now that its firmware is current this little drive is very impressive indeed. It's writing at 786MB/s and reading at 725MB/s. More importantly I am no longer seeing any USB errors or messages in my M1 Mac Mini's Console output. And I feel a whole lot better about this new system as a result.

2) I continue to see multiple SMC Error Code 86 errors per second in the Console output. I don't believe this is hardware related nor do I believe exchanging it will fix the problem. I believe this is strictly an OS translation error as my Intel MacBook Air running Big Sur does not generate them. M1 Macs don't have an SMC; Intel Macs do. I'm hopeful that a subsequent update to Big Sur will remove this faulty code from the M1 kernel.

Thanks everyone for the knowledgeable advice as I worked through this problem. This was my first time contributing to this forum after referring to it for well over a decade.

I believe this is related to the USB-C driver because the error logs sent to Apple always mention a USB error.

Are you booting off of this drive? Some external devices have had issues with working with the mac.

what make and model of external drive

R

I have only used my own new Mac Mini but I believe ALL M1 Mac's will have this in the Console logs if you go looking for it. There is nothing wrong with your (my) computer. It is the sort of thing that slips-by with a xx.0.1 OS release. I respectfully suggest we don't panic and give Apple time to fix this minor, obscure annoyance. Since I updated the firmware of my external SSD my new Mini has been flawless.

Let's not for get AppleCare. Give them a call.

R

I'm definitely seeing the same, I'm on a MacBook Pro with the 1TB SSD. I am thinking that this might be a hardware issue with the SSD, and I see slowdowns on some behavior. I am going to try to swap the computer, I tried a complete re-install of the OS as well as updating to the beta version of Big Sur (11.1). I still see the same kernel error (kernel Failed to write key xxxxxxxx to SMC with error code 86) about 5 times a second.

Final update from me:

Spoke with AppleCare yesterday and explained the problem and steps taken so far (above). They confirmed I’d done everything they would suggest and were happy to talk about service options or returning under the 14-day remorse period.

We worked round the peraonalization issue/bug using the terminal steps here (https://support.apple.com/kb/HT211983), although predictably it didn’t fix the SMC error.

NB: The Tech also did seem surprised I’d gotten the personalization error given this should be fixed in 11.0.1 and asked if I was sure the unit came with 11.0.1 installed (which it did).

Most interestingly though was I heard from my other friend receiving a unit this week, and he too has the problem. This seems at odd with my other friend who says he can’t observe the problem in his unit received Wednesday.

As one last roll of the dice (and given the machine needed a full reinstall for my own setup anyway) I did a revive and restore from another machine using Configurator 2. This includes firmware too so should cover all bases. Alas the problem remains.

This probably exhausts my efforts now. It was interesting but now I just need to decide if to keep the machine. I likely will but I’d have preferred both my friends to have observed it, thus confirming it affects all units and is almost certainly a software issue.

Best wishes.

Is the SSD directly plugged into the Mac? I have been having these issues with dongles I've been using, especially with HDMI and DP, seems to have trouble.

I'm swapping to a full thunderbolt 3 dock as I think it will work a bit better for peripherals.

Not had bluetooth issues, yet. I've removed the cheap (£33 ugreen dongle) and things feel a lot better.

Still got the SMC error, but my wife's new m1 arrived last night, so will see if she gets the same error.

A contributor in another forum suggested that unplugging my M1 Mac Mini from power for several seconds would have the same effect as an old-fashioned SMC Reset. Thinking about that, I realized I hadn't unplugged it since I first set it up under MacOS 11.0.1 weeks ago. So I unplugged it, waited a bit, then plugged it back in. Maybe it's just psychological but it does seem to be more stable now. The pointer (brand-new Magic Trackpad 2) seems smoother and more responsive and I've had no bluetooth disconnects since. This infernal Kernel Error Code 86 continues to spam my Console logs at a rate of 4/sec and my WiFi DL speed is still one-third of what it should be. But overall things are going in the right direction. I believe the MacOS 11.1 update was mainly focused on under-the-hood Rosetta 2 improvements and I'm optimistic that whatever comes next will address these other issues. Fingers crossed!

Also seeing a lot of this in my logs. Kernel is regularly consuming 40-100% CPU according to Activity Monitor, and preventing me from getting the battery life I should be getting. Brand new MacBook Air M1 8GB / 512GB. Started out great last night, but this morning been a little sluggish and some beach balls.

Have tried restarts