MacOS – Kernel Problems randomly restarting MacMini Late 2012

You are correct that the recovery partition is not on your machine.

On my Lion machine I see:

$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            499.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

You could clone your existing drive "Crucial M4 SSD" to an external disk, then repartition and reinstall Lion, then clone it back, though reinstalling Lion over your existing volume may also work! You could also try downloading the Recovery Update and see if that can add it:

http://support.apple.com/kb/DL1464

The main points of this kernel panic are analogous to the mathematical direction to divide 5 by 0

The kernel / core of the OS got an instruction that cannot make sense, so it dumps all it knows about what it sees looking backwards and forces the user to start over.

The kext are kernel extensions and you sometimes can catch one that causes this. Similarly, the page fault (type 14) has to do with memory access. Similarly, if you have the source code you can sometimes use the backtrace to see what code was running on that CPU before the problem was raised.

Other times, the problem has messed up the logic so that none of the values make any sense.

You may notice that I'm not giving you a precise answer. That's because you usually need Apple's assistance to make sense of any particular log file - and even if you give them 10 log files with 10 corresponding panics, sometimes it's not clear what's causing it.

Can you ask a follow on question with specific request - like how to disable the VMware kernel extension or how to make sense of a pattern of crashes (you'll need to summarize them and compare the type of fault, possibly the BSD process name corresponding to current thread (and sometimes this is an innocent bystander and not the culprit) as well as any patterns of the kext activity.

You can learn more about debugging a KP from this excellent but technically challenging article:

• https://developer.apple.com/library/mac/technotes/tn2063/_index.html