SOLUTION to panic(cpu 0 caller 0xffffff8011a16487): "AppleIntelFramebuffer::setPowerState

I live in Japan and bought my 16MBP here. I have the same problem (panic(cpu 0 caller 0xffffff7f885333c5): "DSB0(MacBookPro16,1): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.141.1/IOPCIBridge.cpp:1398) as others. Before this problem set in, though, I had lost the ability to charge with the two USB-C ports on the right side. I still cannot charge from them and, yes, I have done the various resets which some people find fixes the problem. With these two ports unavailable, I most certainly have a hardware problem on an expensive computer which is 9 months old. I find that the 16MBP crashes when I close the shell. The timing of the crash is usually 30 secs though it has also taken as along as 50 sec. I am documenting now all the crashes. I get the same report as pasted above all the time. I did a complete reinstall of the OS (10.15.6) ad the problem remains. I have Apple Care and will demand a new machine. I am concerned, however, that the new device may have the same problem. This had been the very best computer I'd ever owned.

I have done everything I could for this issue. Downgraded to High Sierra. Problem persists. Upgraded to Mojave. Problem Persists. Upgraded to Catalina. Problem Persists. Upgraded to latest Big Sur Beta (Ver 11.0). Problem Persists. The only way I have truly found around it was to install a 3rd party program called "InsomniaX" which does not let the computer sleep when the lid is closed. I recently took the laptop to the Genius Bar, and they ran some tests, but their only solution for my 2015 MacBook Pro was to pay $479 and have the logic board replaced. At this point, that's about how much the laptop is worth. If there's anything I've found out about Apple laptops, is you are at the mercy of the hardware, and AppleCare is a wise investment if you're spending a lot of money on a laptop if they are all prone to this same issue that won't be fixed by software...ever!

I happen to own three other Macs, one MacBook Air 2013 (running Catalina, has same problem, but not very often). A MacBook Pro 15" 2015 (running Catalina, never had an issue), and a 2017 MacBook Pro 15" (running Catalina, never had an issue, but has a the random "popping" sound).

Note to self (and all of you): Just because it's an Apple device does NOT make it invincible to problems that other laptops and electronic devices all can get. If you buy used, be very careful. Look for continued Apple Care coverage in all future used OR NEW purchases.

It's a true shame that at least a 3rd party program can be a band-aid for 1st party hardware.

According to this thread, it is a 10.15.4 problem and is already fixed in the 10.15.5 beta, yay!

my 16inch macbook pro was a refurbished one.. i hope that it will be different with the nexr update