I had the same problem and now I think it's completely gone.
It turned out, after updating to Catalina, that old cron jobs start a single process everytime they should run.
I had a (forgotten) job running every minute and after a while I found hundreds of cron processes in Activity monitor, so I killed all of them and finally retake control on my computer.
Unfortunately, I can't comment, so here is my advice:
I would suggest not only to boot into internet recovery mode, but especially into safe mode/single user mode.
You can check the available startup options here.
Also, before you proceed with anything: Save your data either in a backup or just copy the files somewhere.
If you are unable to resolve this ...
The screenshot with the panic shows that the reason for the kernel panic was that launchd stopped running.
I would suggest looking at the log files for launchd to see if you can find the reason for that in there. Usually you'll see something like "exited at instruction [...]" or "trying to read/write [...]" or "[...] (sent by PID [...])" right before the ...
This was happening to me. I had a cron entry that was running a python3 script in virtual env.
check your crontab for anything running python. crontab -l
Install openssl with brew. brew install openssl.
Then for any script you find in your crontab, make sure it has the openssl lib paths first in the LD_LIBRARY path. Add this to either the shell ...
I have a 2019 macbook pro 15" running 10.15.2 and when I tried to open the intel power gadget, it crashed the entire computer and restarted. I got a message after the reboot saying the computer restarted because of a problem.
The crash log points to the kernel extension by intel. I also ran the command line to see the cause of the previous shutdown and it ...