VB crashes when installing drivers for HASP SRM (Copyright protection USB dongle)

[Kristian Karl]

I get a bluescreen when installing drivers for HASP SRM (Copyright protection USB dongle). The crash occurs always. I have repeated the crash on a XP, and Windows 2000 guests.

Test instructions:

1. Start the guest OS (in this case XP)
2. When guest OS is up running, fetch the latest driver from Aladdin from ​here
3. Unzip the file, and run "HASP SRM Run-time GUI Installation"

Expected results:

• The installation of the drivers should ends successfully.

Actual results:

• During the istallation of the drivers, VirtualBox crashes

[Kristian Karl]

VBox log file

[Kristian Karl]

Sorry for the bad formatting above... I'll repost the description beneath:

VirtualBox crashes when installing drivers for HASP SRM (Copyright protection USB dongle). The crash occurs always.
I have repeated the crash on a XP, and Windows 2000 guests.

Test instructions:
============
1) Start the guest OS (in this case Windows XP)
2) When guest OS is up running, fetch the latest driver from Aladdin at: ​ftp://ftp.aladdin.com/pub/hasp/srm/Runtime_%28Drivers%29/HASP_SRM_Runtime_setup.zip
3) Unzip the file, and run "HASP SRM Run-time GUI Installation"

Expected results:
============
The installation of the drivers should end successfully.

Actual results:
==========
During the istallation of the drivers, VirtualBox crashes

[Kristian Karl]

Please note, that the actual hardware (the USB HASP dongle) is not necessary to repeat the crash.

[Kristian Karl]

I also get the same crash using Vista as a guest OS.

[Andreas Lange]

The problem is not related to USB. The problem appears to be in the instruction decoder of VirtualBox; the aksfridge.sys driver contains obfuscated code, which VirtualBox does not handle correctly.

[Mario Naiito]

Is there any workaround for the askfridge.sys problem?

[Frank Mehnert]

Right. Please could you activate VT-x for that VM session? Note that VT-x seems to be disabled in your BIOS (according to the log you added) so please check your BIOS settings. And after doing so, please make sure that VT-x is indeed enabled for the VM by checking the session information window (HostKey+N).