OT: (sort of) is there a conflict with...

filmy wrote on 5/24/2004, 5:43 PM
More crash related issues -

I have been getting the Blue Screen of death lately and it is related to USB and I did not get this before. So -

Recently i got a Lexmark P3500 printer. It is one of those all in one deals - scanner/printer/card reader. And more recently I got the ShuttleXpress (it came with the Vegas keyboard - also USB).

So the keyboard needed no drivers. The P3500 and the ShuttleXpress did. I can not find any sort of info and any conflicts so I am posting everwhere in hopes of a solution.

Oh - I had also installed the Vegas 5 demo if that helps

This seems random but I get a total stop Blue Screen of death. Usual blah-blahs and these last 2 times I wrote down what the cause(s) were. So here they are -

1> ausb2hub.sys - address F7C598F2 base at F7C58000, Date stamp 3dc1a5ea

2> ausb.sys - address F7B5441 base at F7B50000, date stamp 3dcla5f5

I have uninstalled and updated and re-installed the adaptec drivers.
I have also uninstalled and re-installed the Lexmark drivers.
I have made sure I have the newest drivers for the Lexmark, for the Adaptec and for the ShuttleXpress. Sp1a is installed.

ANy ideas? Anyone else know of any coflicts with lexmark/Adaptec/ShuttleXpress?
Still get the crash.

Comments

craftech wrote on 5/24/2004, 5:54 PM
There is an issue that sometimes occurs while installing drivers for add-in
cards (such as SCSI controllers and audio cards). Basically the Windows registry automatically records SOME info on the device but brands the info as 'read only' and will not allow the driver install to properly complete.
This can happen under both Win2000 and WinXP. To fix it, you'll need to
manually edit your registry. Back it up first.

Go to START, then RUN, and type "REGEDT32" (not "REGEDIT"). In the REGEDT32 program, find the window titled "HKEY_LOCAL_MACHINE" and maximize it. Open the following folders by double-clicking on them:

SYSTEM\CurrentControlSet\ENUM\PCI

You will see a lot of folders ('keys', in this case) named
"VEN_xxxxxxx..."
where "xxxxxx" are strings like "1102&DEV_0004&SUBSYS_00011103&REV_04".
Inside each of these folders will be a folder(s) with a long numerical name.
Click on each folder and look for an entry named "DeviceDesc" that has a
description containing the name of the device you are having trouble
installing. When you find the correct folder, click "SECURITY" then
"PERMISSIONS" from the REGEDT32 menu bar. In the window that opens select
"ALLOW" next to the "Full Control" option.

Close REGEDT32 and reinstall your drivers - they should install just fine,
now."

Hopefully, that solves the problem.

John