Contribute
Register

problem with memory panic stackshot succeeded ** bytes traced 13120 **

Status
Not open for further replies.
I have the same Problem on my HP Envy 15, All the kexts load, but after that, I get a memory panic stackshot.

Edit:
I managed to fix it by changing the config.plist file
 
Last edited:
I am currently doing a fresh install and I was having the same issue. I kept getting "In Memory Panic Stackshot" as soon as I booted macOS from my drive. I basically just updated Clover to r5112 in Clover Configurator and checked all the drivers I had in my UEFI folder minus VirtualSmc.efi cause it was not in there during installing r5112 and it booted up smoothly.
 
I am currently doing a fresh install and I was having the same issue. I kept getting "In Memory Panic Stackshot" as soon as I booted macOS from my drive. I basically just updated Clover to r5112 in Clover Configurator and checked all the drivers I had in my UEFI folder minus VirtualSmc.efi cause it was not in there during installing r5112 and it booted up smoothly.
I'm having the same issue with my install. I uploaded to r5114, didn't see the VirtualSmc.efi in my folder, and am getting the same issue... Anyone have any ideas?
 
Last edited:
What did you change?
 
This problem appeared after unsuccessful try of overcooking on z390 gigabyte Aorus elite motherboard .
The system looped on boot with this message: "problem with memory panic stackshot succeeded":banghead:
CMOS reset with jumper didn't helped.
But this method helped to boot system normaly::headbang:


  1. Shut off the power supply(by turning off the main switch). Wait for 10 seconds.
  2. Press and hold PC Power On button and then turn on the power supply.
  3. Release the PC Power On button once the PC starts.
  4. Shut off the power supply as quickly as possible thereafter.
  5. Turn the power supply back on
  6. Start PC as usual using Power on button
 
I am having the same error after a successful catalina installation on an ex58 board (!) and migration from high sierra. mine is happening in the early stage of the boot, after loading whatevergreen. curious. :D
 
Status
Not open for further replies.
Back
Top