Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

Question

Hi,

I was trying to remove a Logitech webcam's residual entries within my registry using regedit, as their software is terribly persistent even after an uninstall.  I was searching for everything with the keyword 'Logitech' and deleting it from the registry.  During the process, I seemed to have removed some entries that may have belonged to my CM-6501 onboard audio controller and now I have no sound.  When checking the device in Device Manager, I have the following error:

"Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"

I have tried removing the audio controller's drivers and re-installing them, which still results in the same problem.  I have no system restore point or image to revert back to.  I even re-installed the Logitech webcam but this didn't help resolve the audio controller's problems.

I didn't make a backup of the registry, something I always do beforehand, but for some reason failed to do this time.

What options do I have of repairing the current install and getting the audio controller to work again, either by removing the incomplete registry entries or restoring the parts that are missing?

Answer 1

 

I don't know what either values mean but I suspect the LowerFilters value might have something to do with Logitech? I could be wrong.

 

Yes, that is associated with Logitech and appears to a left-over from removing Logitech software.

That value will try to load the LVUSBS64.sys driver and if the LVUSBS64 does not exist on the system the issue will occur.

The ksthunk is normal and the default.

Try removing the LVUSBS64 value.

To remove the LVUSBS64 entry double-click LowerFilters and, under Value data, remove LVUSBS64  > OK

Create a system restore point beforehand and restart the computer after.

Answer 2

Glad that worked.

The UpperFilters and LowerFilters values determine what filter drivers, including third party filter drivers, are loaded for a device or devices.

If an UpperFilters and/or LowerFilters value exists in the registry but the corresponding .sys driver does not exist in the C\Windows\System32\drivers folder then an error, like you experienced, would occur. 

There is some more info on filter driver registry entries in the following link - it's for Vista but would generally apply to Windows 7:

http://support.microsoft.com/kb/976267/en-us

For the registry key in your case (Media) would affect audio, USB audio, etc.

Answer 3

Can you check the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E96C-E325-11CE-BFC1-08002BE10318}

At that registry key, in the right window, is there, under "Name", either an UpperFilters or LowerFilters value?

If so, for each of the UpperFilters and/or LowerFilters value, what is listed under "Data"?

Answer 4

@auggy - You are a magician!  It works!

I removed the value from the LowerFilters key and restarted.  Immediately, the CM-6501 audio controller is working normally again.  But how does removing that one key effect two devices?  I'm really interested.  Could you please explain further?

I must admit, I wasn't hopeful that your steps would work before trying them.  I was sure that I would have to populate the LowerFilters key with another .SYS driver file value that related to the CM-6501 in order to get it work.  I've since checked the registry, and it's still blank, even though the audio controller works.  So what do these two keys actually do, and what is responsible for populating them?

When having the problem, I didn't mention it, but lots of controllers related to the USB controller host and the PCI bus were failing too alongside the audio controller.  Those problems have also disappeared since blanking the registry key.

Answer 5

UpperFilters = ksthunk

LowerFilters = LVUSBS64

I don't know what either values mean but I suspect the LowerFilters value might have something to do with Logitech? I could be wrong.