panic(cpu 1 caller 0xffffff8010cba220): "a freed zone element has been modified in zone kalloc.32:
expected 0xdeadbeefdeadbeef
but found 0xffffff80596ff7e0,
bits changed 0x2152416f87c2490f,
at offset 16 of 32
in element 0xffffff8061a823e0
The above is a classic 3rd party kernel extension panic.
You have the following 3rd party kernel extensions. Pick 1, pick them all. But at least one of these guys is responsible for your kernel panics
com.techsmith.TACC 1.0.2
com.Perfect.Driver.SystemAudioRecorder 1.0.0
com.hzsystems.terminus.driver 4
com.Cycling74.driver.Soundflower 1.6.7
at.obdev.nke.LittleSnitch 4740
it does not matter if you have identical systems. They are not operated in lock step, so they do different things, at different times, have different amounts of RAM being used, cause different bits of software to run at different time, and with different interactions between the software.
One of those kernel extensions is your problem.
The only other bit of information I can get from the panic report is that it happened in the I/O stack, but I do not know if it was file system or network I/O, so that leaves a broad area that could be the cause.