I FINALLY fixed the issue. Turns out I was using the wrong interface :$ You may now load the module. It should no longer cause kernel panics or unresponsive kernel