Big Sur crash restart loop after update

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





Big Sur crash restart loop after update

it seems to happen every 32+ mins, I have reinstall BigSur, but it doesn't seem to work... HELP

Macbook 2019 16 GB 2667 MHz DDR4
'2.3 GHz 8-Core Intel Core i9

I came across this issue on MBP 16 today w/ 11.0.1

(A variant of rellect's process)
Part 1:
Mac crashes at login screen, then boots up with Mac's equivalent of BSOD.
Once its recovers back to login screen. Press the shutdown icon to shutdown the Mac.
Press Cmd+R and power button to go to recovery mode. Then unlock by selecting my user account. Then unlock with my password.
Then shutdown, and press power button to boot back up to the login screen. Entered the password and it caused the crash again.

Part 2:
It recovered back to login screen again. Force shutdown by pressing button until the power goes off.
Then press the power button again to boot back up to the login screen.
Then entered the password to login normally.
Mac's security and privacy has a bunch of popus noting some kernel externs were disabled as they caused bootloop.
Disabled all the extensions from loading and everything seems to be back to normal.

It is clear that Part 1 didn't work, however, I am not sure if the second part worked because of part 1. I recommend just trying part 2 and if it doesn't help, then try part 1 and then part 2.

Hope it helps!
Same issue. Infinite crash loop. Apple, fix this! This is keeping me from making my living.
Same problem here on 11.0.1 (20B29) and it's not a beta version. This gonna be killing me. any solution?
I had a similar problem on my MBP 16 after installing Big Sur (11.0.1) via Software Update. Endless kernel panics and reboots. Safe mode did not work. Weirdly, in Recovery mode I could not get the APFS disk mounted. The system volume reported "Sealed: Broken" and my user data was locked by FileVault and I could not unlockVolume. I also could not reinstall Big Sur, as the installer was unable to unlock the disk and reported an "unexpected error". (Same thing in Disk Utility when attempting First Aid)

I took a bunch of steps, and am unsure which were the essential ones so I'm posting everything I did. Maybe this will help someone else.

1. Reset SMC
2. Booted into recovery mode
3. [Unsure if useful] Attempted to use 3rd party APFS file recovery utility (iBoySoft), running: sh <(curl URL hidden
4. Played around a bit with 3rd party tool but it didn’t work - it asked for password to unlock disk, but none I tried worked.
5. In terminal, tried “resetpassword” - and selected forgot password. For the first time, it let me change the password for my user (admin) account. It had me authenticate via iCloud and sent a trusted device request/confirmation code, etc. It seemed to suggest I was changing the FileVault password.
6. [Unsure if useful] Startup Security Utility (from pulldown menu in Recovery mode) now worked for the first time. I reduced security level to medium to boot any previously authorized OS
7. Reinstalled Big Sur from recovery mode - it was now able to unlock the disk
8. Reinstallation successful

On first boot, Big Sur reported some 3rd party extensions were causing reboot and have been disabled. Based on others' experience, I'm guessing this was the cause of the previously encountered kernel panics (?)

My best guess is that the essential steps were 1,2,5, maybe 6, and 7. Good luck
Update: Macbook pro 16 restarts every 12 minutes. I could transfer vital files from mac hd to an external drive after 15 times restarts. in meanwhile I download Catalina as well.
first try to make a bootable flash was failed. coz it takes more than 12 mintues.
I tried on faster sd card and it works.
I've done clean install with Catalina. It works well. #BigSur beautifully sucks. never ever upgrade.
I was able to fix this issue by performing the following steps:
  1. Restart into recovery mode by holding Command + R during start up.

  2. Click the Apple menu option and choose “Startup Disk”.

  3. Unlock your hard drive to choose it for booting.

  4. The computer should restart and return to normal.

I hope this helps!

jz1988 advice worked for me. thank you!
Hi all,

Managed to get mine to work again by booting into recovery mode, opening disk utility and performing first aid on the main volume, then doing the same on the data volume.

Booted up fine after that!
Happens two times for me. Any solution?
I have same problem, i format and install and loop reboot and black crash screen
I have same issue in my Macbook pro 13 inch. restart loop after update~~ any solution?

The same is happening on my iMac. Installed yesterday and now it keeps restarting again and again. I'm going to check to see if the time is similar to what another person posted (about 35 min). This is unacceptable and disrupting my work especially since I'm a university lecturer and all classes are online now. Get it fixed TODAY!
Try disabling both automatic graphics switching and enable power nap under battery and power adapter.
Path: System Preferences > Battery
i just wanted to add here, I had this issue and i tried all of these suggestions, none of which worked, but reinstalling the update in recovery mode worked for me.
I had the same issues. I tried the other suggestions but it didn't work. I was only able to boot and login to my session in safe mode (holding Cmd+S during startup).

I was then able to solve my problem with a RAM/PRAM reset : https://support.apple.com/en-us/HT204063

Good luck to all
I'm having similar issues - my Macbook keeps restarting randomly! Apple should really fix this immediately!

Besides from this, I'm having issues connecting to the Wifi and my personal hotspot randomly - the issues are completely messes up my working life these days. A restart often helps the internet connection issues, but I'm not prepared to have and expensive computer, and then having to go through so much trouble constantly. Also, restarting the computer doesn't work most of the time - it closes down some of the programs and then just stalls in the process letting me know that Preview hindered the restart - though Preview seems fine. In addition, the force quitting function doesn't work when I'm having this issue. Only option is harsh manual button down turn-off the computer.

On top of this my computer is struggling bad with a whole lot of ventilation-noise just from having my email, Word and Safari open.
Its a 2,3 GHz 8-Core Intel Core i9, Intel UHD Graphics 630 1536 MB from the end of 2019

Talked to the Danish Apple support last week and they reported that there were no general issues with the Big Sur update - should have googled before calling ;)
Never experienced so many systematic issues with Mac ever before - hope they fix this ASAP or I'll have to continue my PhD-thesis on a Windows computer

So I think I figured out the problem at least in my case. For whatever reason after I upgraded to big sur I found my fans were not kicking in when they were supposed to and as a result my computer temperatures ran really hot. I have turbo pro free extension that enables me to monitor my temp. So it would heat up, freeze and reboot.

I would have nothing more than a Firefox browser open and temp would run upto 90 degrees. So to fix this I reset the PRAM and SMC. Once I did that all is well. Fans kick in and my computer temp is between 55 and 70 Celsius now.

if this doesn’t work you can run diagnostic by rebooting your computer and pressing and holding down “D” on reboot. That will take you to run online diagnostics if the problem is something else. Hope this helps
i have same crash problems , do you have any plan now?

log:

{"filestoattach":["\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2020-12-25-005308.0003.ips"],"logpath":"\/Library\/Logs\/DiagnosticReports\/ProxiedDevice-Bridge\/panic-full-2020-12-25-005308.0003.ips","panicstring":"panic(cpu 8 caller 0xffffff80083fd817): \"IOSCSIPeripheralDeviceType00::setPowerState(0xffffff938d618520 : 0xffffff800a66d2e0, 3 -> 2) timed out after 251675 ms\"@\/AppleInternal\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-7195.60.75\/iokit\/Kernel\/IOServicePM.cpp:5382\nBacktrace (CPU 8), Frame : Return Address\n0xffffffa0b18fbac0 : 0xffffff8007cb9aed \n0xffffffa0b18fbb10 : 0xffffff8007dfc6e3 \n0xffffffa0b18fbb50 : 0xffffff8007decd1a \n0xffffffa0b18fbba0 : 0xffffff8007c5ea2f \n0xffffffa0b18fbbc0 : 0xffffff8007cb938d \n0xffffffa0b18fbce0 : 0xffffff8007cb9678 \n0xffffffa0b18fbd50 : 0xffffff80084be3ca \n0xffffffa0b18fbdc0 : 0xffffff80083fd817 \n0xffffffa0b18fbe10 : 0xffffff80083fd139 \n0xffffffa0b18fbe20 : 0xffffff8008415bee \n0xffffffa0b18fbe60 : 0xffffff80083fbeb8 \n0xffffffa0b18fbe80 : 0xffffff8007cfe6b5 \n0xffffffa0b18fbef0 : 0xffffff8007cff5c4 \n0xffffffa0b18fbfa0 : 0xffffff8007c5e13e \n\nProcess name corresponding to current thread: kerneltask\nBoot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev\n\nMac OS version:\n20C69\n\nKernel version:\nDarwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1\/RELEASEX8664\nKernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11\nKernelCache slide: 0x0000000007a00000\nKernelCache base: 0xffffff8007c00000\nKernel slide:   0x0000000007a10000\nKernel text base: 0xffffff8007c10000\nHIB text base: 0xffffff8007b00000\nSystem model name: MacBookPro16,1 (Mac-E1008331FDC96864)\nSystem shutdown begun: NO\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 1181858607489\nLast Sleep:      absolute      basetsc     basenano\n Uptime : 0x000001132c433446\n Sleep  : 0x0000000000000000 0x0000000000000000 0x0000000000000000\n Wake  : 0x0000000000000000 0x00000004793297ba 0x0000000000000000\nlast started kext at 366563964712: @filesystems.smbfs\t3.4.1 (addr 0xffffff7fa8e63000, size 434176)\nlast stopped kext at 485692278636: >usb.!UHostPacketFilter\t1.0 (addr 0xffffff800aa5b000, size 8192)\nloaded kexts:\n@filesystems.smbfs\t3.4.1\n@filesystems.exfat\t1.4\n|SCSITaskUserClient\t436.40.6\n>!APlatformEnabler\t2.7.0d0\n>AGPM\t119\n>X86PlatformShim\t1.0.0\n@filesystems.autofs\t3.0\n@fileutil\t20.036.15\n>!ATopCaseHIDEventDriver\t4020.6\n>!AHIDALSService\t1\n@kext.AMDRadeonX6000\t4.0.2\n@kext.AMDRadeonServiceManager\t4.0.2\n>!AUpstreamUserClient\t3.6.8\n>!AGraphicsDevicePolicy\t6.2.2\n>!A!IKBLGraphics\t16.0.1\n@AGDCPluginDisplayMetrics\t6.2.2\n>AGDCBacklightControl\t6.2.2\n>pmtelemetry\t1\n>LuaHardwareAccess\t1.0.16\n|IOUserEthernet\t1.0.1\n|IO!BSerialManager\t8.0.2f9\n>!AThunderboltIP\t4.0.3\n>BridgeAudioCommunication\t100.2\n>!AMCCSControl\t1.14\n>!AAVEBridge\t6.1\n>!AMuxControl2\t6.2.2\n@DontStealMacOS_X\t7.0.0\n>!AHV\t1\n>!ADiskImages2\t1\n>!A!ICFLGraphicsFramebuffer\t16.0.1\n>!ABridgeAudio!C\t100.2\n>!A!IPCHPMC\t2.0.1\n>!AGFXHDA\t100.1.431\n>!A!ISlowAdaptiveClocking\t4.0.0\n>usb.!UHostBillboardDevice\t1.0\n>BCMWLANFirmware4378.Hashstore\t1\n>BCMWLANFirmware4377.Hashstore\t1\n>BCMWLANFirmware4364.Hashstore\t1\n>BCMWLANFirmware4355.Hashstore\t1\n>!ABCMWLANBusInterfacePCIeMac\t1\n@filesystems.tmpfs\t1\n@filesystems.hfs.kext\t556.60.1\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n@filesystems.apfs\t1677.60.23\n@private.KextAudit\t1.0\n>!ASmartBatteryManager\t161.0.0\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n@!ASystemPolicy\t2.0.0\n@nke.applicationfirewall\t310\n|IOKitRegistryCompatibility\t1\n|EndpointSecurity\t1\n@kext.triggers\t1.0\n>!AHIDKeyboard\t222\n>!AHS!BDriver\t4020.6\n>IO!BHIDDriver\t8.0.2f9\n>!AActuatorDriver\t4400.28\n>!AMultitouchDriver\t4400.28\n>!AInputDeviceSupport\t4400.35\n@kext.AMDRadeonX6100HWLibs\t1.0\n>!ABacklightExpert\t1.1.0\n>X86PlatformPlugin\t1.0.0\n@kext.AMDRadeonX6000Framebuffer\t4.0.2\n>!ASMBus!C\t1.0.18d1\n>!AGraphicsControl\t6.2.2\n|IOAVB!F\t900.12\n@kext.AMDSupport\t4.0.2\n@!AGPUWrangler\t6.2.2\n|IOAccelerator!F2\t439.52\n@!AGraphicsDeviceControl\t6.2.2\n|IO!BHost!CUARTTransport\t8.0.2f9\n|IO!BHost!CTransport\t8.0.2f9\n>IOPlatformPlugin!F\t6.0.0d8\n|IONDRVSupport\t585\n|IOAudio!F\t300.6.1\n@vecLib.kext\t1.2.0\n@plugin.IOgPTPPlugin\t900.11\n|IOEthernetAVB!C\t1.1.0\n>!A!ILpssUARTv1\t3.0.60\n>!A!ILpssUARTCommon\t3.0.60\n>!AOnboardSerial\t1.0\n@kext.AMDRadeonX6000HWServices\t4.0.2\n|IOGraphics!F\t585\n|IOSlowAdaptiveClocking!F\t1.0.0\n>usb.!UHub\t1.2\n>usb.cdc.ncm\t5.0.0\n>usb.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n>!ABCMWLANCoreMac\t1.0.0\n|IOSerial!F\t11\n|IO80211!FV2\t1200.12.2b1\n>IOImageLoader\t1.0.0\n>corecapture\t1.0.4\n>!AThunderboltPCIDownAdapter\t4.1.1\n>!AThunderboltDPInAdapter\t8.1.4\n>!AThunderboltDPAdapter!F\t8.1.4\n>!AHPM\t3.4.4\n>!A!ILpssI2C!C\t3.0.60\n>!A!ILpssI2C\t3.0.60\n>!A!ILpssDmac\t3.0.60\n>!ABSDKextStarter\t3\n|IOSurface\t289.3\n|IOSkywalk!F\t1\n>mDNSOffloadUserClient\t1.0.1b8\n@filesystems.hfs.encodings.kext\t1\n>usb.!UVHCIBCE\t1.2\n>usb.!UVHCICommonBCE\t1.0\n>usb.!UVHCI\t1.2\n>usb.!UVHCICommon\t1.0\n>!AEffaceableNOR\t1.0\n|IOBufferCopy!C\t1.1.0\n|IOBufferCopyEngine!F\t1\n|IONVMe!F\t2.1.0\n>!AThunderboltNHI\t7.2.8\n|IOThunderbolt!F\t9.3.2\n|IOUSB!F\t900.4.2\n>usb.!UXHCIPCI\t1.2\n>usb.!UXHCI\t1.2\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2.1\n>!ASMCRTC\t1.0\n|IOSMBus!F\t1.1\n|IOHID!F\t2.0.0\n$!AImage4\t3.0.0\n|IOTimeSync!F\t900.11\n|IONetworking!F\t3.4\n>DiskImages\t493.0.0\n|IO!B!F\t8.0.2f9\n|IOReport!F\t47\n|IO!BPacketLogger\t8.0.2f9\n$quarantine\t4\n$sandbox\t300.0\n@kext.!AMatch\t1.0.0d1\n|CoreAnalytics!F\t1\n>!ASSE\t1.0\n>!AKeyStore\t2\n>!UTDM\t511.60.2\n|IOUSBMass!SDriver\t184.40.6\n|IOSCSIBlockCommandsDevice\t436.40.6\n|IO!S!F\t2.1\n|IOSCSIArchitectureModel!F\t436.40.6\n>!AMobileFileIntegrity\t1.0.5\n@kext.CoreTrust\t1\n>!AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n>!ACredentialManager\t1.0\n>KernelRelayHost\t1\n|IOUSBHost!F\t1.2\n>!UHostMergeProperties\t1.2\n>usb.!UCommon\t1.0\n>!ABusPower!C\t1.0\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n>watchdog\t1\n@kec.pthread\t1\n@kec.corecrypto\t11.1\n@kec.Libm\t1\n"}
I had a similar issue on my work laptop. To fix it, I had to upgrade Crowdstrike.
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.
Still having this issue... So interrupting... Any solution for that?
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.
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

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 trojan, 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.

Big Sur crash restart loop after update
 
 
Q