thanks for asking.

The crash log does not describe a kernel panic, but a crash of the 
application kextcache, which runs in user space. (I've changed the 
topic of this thread to reflect that)

As

- Remote Buddy is not running at this point

- the kernel extension does not do *anything* until after Remote Buddy 
is loaded and running

- the kernel extension does neither hack, patch, modify, replace, 
remove or otherwise alter any of your kernel extensions, functions or 
system files (it is *completely* system conform, using only documented 
APIs in an absolutely clean manner).

- Remote Buddy is not invoking kextcache at all (not even in its 
installer), following the advise in the kextcache man page

- and kextcache works *on* kernel extension files, but does neither 
load nor execute any code contained in them

neither Remote Buddy nor its kernel extension can be the cause of that 
tool's crash, sorry.

Also, googling for "kextcache crash" and "kextcache crash patchVTable" 
will lead you to a handful of similiar or even identical crash logs - 
some of which are predating even the first line of code of Remote 
Buddy by a year.

Best regards, 
Felix