Big Sur crash restart loop after update

Question

Luismartinez OP

Created Aug ’20

Replies 50

Boosts 0

Views 22k

Participants 49

So after updating my MacBook Pro 16 inch , it starts up , then once I log on , it just completely turns off and reboots

Code Block panic(cpu 9 caller 0xffffff800189dc5a): "Inconsistent OOL/copyout size on 0xffffff86e59a7ba0: expected 44, got 0 @0xffffff86e604bf48"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.40.44.151.1/osfmk/ipc/ipc_kmsg.c:5032
Backtrace (CPU 9), Frame : Return Address
0xffffffa0ee73b9b0 : 0xffffff80018be6ad 
0xffffffa0ee73ba00 : 0xffffff80019fef13 
0xffffffa0ee73ba40 : 0xffffff80019ef96a 
0xffffffa0ee73ba90 : 0xffffff8001863a2f 
0xffffffa0ee73bab0 : 0xffffff80018bdf4d 
0xffffffa0ee73bbd0 : 0xffffff80018be238 
0xffffffa0ee73bc40 : 0xffffff80020b9f1a 
0xffffffa0ee73bcb0 : 0xffffff800189dc5a 
0xffffffa0ee73bd10 : 0xffffff800189df92 
0xffffffa0ee73bda0 : 0xffffff800189e4b1 
0xffffffa0ee73bde0 : 0xffffff80018b126e 
0xffffffa0ee73be60 : 0xffffff80018b1d2a 
0xffffffa0ee73bef0 : 0xffffff80019d45e3 
0xffffffa0ee73bfa0 : 0xffffff8001864216 
Process name corresponding to current thread: endpointsecurityd
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Boost

Answer 1

Maleficent OP

Jan ’21

iMac kept crashing every few minutes. Uninstalling firefox had no effect. Restarted in recovery mode and reinstalled Big Sur which seemed to work, hasn't crashed for a couple of days.

0

Answer 2

Nola OP

Mar ’21

Still having this issue... So interrupting... Any solution for that?

0

Answer 3

Deranger OP

Mar ’21

I finally fixed my Late 2013 MBP, which has been rebooting whenever I log in since a fit of rage during Christmas Break, with an iphone backup and a resulting unintentional upgrade to Big Sur.
Safe mode would work. First time login with a new account would work. First time login with a new OS on a new drive would work. Otherwise, about the moment you would expect to see the Finder background, it would restart. I could not find any errors in boot logs.
Finally after having it turned off for a couple of weeks, and going back to an older install of Big Sur, I saw something different. A first boot sort of "I'm going to calibrate your battery" and when I clicked OK, it rebooted.
Turns out the battery was DEAD. 6% or less charge, and quite swollen. Don't know why I didn't notice that earlier. OS in Safe Mode did not call it a bad battery though, just that it was not charging.
Today I replaced the battery, and now it boots fine, logs in fine, reboots when I tell it to reboot. All is good again.
So, bad battery = no login, even though it was plugged in.

0

Answer 4

lbellani OP

Mar ’21

Had the same issue
My MBP (2017 tbar) kept restarting just after log in, even in safe mode.
I reinstalled OS and it started working fine again but just after 2 days same issue.

HAd to format and install from scratch. Now seems to be working fine

0

Answer 5

Neurophob0s OP

Jul ’21

Hi everyone. I just decided to share with you my experience.

After installing Norton Security with macOS Big Sur 11.4, my MPB16" 2019 started to behave like described. I'll add some detail. I had two accounts, normal user and admin user. Both of them could not connect to wifi network, and after a few minutes of work with both of them my computer's fans sped up noisy, black screen, computer rebooted and showed "your computer has rebooted because of a problem" screen (black screen, not the pop up already in logged os).

I tried to reinstall the os plenty of times maintaining my hard drive partitions scheme. At some point before the completion of the process, same issue, fan sped up abruptly and all went to reboot because of a problem. However this problem did not occur at all with safe mode, which could connect to wifi normally and did not crash, though it was really slow and heaty. I tried as well to update to Big Sur 11.5 from safe mode, no luck at all, because it reboots to complete and then the problem starts again blocking any progress.

The only solution for me was to delete the partition table. After reformatting the chosen drive for Macos, I could go into macosX base system and reinstall Big Sur onto it. So now I'm using it without any problem, it upgraded straight to 11.5 automatically.

I believe something (Norton? not sure) put in the hard drive some file acting like a ******, some persistent "venom" which was being constantly parsed even during os reinstall process. I don't know where it came from, not sure if this is an explanation. Deleting partition table "removed" it, so the clean install process could go over that sector which before was the place where this file, being parsed, caused the stop. Since the entire machine was under pressure even if idle, I believe this file was a service being run. The fact that safe mode run without any problem should confirm it. Unfortunately I was not able to map it and see what was it, because system monitor, when run, did not display anything, as it was being forbidden to access pids list.

So, while it's not a full solution, if you are dealing with this situation, deleting the old partition and making a clean reinstall solved everything for me. Hope it helps.

0