ok so I took the 16” MacBook Pro that was having KPs and wiped it.
Erased the entire partition table from Internet Recovery and started from scratch.
Reinstalled MacOS 10.15.4 (which is the only option for this machine from Internet recovery.)
Went into the OS and loaded my iCloud account. I let it finish syncing content from iCloud Drive and boom! After the display went to sleep for some time I tried to wake it only to find it has kernel panicked with the same messages we’ve all been experiencing.
It was plugged in and setup by default to use PowerNap while plugged in.
I then installed the developer beta profile, downloaded and installed Developer Beta 4 of MacOS 10.15.5.
I left the machine alone all night and let it finish syncing data. No kernel panic. And it was plugged in with Power Nap enabled.
Theory: Something is happening to affected machines running 10.15.4 that seems to have been addressed (although perhaps not completely fixed) in 10.15.5 betas 3 and 4.
I have only witnessed one kernel panic on one of two exactly IDENTICAL 16” MacBook Pro’s running these two betas. And that Kernel
Panic occurred on a machine that has been upgraded from 10.15.3 to 10.15.4 and then to Dev Beta 10.15.5.
The other machine (with no kernel panics) arrived from Apple brand new with 10.15.3. I then installed 10.15.5 Betas 3 and 4 and have yet to experience any similar kernel panics to those the other machine (once running 10.15.4) was exhibiting.
So this current set of tests (wiping and reinstalling from scratch, then updating to latest Dev Beta) is to assess whether the Memory Corruption Kernel Panic (which was different from all the others reported and those I had been experiencing since 10.15.4) was due to corruption of certain system files from the repeated crashes or from the upgrade path taken vs a possible hardware fault.
Outside of a hardware fault or potential data corruption I am struggling to explain why two identical machines would behave differently.
but if this indeed is purely hardware related then Apple has a much bigger problem on their hands with the 2019 16” MacBook Pro based on the sheer volume of reports. Still I’m doubtful of this scenario given the reports have been centered primarily around the release of 10.15.4 and one other Catalina version prior to 10.15.3.