Kernel panics usually have nothing to do with hen or any other payload. Kernel panics usually occur during or straight after the kernel patching process.
Whenever you first run any payload after your PS4 has booted it basically goes through 3 stages.
- 1. First it runs a webkit exploit to gain basic access to the system.
- 2. When it has basic access it then runs the kernel exploit to patch the kernel and gain furthur access.
- 3. Once the kernel has been patched it then loads and runs the actual payload. Either Hen, FTP, BinLoader or whatever payload you selected.
Once the first payload has run on your PS4 and loaded correctly you will notice that all payloads you run after that load slightly faster.
This is because they do not have to do step 2 anymore because the kernel is already patched.
This is also why you dont get kernel paincs with other payloads you select after Hen has already been run.
There is another kind of 'soft' kernel panic that only occurs when you turn off your PS4. This usually happens when you run a lot of payloads after one another. (using Fan Control over and over is a good example of this)
You might not notice this at first because your system runs fine but when you shut it down the 'soft' kernel panic happens. The next time you turn on your PS4 you will notice that you have to press the power button twice to turn it on. (just like after a normal kernel panic)
I visualise the kernel patching process and kernel panics like this:
Imagine you are trying to jump through the open doors onto a fast moving bus.
Sometimes you jump cleanly through the open doors and everything is fine (Successful kernel exploit)
Other times you miss and Splat! (Instant Kernel panic)
Sometimes you make it through the doors but hit the sides on the way in. (Hen appears to load OK but it kernel panics a few seconds later!)
You try and jump onto moving bus but the doors are firmly closed! (You are not on 5.05 firmware and will never get in!)