Windows 7 "Incompatible" Driver Blocking

[Jonathan_King]

Did you run the Upgrade Advisor before you installed Windows 7? It appears that your laptop does not support Windows 7.

Drivers & Downloads

Please run the Upgrade Advisor from this link: Free Download PC Upgrade Advisor Windows 7 Hardware Programs Issues

 

[theog]

Try part 2 in this tutorial:

http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

 

[TimStitt]

Hi Halfdemon,

I have a few thoughts.

• Do a search for libusb0.sys in your system, check the version of all installed that you find. You may have more than one. If you find more, remove all but one version to a usb stick. Reboot, test, swap if necessary. Remember to do an entire system wide search especially looking in SYSWOW64 drivers folder.
• You siad that you've installed twice, is this with a standard Windows 7 Disk (i.e. not a slipstreamed disk or anything non-MSfactory
• have you updated any other drivers recently, if they are faulty and sharing memory addresses Win7 will choose which one it thinks he issue is with and block it.
• Is there anything in your event log that could help us?
• What firewall / antivirus are you using, these can sometimes effect drivers.
• A final thought, your Certificate database may be damaged and perhaps windows can no longer find the certificate for the driver. I'll come back to this if all other angles fail.

- Timo

 

[Halfdemon]

Would it help to know that i occurred after a rather short sleep cycle(maybe 20 secs) and a bsod following wake?

 

[Halfdemon]

All the entries in my event logs relating to drivers not loading all point to the same sys file. The disc is straight from ms no slipstreams. I am using avg free latest version and updates. And how would i go about repairing the certificate database?

 

[TimStitt]

Would it help to know that i occurred after a rather short sleep cycle(maybe 20 secs) and a bsod following wake?

Every little bit of info helps

That's why I asked you the below info and Jonathan_King asked about the upgrade advisor........I'm going to add and remove some of my questions based on your update. thanks.

• Do a search for libusb0.sys in your system, check the version of all installed that you find. You may have more than one. If you find more, remove all but one version to a usb stick. Reboot, test, swap if necessary. Remember to do an entire system wide search especially looking in SYSWOW64 drivers folder.
  
• Have you updated any other drivers recently? If they are faulty and sharing memory addresses Win7 will choose which one it thinks he issue is with and block it.
• Your Certificate database may be damaged and perhaps windows can no longer find the certificate for the driver.
  

  Here's the official Microsoft Fix . The CRL may have become corrupt during a BSOD.

• Temporarily turn off sleep mode, there have been a number of drivers that have failed because they have not been written well to handle hit.
  There are two things here to turn off here:

1. Open Device Manager
2. Find your device/s with the issue and right click on it./them.
3. Select properties and see if your selcted device has a POWER MANAGEMENT tab.
4. If so, Untick the Allow the computer to turn off this device check box
   
5. Test for your issue
6. If the problem does not occur then go no further, if it still occurs
   Continue to step 7.....
7. Open control panel
8. Open Power Options
9. Change yoru Current Plan Settings
10. In the 'Put the computer to sleep' box, choose NEVER from the drop down.
    
11. Save Changes

-Timo

 

[Halfdemon]

Found the real culprit by mistake. I had looked over at one of my projects that had special software that required libusb win32 to be installed, unistalled it and fixed it. Thanks for all the help though. Hopefully this will eventually help someone else.

 

[TimStitt]

Found the real culprit by mistake. I had looked over at one of my projects that had special software that required libusb win32 to be installed, unistalled it and fixed it. Thanks for all the help though. Hopefully this will eventually help someone else.

Thanks for coming back to post that and you'r right it will help someone else.

From a technical perspective - the other driver likely shares the same memory allocation.

It's great to hear that your issue is resolved.