Hmm. Will this be the end of this long thread or not?

I hope this will be the end!

Just a quick post for now (will follow-up later with add'l info for you or others reading that might find helpful understanding/debugging similar problems)

But first and foremost:
CONGRATULATIONS!!! CONGRATULATIONS!!! CONGRATULATIONS!!! CONGRATULATIONS!!!

After all the effort in this thread (not to mention your own effort even before starting the thread) it's awfully suspicious that your sound FINALLY starts working again after we first
- Remove the Logitech media class filter and then you
- Reinstall your sound card!!

In any case, would advise

1. Create a restore point
2. Install and run DriverMax to backup all your current drivers
3. I don't know if you run backup software that allows you to backup and image your hard drive. But if you don't, i think now is an excellent time to invest in buying it!!! (I personally prefer/use Acronis True Image). This should at least guarantee that whatever happens (and should the logitech filter be the problem source and possibly interfere again from this point forward) you can always have the option to restore to this moment in time on your hard drive!

I had already started to prepare a reply for you before getting your latest good news (which am still happy to hear! ) Most of the reply still applies (except I changed NEXT STEPs to reflect where things are now) So let me know what you want to do (if anything) about NEXT STEPS below

=> For you (or anyone reading): Read Explanation below for summary of info and reasoning behind what-would-be-next had the problem not been fixed
=> Or you can just skip to Next Steps below to decide what to do now (that problem appears fixed)

Explanation

• Windows audio drivers (that are part of Windows) will not run
  • I interpret as a continued sign of an underlying and fundamental problem with your system
  • It might be due to your Sigmatel driver but..
  • It might be a sign of something completely different and another problem – having little or nothing to do with Sigmatel
• Your drivers appear to install but not start
  • As I interpret all those setupapi trace logfiles you sent me: Your drivers are actually installing OK. (Specifically, Microsoft Hi Def UAA, the WDM drivers (- these are the Windows audio drivers) and your Sigmatel driver)
• HOWEVER, driver installation is a separate step from getting them to actaully start and run
  When it comes time for Windows to actually START the drivers running
  • Microsoft Hi Def UAA starts and runs OK
  • But Sigmatel and WDM drivers fail to start They report device manager error code 39
• Follow-up steps are to start uninstalling media drivers and then reboot after each one to check WDM drivers
  • They need be uninstalled via Add/Remove Programs first if you find them there. If removed via Add/Remove Programs the device shouldn't get reinstalled on reboot
  • Uninstall via Device Manager if need be. However, if they reappear on reboot after uninstall via Device Manager it means we need find the driver Setup Installation file (.inf extension) usually will be in C:\Windows\system32\inf that's allowing the reinstall to still happen. Once found, simply the rename it to a different extension (i.e. NOT .inf)
  • Uninstall the sound card first, then Microsoft UAA driver and other media drivers as needed until the Microsoft kernel WDM drivers don’t display an error immediately after reboot

Now that sound's fixed Next Steps

1. Do you still want to address the ATI issue? If yes, probably best to start a new thread
2. What about the Logitech driver? Recommend at least look at the state of Logitech driver
   • If the Logitech driver device status is “Working”
     => Is possible Logitech will reinstall the media filter
     => But it's also possible the LVUSBSta filter may only be a problem when the filter exists before the Sound card is working (I don’t know)
     => Though in, worst case, you now know how to remove the filter again if need be!!
3. Btw.. it was my old “DevQuery” script lead me to discover that Logitech filter in the first place.
   • It would be good if I could take another look at all your media devices (which will include your Logitech cam stuff). I attached a version I think is all debugged If you save the attached file as a .bat file and run it (will take up to 30 seconds or so), then attach the .txt file it leaves on your desktop

Attached Files

DevQueryMedia.txt (2.6 KB, 4 views)

As far as the ATI problems, gone. So basically as far as im concerned my comp is back to the way it was to begin with (lol its a dell, you cant expect perfection!) And as the script output from that batch file what kind of file is supposed to saved to my desktop? Cause the file have now is not compatible with techspot

Glad to hear ATI problem is gone!!

And for the script output:
1) you did download the NEW script in my last post (then renamed it .bat extension?)
2) The name of the output file on your desktop is DevMediaData.txt which should be compatible with TechSpot as it's a .txt file

Oh there it is.... i didnt look for it good enough i guess... lol

Attached Files

DevMediaData.txt (53.0 KB, 6 views)

ALMOST...

The output file is the correct one BUT your logitech cam stuff should be connected and turned on in order for me to see its driver status/data info so we can finally put all of this issue to rest.


Sooo.... if you are going to throw away, NEVER connect and never turn on and try to use your logitech cam stuff again, we can say we're done now.

However, if there's that chances you may want to try using that webcam again sometime future....etc. etc. etc. Please connect the equipment, turn it on, and then run the batch file again. It will overwrite the old file on your desktop as it creates a new one. If you could post it please.

Nah im done with it.... i only used it once and if i do wanna use it again im just gonna go buy a newer cam (better mega pixels)

We did it! Your Sigmatel sound card is fixed! As well as your modem (if you happened to know you also had a modem) !

If you could do one last thing? Update the Thread Title to read SOLVED: Major problems with Sigmatel audio card

Strong evidence the problem was due to the Logitech media class filter!!!
=> We may have found another reason why sooo many people on the Internet can't get their sound cards to work!
=> They should check for media class filters and/or sound device filters!. I'll be adding a post for anyone reading on how to check / fix filter problems with audio devices

BEFORE: When the Logitech media class filter LVUSBSta.sys existed, every attempt over many months ended with

• SigmaTel High Definition Audio CODEC Device has a problem: 39.
  • Device HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801F5&REV_1022
• Modem Device on High Definition Audio Bus Device has a problem: 01.
  • Device HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900

AFTER: the Logitech media class filter was removed and the sound card driver re-installed

• SigmaTel High Definition Audio CODEC Driver is running.
  • Device HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801F5&REV_1022
• Conexant HDA D110 MDC V.92 Modem #3 Driver is running.
  • Device HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900

Here's an easy method to check if filters are being applied to your sound card

Do the following:

• Start->Run, enter: devmgmt.msc to open Device Manager
• Look under Sound, video, graphics for your sound card
• Rt click your sound card, select Properties, click the Details tab
• Use the pulldown menu to select and check each of the following:
  => Device upper filters
  => Device lower filters
  => Class upper filters
  => Class lower filters

If you don't see anything displayed for any of the four filters above, it means NO filters are being applied to your sound card. If you did see filter(s) displayed:

Device filters are specific to a device. So, if you see a device filter (upper or lower) it was very most likely installed as part of your sound card driver's install and isn't causing the sound card problem

Class filters, however, may have been installed by a different vendor then the sound card's manufacturer (as was the ultimate discovery and problem source in this thread!)
=> Be cautious of non-Microsoft class filters (upper or lower) applied to your sound card
=> "Cautious" simply means it might be causing problems if you're having sound card issues

To learn more about a specific filter (including the vendor who provided it) install Serviwin
=> If you saw a filter displayed, information about it should appear when you run Serviwin and click View->Drivers