AnywhereUSB BSOD

Have a new AnywhereUSB 2 port. Getting intermittent BSOD’s. Version is 2.7.00 of the driver. AWVUSB.SYS is what it is bluescreening on. Pls see attatched screenshot of BSOD. Anyhelp would be appreciated

Please try the latest beta AnywhereUSB driver, which has bug fixes related to bluescreens, then let me know if the bluescreens continue or not.



Loaded new driver and will let ya know how it goes. Thanks

Uggg, Uninstalled the old driver and reinstalled the new driver about 9am this morning. The server has rebooted and BSOD’ed again. I did not catch the screen scrape. Told it not to restart on error and I’ll catch the screen scrape when it happens again. Thanks.

BSOD’ed again. Got screen scrape if you want it.

Did not mention a driver this time.


Whatcha think?

I sent you a message through the forum with further instructions. Please check your inbox/messages for details.

Also please let me know what kind of USB devices you had connected to the AnywhereUSB (when the bluescreen happened), and if there was any pattern to the bluescreen, i.e. did it happen when you were interfacing with any of those devices or not, and was the AnywhereUSB idle or in use.

BSOD’ed again. Sent memory dump per your instructions. Thanks

Got your email. Have followed your instructions and waiting for the BSOD to happen again. It’s been up for 2 days, the longest so far! The device is a USB license key…Sentinel HASP Key from SafeNet Inc. To my knowledge, these BSOD’s have happened while the server was idle. Will find out for sure though.

running into the same problem with VM WIN2k8 R2 64-bit and safenet HASP dongle. After awhile my server will BSOD and complain about awvusbd64.sys. I’m currently using v3.10.20 driver on the VM server.

What bothers me is that no one (Safenet or Digi) wants to take ownership.
I don’t understand why Digi would pass the buck on this issue, as this would benefit the most.

So where I stand is; I’ve opened a case with Safenet,
If they don’t came back to me with a fix I will be returning my 8 AnywhereUSB/14 devices and explorer other options.

I wont be calling Digi support, as they seem like they don’t want to help and will pass the buck as soon as they can.

So to the real reason i’m posting on this thread is because I’m hoping someone has figured out the issue. the last post was back in 2010.
So if anyone has any info please post.


I don’t think it’s accurate to say that Digi is passing the buck.

Our engineering group has analyzed many memory dumps from customers who reported this issue to us (bluescreens when using AWUSB with SafeNet/Aladdin dongles, i.e. HASP), and they pinpointed the cause of the bluescreen to a bug in the dongle driver.

Unfortunately, we aren’t able to work around that bug. If we were able to work around it, we would be glad to (we have done those sorts of things in the past).

We have spent a considerable amount of time trying to get SafeNet to help us with this, but they do not seem interested.

We are very interested in helping SafeNet fix this. We need their cooperation though.

P.S. If you haven’t already, please open a support case with Digi, this way we can link your case with an internal “failure” for tracking purposes and notify you if/when there is ever a resolution to this issue.

the AnywhereUSB device and SafeNet HASP driver works great with physical machine, I only have the problem with a VM machine.
After talking with safeNet they stated that the driver it’s BSOD’ing on (AWVUSBD64.sys) is owned by you (Digi).
With that being said, has anyone is your company reached our to VMware?

current enviroment
-VM version 7
-Windows 2008 R2 64-bit standard
-4 core AMD processor 8431 2.41GHz
HASP driver - 5.95
Software that requies the HASP - Onxy X10 (ProductionHouse)

With the Pass the buck comment, Yes I feel that you guys are.

  1. Nowhere on your site states that your device is not 100% supported with SafeNet product
  2. When I called for support, your tech was quick in stating that it wasn’t our (Digi) problem call SafeNet. He didn’t suggest anything or offer any guidance.
  3. I feel that it is your responsibility to spearhead this issue and found a solution for your customers. Virtualization is the now and the future.

Hi there - I’m new to the forum, but I’m now having this same behavior on a Win2003 server. However, this behavior is new this weekend. In addition the users of an application on the machine have since started getting error messages saying that the USB dongle attached to the Digi is unavailable. A reboot of the server fixes the problem for a while.

I’m running a VM of the server in question. This used to be a physical box, but was running for over a month stable as a virtual. This past weekend was patching day. After installing the following list of patches I have started getting BSOD’s and unresponsive USB response from the dongles.

I am thinking that one of the patches I installed may have caused this to start happening. Any thoughts or theories would be greatly appreciated.

Updates (all microsloth)
KB2544521 (IE Update)
KB2530548 (IE Update)
KB2555917 (kernel mode drivers)

Thanks, Erik

We are having these same problems on 20 VMWare servers we have built for a new system. We are stymied on our project at this point.


To directly answer your question, we have not contacted VMware because we don’t think they are the cause of the issue.

I cannot explain why you are only seeing this issue with a virtual machine and not a physical machine.

Again, from analyzing many memory dumps from other customers who have reported similar issues, we have strong evidence which leads us to believe there is a bug in the dongle driver. We have opened a support case with SafeNet to discuss this with them (specifically to guide them on what they should fix), and it seemed to fall on deaf ears, so to speak.

While our driver may be mentioned in the memory dump, that doesn’t necessarily mean our driver is “at fault”. A more detailed investigation must be done (which we did) to accurately determine the source of the problem.

I can understand your frustration and hope that you understand that we’re just as interested as you at getting this fixed. We have spent countless hours on this issue. The fact is, SafeNet needs to help. Since you are in contact with them, please remind them that we are willing to help.

SafeNet has contacted us about this, and they now seem interested to help us work towards a resolution.

Our engineering group is in contact with their engineering group discussing this.

I’ll post an update here once I receive more information.


Do you have any SafeNet (possibly called Aladdin) dongles attached to the AnywhereUSB, or dongles that use the SafeNet driver?

We have rebuilt and reconfigured over 20 VMWare servers from 2008 to 2003 because of this issue based on the belief that 2003 was stable. I will need to check and see if any of these patches have been applied on our servers and if not whether applying them is going to result in the situation you have. That would be a very difficult result for us to deal with.

Hey Guys - I pulled all of the forementioned updates off the server and I’m still having weird behavior. I haven’t had a BSOD yet, but that was random anyhow. The application still has trouble finding the key.

Jeremy - In response to your question, yes, I do have a Safenet Key with the software installed and in fact I have 2 of them. One shows up as something from Rainbow Technologies and the other shows up as Aladdin. I’ve included the USB Key info below.

Device Descriptor:
bcdUSB: 0x0100
bDeviceClass: 0xFF
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x04B9 (Rainbow Technologies, Inc.)
idProduct: 0x0300
bcdDevice: 0x0200
iManufacturer: 0x02
iProduct: 0x01
iSerialNumber: 0x00
bNumConfigurations: 0x01

Device Descriptor:
bcdUSB: 0x0100
bDeviceClass: 0xFF
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0529 (Aladdin Knowledge Systems)
idProduct: 0x0001
bcdDevice: 0x0100
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x00
bNumConfigurations: 0x01


Related to the following issue that you reported…

“the users of an application on the machine have since started getting error messages saying that the USB dongle attached to the Digi is unavailable. A reboot of the server fixes the problem for a while.”

…first, I suggest determining if the AWUSB is connected (or not) to the VM when the issue happens. To do this, you can either:

  1. Look at the Port LEDs on front panel of the AWUSB. If it’s an AWUSB/2, AWUSB/5, or AWUSB TS-44 model, all of the Port LEDs should be solid green when it’s connected to a host PC. If it’s the AWUSB/14 model, then only the Port LEDs related to the Group in question (that he host PC is configured to connect to) should be solid green.


  1. Look in Windows Device Manager. Is the dongle listed in Device Manager (where it should normally be) without any yellow warning icons?

If the AWUSB and dongle are still connected at the time of the failure, you may want to try some of the suggestions in the KB article linked below.

Hey Jeremy - I will go through the KB article and report back my findings.