BSOD (IRQ_NOT_LESS_THAN...) when trying to install a modem in vmware

Posted on 2009-06-30
Last Modified: 2012-05-07
I did this about 6 months ago using the digi anywhere usb and best data 56k modem. and it worked fine.  Following the same procedure as before, this time when installing the driver for the modem, it blue screens with the IRQ_NOT_LESS...

The only difference this time is that I'm using a vm that was physical (converted from physical to virtual).  Would that have anything to do with it?  Perhaps a device that was left over in device manager when the machine was physical that is causing a conflict?
Question by:vianceadmin
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2

Expert Comment

ID: 24746896
(I hope you have a backup. Before tinkering..)

Couple things I'd like to know:
 Before installing / attaching the virtual HW to the virtual machine, did you install the driver to the OS?
   (Some instructions require this. and may not be good for the vm.)

 Have you tried to install a generic modem driver, then attach the port to the virtual machine?

The BSOD is definitly a driver issue - and USB drivers have always been ... touchy.


Author Comment

ID: 24748226
No, the way I did it in the past with the other server was to connect the USB over IP device on the network, install the drivers for the USB device on the server (so the server would see it), connect to it and once connected to the USB over IP hub, the modem that was connected to the hub showed up in device manager and I then installed the driver for it.  

I have read this is the only way to get a vm to see a modem (since ESX doesn't support PCI modems).  I did come across an article about removing un-needed hardware when you virtualize a physical machine.  I ran the command SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then in device manager change the view to show hidden devices and I did see quite a few devices (that were present when the machine was physical but are no longer needed).  I removed the old PCI modems that were still in device manager but I still see these (attached).  Could one of these old devices be causing a problem?  Should I uninstall each of them?


Author Comment

ID: 24748831
Re-ran the command SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and devmgmt.msc in the command prompt and removed all old modems/network connections again (there were a few leftover).  Rebooted and same blue screen.  Obviously, it's a conflict with a "phantom" device that is no longer on the server but it still remembers the device from it's "physical" days....How do I find out what "phantom device" is causing the issue?

Accepted Solution

schriste earned 500 total points
ID: 24753540
So, We are looking at a 'legacy' driver / hardware situation.

Firstly, and I should have asked this before,  there is a limited list of 'valid' hardware for VMWare - does this modem meet the Hardware Compatability List?


Just a thought, and it is a doozy, you may want to sysprep - clean out all the hardware and related drivers and let it do a 'from scratch' rebuild of the HW.  I honestly don't know if Sysprep works for VMWare.  We use Acronis for copying full server installs, which when using the 'Universal Restore' option, is just like booting from a sysprep-ed system. We have sucessfully booted to Virtual Machine a few times, some HW didn't detect until we dropped in the VMWare tools though.


Author Comment

ID: 24766271
Couldn't figure this out.  Seems like if I try to install the modem on a machine that was physical that has been virtualized using the vmware converter, the vm will blue screen.  Tested it on a machine that was virtualized from scratch (not converted) and modem installs fine.  Going to leave it as is on that server...

Thanks for your help though...

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question