Description:*BSOD* Kmode Exception Not Handled. Aksdf.sys


This only affects Windows 2012 Servers with Sentinel HASP key drivers by SafeNet


Version: The issue was caused by a Windows Security Update that was released on 2/21/2018 Update (KB4076493) and will not commit the update until a reboot.


Solution:

To Fix the issue:


Boot the Server in “safe mode” and let windows rollback the update. To do so, when the server first boots up, keep hitting F8 until you see the ability to select additional boot options (the moment to start pressing the key is when the user sees the status of "scanning for devices" in the case of PIF's Dell Poweredge servers). If that does not work, as soon as you see the Windows logo, hold the power button to turn off the server. Performing this cycle 2 -3 times will boot you into the advance recovery options. From here select troubleshooting and then the option that will let you boot into safe mode (If server stuck in safe mode boot loop see below). 


Once into safe mode, uninstall the HASP key drivers from the USB section of Device Manager and go into the C:\Windows\System32\Drivers\ directory and delete the following files.


Aksdf.sys

Aksfridge.sys

Aksclass.sys

Akshasp.sys

Akshhl.sys

Aksusb.sys

Hardlock.sys


You can also search the registry for all instances of "hasp" and delete them.


Remove the Hasp Key from the back or inside of the server. It is a small black USB device, that looks a lot like a flash drive. It may have a red light on the end. If you have moved over to the Eclipse software, you no longer need this device attached.



If you are still on Legacy Docstar, you will need to reinstall the latest drivers, so perform the following:


Install the latest Sentinel HASP drivers (7.80 or newer) which can be found at https://sentinelcustomer.gemalto.com/sentineldownloads/

OR (and stop services)

https://supportportal.thalesgroup.com/csm?sys_kb_id=979a4e21db92e78cfe0aff3dbf9619c6&id=kb_article_view&sysparm_rank=1&sysparm_tsqueryId=35376bfadbb8e45091a9742339961994&sysparm_article=KB0018319

You will need the Command Line Run-Time installer.

To run the Command Line Installer extract it to the root of the C: Drive, open a command prompt and type in the following.

C:\haspdinst.exe -i



To get Windows Server out of “Safe Mode” Boot Loop:

  1. In troubleshooting options click on Command prompt
  2. At the command prompt type in Regedit and hit enter
  3. Click on Computer in the left panel above the registry keys
  4. Click on File then choose export and save to the C:\windows\system32\cofig\RegBack\ directory
  5. Take note of drive letters as you will need this to replace the registry and backup files.
  6.  Go back to command prompt and type in 
xcopy /e C:\Windows\System32\Config\*.* D:\RegBackup


        7. Press enter. If prompted for directory or file, choose d for directory. The D: drive will act as your backup location in case something goes wrong.

        8. Go to command prompt and type 

xcopy C:\Windows\System32\Config\RegBack\*.* C:\Windows\System32\Config\


        9.Press enter. Hit A for All

        10. In Command Prompt type

BCDEDIT /SET {Current} recoveryenabled


        11. Press NO and hit enter.

        12.Type exit and choose “Turn Off PC”

        13. Now boot PC in NORMAL MODE and the system will revert the updates and you can now remove the HASP drivers and update the as described earlier in this document