MBPro late 2012 KernelPanic after update

I agree, the Kernel Panics do seem to favor bad memory. With bad memory items can sometimes become corrupt after a time. A .dmg file is many times compressed so that requires processing and bad memory can make that process fail. Many times bad memory is very hard to identify since it may require some very specific circumstances for the failure to appear.

With Memtest86 you can try selecting a different CPU option which may allow the failure to trigger sooner/more often. Unfortunately Apple hardware does not allow for some of the CPU options compared to a general PC.

Keep in mind the only useful diagnostic is one which reports an issue.

Edit: I doubt the SSD is the problem, but there is an easy way to check. Try installing macOS to an external USB3 drive. If you have no problems installing, booting, and using macOS from the external drive, then it may indicate the internal SSD may be bad (or perhaps has an APFS file system issue). If you have the same problems with the external drive, then the internal SSD is not the cause of the problems.

These panic reports from your original EtreCheck reports strongly suggest you have RAM memory errors.

In my opinion, you should give that possibility great weight in your decision-making process.

2022-01-16 18:15:13 Kernel Panic

Details:

panic(cpu 1 caller 0xffffff802c76adff): "Possible memory corruption: p

map_pv_remove(0xffffff803f7e6fa0,0x10dbd8000,0x88500, 0x80000000885000

76, 0xffffff913bf73c54, 0xfffffea62db0dec0): null pv_list, priors: 1"@

/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.82.8/o

sfmk/i386/pmap_internal.h:786

2022-01-16 10:45:11 Kernel Panic

Details:

panic(cpu 2 caller 0xffffff80230bf642): initproc exited -- exit reaso

n namespace 6 subcode 0x1 description: dyld cache load error: shared c

ache file open() failed

2022-01-15 23:12:46 installd Memory

Executable: /System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd

Your kernel panics recalled by EtreCheck suggest bad RAM memory.

<< I've run a REMBER test and got no issues. >>

please provide details about HOW you ran REMBER -- stand alone or inside MacOS -- and how long you ran it for.

I get the idea you are trying to create a duo boot of High Sierra and Mojave. Correct me if I am wrong. And High Sierra runs just fine.But installing Mojave will not complete. Could be memory, but since High Sierra runs, that gives me pause. I am assuming your volume is already set to AFPS. Here is an article on AFPS.https://eshop.macsales.com/blog/44596-partition-drives-create-apfs-containers-for-space-sharing-with-disk-utility/ I have an article on installing a second volume using APFS. You may have already tried this, but here it is anyway.https://macpaw.com/how-to/dual-boot-high-sierra-and-mojave Forget the cleanmymac crap. You should be able to create an external boot disk of Mojave and run it. If not that would be telling.

You could download and run memtest86 and create a bootable usb flash drive to run it on.Isolating bad DRAM or memory bank after k… - Apple Community Are you running the Mojave instal with peripherals running or connected? If so don't. Your MacBook Pro is upgradable to Catalina. You ram memory is removable and replaceable , I don't understand (can do nothing to fix it). You would have to have a bad memory slot. You have Mojave on secondary volume. can you boot to it?

Late 2012 is a retina model, so it does NOT have replaceable RAM modules -- it is the first to have the RAM soldered to the mainboard for maximum reliability.

The EtreCheck report confirms NOT upgradeable (and implies not replaceable either).

I missed that it's a MacBook Pro 2012 Retina. Which means your right . The non retina mid 2012 is upgradable. I tend to forget when Macintosh went to the soldered in memory.