Try removing the vbox family of modules before suspending. If this solves the kernel panic, the vbox modules can be added to the list of permanently removed modules before suspend so that these modules are loaded automatically after suspend:
Try removing the vbox family of modules before suspending. If this solves the kernel panic, the vbox modules can be added to the list of permanently removed modules before suspend so that these modules are loaded automatically after suspend: