MacOS BigSur 11.3 restarts after sleeping

I too am having this issue with a 2017 MBP 15" as are many other people based on this thread from MacRumors: https://forums.macrumors.com/threads/mbp-kernel-panics-overnight-every-night.2294049/

I also tried disabling hibernate yesterday by using this command: sudo pmset -a hibernatemode 0

Unfortunately I woke up this morning and my Mac was off and I got the same kernel panic message that I get every morning. My system doesn't restart after just closing the lid. It only happens when I close it for the night and when I wake up the next morning, it is off. I have no issues if I close the lid throughout the course of the day.

It is unbelievable that over a week after the issue has been reported, Apple has not yet released 11.3.1 with a hot-fix.

The reports of this issue is extensive as mentioned in this thread and it appears that going with a clean install of 11.3 solves the issue, which is specifically related to 2017 mbp - but hey, who has the time of performing a clean install of macOS?

What strikes me is that nobody from apple has yet weigh in on the issue or provided a realistic solution time estimate.

To me disabling hibernation is not something I'm willing to do (even because the issue kicks in only after extended period of inactivity), I just rather switch Mac off overnight.

Cheers to the new AppleSoft, well-done.

I have now upgraded to Big Sur 11.4. We'll see what happens.

As I understand it, sudo pmset -a hibernatemode 0 does not prevent the suspend to RAM mode, but only the suspend to disk mode. The suspend to disk mode happens by default only after 24 hours or when the battery is empty.

So during one night everything is like in hibernatemode 3 - assuming the McBook has enough power.

I have had the MacBook in standby with the lid closed for about 4 hours during the day and did not get a kernel panic.

Same problem here, MacBook Pro

Diagnostics Information (past 7-30 days):

    2021-05-03 08:59:53 Kernel Panic (5 times)

        Details:

            panic(cpu 0 caller 0xffffff801216e4f9): "hibernate_lookup_paddr of 395

            2376 failed\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/2288acc43c/Li

            brary/Caches/com.apple.xbs/Sources/xnu/xnu-7195.101.1/osfmk/vm/vm_resi

            dent.c:8099

    2021-04-29 13:15:00 syspolicyd - High CPU Use

        Executable: /usr/libexec/syspolicyd

    2021-04-28 08:15:42 trustd - High CPU Use

        Executable: /usr/libexec/trustd

    2021-04-27 17:16:39 com.apple.WebKit.WebContent - High CPU Use

        Executable: /System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

    2021-04-27 08:17:00 routined - High CPU Use

        Executable: /usr/libexec/routined

    2021-04-26 11:11:41 SmartPSS.app - Crash (3 times)

        Executable: /Applications/SmartPSS.app

Have the exact same message after startup.

As many others here a 2017 15" MB Pro.

Ran MemTest86 after asking for help on reddit, this showed no issues. Disk Utility showed nothing. Reboot +D did exactly the same. Tried a few things without avail. Hoping Apple will resolve this issue soon.

Edit: after posting I saw Cesar231092's message, currently downloading, keeping my fingers crossed.

I have the same problem with 2017 MBP 15'' after Big Sur 11.4 update. It is very easy to replicate for me by changing the Battery options to turn of the display after 2min on battery. Once the display goes dark, only way to bring it back is by hard reboot.

I have sent my laptop to Apple for analysis of this issue, and they replaced my display module and sent back yesterday. But I still have the issue. So they have no clue as well.

Some back story on how I am still covered with Apple support for 2017 MBP... I have paid for my display to be replaced couple of weeks ago due to the Flexgate issue that apple does not acknowledge on 15 inch MacBooks.

I'm having the same issue on my MacBook Pro 15" (2017). Looks like it's affecting a lot of people after the Big Sur 11.3 update. All with the 15" 2017 MacBook.

2015 MPB, 13 inch, just updated to 11.4 and so far so good

I am having the same problem

It's happening every night- wake up in the morning and get the error message, then takes several minutes to get back to desktop. Very annoying...

2017 15" MacBook Pro

Big Sur macOS 11.3 (20E232)

The same issue at MacBook Pro 15-inch, 2017, after update into Big Sur 11.3: panic(cpu 0 caller 0xffffff800af6e4f9): "hibernate_lookup_paddr [...]".

Obviously a hardware issue - it seems that Apple is slowly killing Intel machines. All the computers mentioned here have T1 chip. T2 owners are next.

Interesting, have not tried to hibernate it yet but will do so. The upgrade contains two security fixes, no mention of fixing this problem. On MacRumour forums several people claim problem persists after upgrading to 11.3.1

I too am disappointed we have not heard a thing from anyone at Apple regarding a fix or "We're looking into it" or even a request for further information. I've been sending in kernel panic reports every time it happens.

I'm using 2017 Macbook Pro 15". until Big Sur 11 update 3-4 days ago, it was completely fine. But after the update, everytime it is going to standby for more than a while (at least few hours if not more), then it is unable to wake up. It crashes. I've to restart the machine and I lose all my work.

I reset NVRAM etc also. But didn't help.

This is my office laptop given by Intuit, and the work is really suffering a lot because of this. I've send the error report to Apple few times. Not sure how soon can i expect a fix.

I have a 2017 MacBook Air using Catalina 10.15.7 and this has been happening for the last three nights. I don't have anything attached to the MB and it is not plugged in overnight. It doesn't bother me particularly unless it is a symptom of something worse.