Solved Are my audio drivers being re-installed at every boot?

[joehimself]

I can't find a solution on Google because there are too many threads relating to this general error but not my exact problem.
Can't think of any new installs that would affect my computer in the last week since this started.

On every boot up, W7x64 displays "Device driver was not successfully installed".

When I click this popup it displays a list of all my audio equipment with red 'x's (M-audio usb MIDI interface, Presonus usb audio interface, Creative internal sound card [not usb], and a software internal MIDI interface).

I close this list of errors popup, and all signs of trouble are gone! All devices are working! sfc /scannow passes, and Device Manager show no errors.

With the computer still on, if I turn off the power to the Presonus audio box, and then power it up again I get the exact same symptoms (except for the Presonus box only, of course).

A system restore to before the problem started didn't fix it, so I'm guessing it's not a registry problem..

Only Audio Drivers are in the "failed" list.
They have different connections:
2 are usb
one is internal software only and has no external connections
one is internal (pci buss sound card)

Please help.

 

[fireberd]

I have a recording studio (I use Sonar X3). I don't get this with my devices.

First thought is install/reinstall the Intel motherboard chipset drivers. Audio devices may or may not work (correctly) if the chipset drivers were not installed or are corrupted. As you have an Intel motherboard, you can go to the Intel site and get the correct chipset driver.

 

[joehimself]

Thanks firebird,
I have X3 also and this computer has been working fine with sonar 8.5, X2, and also x3, So I don't think it's sonar. This computer is almost 2 years old and has been running fine until 2 weeks ago. Actually it is still running fine RIGHT NOW! lol
I'm doing a recording project right now with X3.
I don't want to just ignore this as it's way past time for me to do my HD cloning for backup and I don't want to clone the HD if something is wrong with the system.

 

[fireberd]

Did you try the Intel motherboard chipset drivers? That would be a good start, as the chipset drivers identify all the hardware devices on the motherboard.

I have X3d Producer. I have a Roland Octa-Capture and an MAudio Fastrack Ultra 8R interfaces.

 

[joehimself]

I did just now update the Intel chipset drivers but I still have the problem.
Thanks for the idea, though.

 

[fireberd]

Try to narrow it down. Disconnect one or both USB devices and boot up. See if you get the error message. If you do not then one of the USB devices/drivers are causing this.

Do you have other USB devices? that you can temporarily disconnect.

 

[joehimself]

I did try that earlier and every combination if usb I could think of. e.g. if I unplug both usb audio devices I still get the failed install alert on my sound card and software midi port.

Isn't there a way to log the bootup procedure into a text file?. I'll try googling that tonight.

 

[joehimself]

Again, the biggest mystery for me is that everything actually ends up working as intended. It's the 'failed install' alert that worries me.

 

[fireberd]

After thinking about this, it could be something else not being installed correctly or the sequence in which the devices are installed that could be causing this.

Look at the startup in the MSCONFIG panel. Temporarily remove everything except what is essential (that may be hard to determine but what needs to be done) and then reboot and see what happens.

 

[joehimself]

I keep a very clean bootup list. There's only a few necessities in there. (no nVidia, Creative, Adobe, etc.)

And definitely nothing new or changed. Seems like if it were an actual driver problem it would end up being crippled as the last result. I was very surprised that a system restore didn't fix this.

Again I'll find out how to log a boot record tonight. Thanks, fireberd!

 

[ComputerGeek]

Device Manager keeps a log file of device install/uninstall events. It might have some insight to your problem.

• Delete C:\Windows\inf\setup.dev.log
• Reboot. (This should re-create the problem, right?)
• After the error message pops-up, wait 2 minutes then note the time.
• Open the error message. YOu see the problem? Wait two minutes again. note the time
• Close the error message. Things now look OK again? Note the time
• Zip and upload a copy of your C:\Windows\inf\setup.dev.log file

Also tell me the 3 times you noted above (so i can correlate those times to events in the log)

 

[joehimself]

Thanks Computergeek,
That sounds promising. I'll try it this evening when I get home.

 

[joehimself]

I don't have a 'C:\Windows\inf\setup.dev.log' file.

Additionally, I wouldn't be able to time the alert without clicking on it because the error notification goes away by itself within seconds (then everything works normally).

 

[ComputerGeek]

Sorry, my BAD! My typo

Do you see C:\Windows\inf\setupapi.dev or C:\Windows\inf\setupapi.dev.log? (Windows may have the .log extension hidden)

If not,
Open an elevated command prompt window, type regedit navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
> If there's a subkey LogPath delete it
> Is there a subkey named LogLevel? If it exists, it should have value 0

LogLevel    REG_DWORD    0x00000000

 

[joehimself]

No subkey LogPath

LogLevel = 2000ff00
Should I change this to "0"?

InstallationSources =
C:\Windows\System32\DriverStore
E:\DRIVERS SYSTEM\HARDWARE\ROCKETU 1144B USB 3.0 PORT\PLE8609_WIN_6.5.0.0\X64
E:\DRIVERS SYSTEM\HARDWARE\ROCKETU 1144B USB 3.0 PORT\PLE8609_WIN_6.5.0.0
E:\DRIVERS SYSTEM\HARDWARE\ROCKETU 1144B USB 3.0 PORT\ASM104XV1162WHQL
E:\DRIVERS SYSTEM\HARDWARE\DELL S2230MX MONITOR
INSTALLATION SOURCES

(RocketU is an internal USB 3.0 interface (internal) card

 

[joehimself]

Yes! I do see C:\Windows\inf\setupapi.dev and also setupapi.dev.20131212_073557.log
I would have already tried your first solution again, except that, as far as timing everything, The alert windows goes away by itself after a few seconds. (I'm guessing it goes away when everything gets fixed)

 

[Skits559]

Download DriverTuner? - download DriverTuner? to Update your pc drivers - DriverTuner ?

you can download Driver Tuner, and check for any missing drivers, hope i helped.

 

[joehimself]

@skits559
I saw bad reviews on Driver Tuner plus it costs money. I appreciate the nice people here that are trying to help me. Thanks for the tip, though.
http://www.sevenforums.com/members/skits559.html

 

[joehimself]

I deleted C:\Windows\inf\setupapi.dev, changed LogLevel to 0, then restarted W7.
No luck yet.

My sister-in-law got scammed by Driver Tuner 2 years ago. blah blah blah. Sorry if I sounded like jerk regarding them but I didn't want to go into all that. skitts599, I apologize to you. I'm sure you don't work for the company or have anything to do with them. Thank you for trying to help me.

 

[ComputerGeek]

LogLevel = 2000ff00
Should I change this to "0"?

That's interesting.....

The default value is "0".

LogLevel can be set to other values to change the verbosity of the trace level. Yours is set to the most verbose trace level possible. Curious: Was someone debugging device issues for you in the near past? It appears a copy of the log was created Dec 12, 2013?

Don't know if current verbosity might overwhelm me, but let's give it a shot as is (we'll forget about any timing for now)

fyi.. Personally i HATE that Vista and higher hides file extensions by default. I think it makes it easier to miss and/or confuse things. CtlPanl->Folder Options->View tab. Uncheck option to Hide extenstions for known file types. Click OK

> Get ready to repeat the problem sequence
> Delete Windows\inf\setupapi.dev.log
> Go through the steps to recreate the error (windows will create a new setupapi.dev.log file)

Zip up the setupapi.dev.log file and tell me the sequence of things/messages you saw on the screen. I'll try to correlate to the sequence of events in the log file