TechSpot - PC Technology News and Analysis

LookinAround · #81 12-31-2008

Well, first of all HAPPY NEW YEAR. and hope you get sound again soon in 2009!

As to post #78. .sorry if not clear.. tried describing how to verify that tool was being found but is now a non-issue as it's clearly found and reporting data per the file you sent.

Have fun this evening.. Hopefully my first post in 2009 will be instructions to try fix this nagging bug!

TridentCrash · #82 12-31-2008

Alright Thanks! Happy new years to you too

This is number one on my new years resolutions! lol

LookinAround · #83 01-02-2009

Quote:

Originally Posted by TridentCrash

Alright Thanks! Happy new years to you too

This is number one on my new years resolutions! lol

Recovered from New Year's yet??

just fyi.. if not still tonight, will have something posted tomorrow

LookinAround · #84 01-03-2009

Goal is to fix problem where Windows can’t load drivers from WDM library

Once it's fixed:
==> msinfo32 shouldn’t report any driver in wdm library as a problem On your computer, msinfo32 has been reporting Microsoft System Audio Device. (Below is list of I think all drivers in wdm library).
==>Your sound may start working once this is fixed but maybe not if fixing the one problem reveals something else lurking (tackle that if need be. Will tell you an “fyi” later of something else i noticed in the data dump you last provided.)

Drivers in wdm library
Code:
Microsoft Kernel Acoustic Echo Canceller
Microsoft Kernel Audio Splitter
Microsoft Kernel DLS Synthesizer
Microsoft Kernel DRM Audio Descrambler
Microsoft Kernel GS Wavetable Synthesizer
Microsoft Kernel System Audio Device
Microsoft Kernel Wave Audio Mixer
Microsoft Streaming Clock Proxy
Microsoft Streaming Quality Manager Proxy
Microsoft Streaming Service Proxy
Microsoft Streaming Tee/Sink-to-Sink Converter
Microsoft WINMM WDM Audio Compatibility Driver

Device Manager Setup

Normally, Device Manager doesn't display “ghost" devices"
=> We change it so your Device Manager shows ghosts when you click View->hidden devices (Can change back when we’re done)
Fyi: Now that you can see “ghosts” note it's not good to delete ghosts just because they’re there (there are good ghosts! Deleting the wrong ghost can cause you grief later)

Setting Device Manager to Display Ghosts
- Close Device Manager if open
- Rt click My Computer->Properties->Advanced tab, click Environment Variables
- See System Variables in LOWER part of window
- Click New for System Variables. In the new window, enter (exact spelling. copy/paste variable name is best)
===> Variable name: devmgr_show_nonpresent_devices
===> Variable value: 1
===> Click OK close all System Properties windows

Verify you can see ghosts
<< For testing now you should use Device Manager’s default View Devices by Type (NOT Devices by Connection) so you can scroll to sound devices and see all sound devices together
Except, with this view, the Microsoft UAA Bus Driver will now be found under System Devices
- Open Device Manager, click View->Show hidden devices, scroll to Sound devices
- You should see several devices with semi-transparent icons. These are ghosts.
- If you don’t see any ghosts, you probably typo’ed the System variable name above

And finally
>> NOTE!!
a) Key to these steps: We do not want Windows to reinstall anything until AFTER you’re all done (Keep an eye none of those device pop-up balloons)
b) While you are uninstalling Windows might tell you it needs to reboot. But it prompts first. ALWAYS SAY NO. Do the reboot yourself when done >>

Delete file C:\Windows\setupapi.log
Open Device Manager. Click View->Show Hidden and scroll to sound devices
Review the uninstall list below so you’re first familiar which devices to uninstall (i.e. what appears on your computer vs. in the list below) Remember MS System Audio uninstalled last (not critical it's last but Windows does ask reboot after this one)
Also see 2nd list below for sound devices that might appear you should leave alone
Uninstall list
- Leave the Microsoft UAA Bus driver as is
- Uninstall these (whichever appear)
  ===> Audio Device on High Definition Audio Bus
  ===> Modem Device on High Definition Audio Bus
  ===> Conexant HDA D110 MDC V.92 Modem
  ===> Conexant HDA D110 MDC V.92 Modem #2
- Except for Microsoft Kernel System Audio Device uninstall every wdm library driver you see. list repeated below
- Finally, Uninstall Microsoft Kernel System Audio Device
- Reboot
- After re-boot run msinfo32. (no more complaints i hope?)
- Then run the Dell sound card install
- If still any problems send me C:\Windows\setupapi.log along with msinfo32 report

Code:

Microsoft Kernel Acoustic Echo Canceller
Microsoft Kernel Audio Splitter
Microsoft Kernel DLS Synthesizer
Microsoft Kernel DRM Audio Descrambler
Microsoft Kernel GS Wavetable Synthesizer
Not till last => Microsoft Kernel System Audio Device
Microsoft Kernel Wave Audio Mixer
Microsoft Streaming Clock Proxy
Microsoft Streaming Quality Manager Proxy
Microsoft Streaming Service Proxy
Microsoft Streaming Tee/Sink-to-Sink Converter
Microsoft WINMM WDM Audio Compatibility Driver

List of Sound devices if you see just ignore

Code:

BDA IPSink
BDA Slip De-Framer
Closed Caption Decoder
Logitech Mic (IM/Connect)
NABTS/FEC VBI Codec
World Standard Teletext Code

Benchmark · #85 01-04-2009

Earlier today I had the pleasure of listening to sereen music through a pair of sony ex71 bud earphones via the audio jack on a Dell 1100 laptop with SigmaTel sound card to only get pins and needles in my left foot, stomping and getting a static electric shock through the left earphone for the music to turn into scratchy and robotic high / mids and completely distorted lows.

I have tried reinstalling all software to no avail, so wondered if anyone has any ideas on rectifying before I shoot off and get a new cheap external sound card (any recommendations here also?)

Your views would be appreciated!

LookinAround · #86 01-05-2009

Hi Benchmark

In general, you should post a new problem/question in your own new thread

But aside from "in general" reasons i think will also attract more people to look at a new thread (and increase your odds for good answers!)

You can click here for more general stuff/info

And welcome to TechSpot!

Benchmark · #87 01-06-2009

Hi LookinAround

Sorry about that. I am new to this and will do.

And thank you for the welcome!

TridentCrash · #88 01-09-2009

Quote:

Originally Posted by LookinAround

[*]After re-boot run msinfo32. (no more complaints i hope?)[*]Then run the Dell sound card install

By this do you mean the chip set or SigmaTel Audio card driver?

I did the SigmaTel Audio driver.

As for msinfo 32 its showing everything that i had uninstalled from your previous instructions is not working improperly

Microsoft Kernel Acoustic Echo Canceller SW\{4245FF73-1DB4-11D2-86E4-98AE20524153}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
Microsoft Kernel Audio Splitter SW\{2F412AB5-ED3A-4590-AB24-B0CE2AA77D3C}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
Microsoft Kernel DLS Synthesizer SW\{8C07DD50-7A8D-11D2-8F8C-00C04FBF8FEF}\DMUSIC 39
Microsoft Kernel DRM Audio Descrambler SW\{EEC12DB6-AD9C-4168-8658-B03DAEF417FE}\{ABD61E00-9350-47E2-A632-4438B90C6641} 39
Microsoft Kernel GS Wavetable Synthesizer SW\{6C1B9F60-C0A9-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
Microsoft Kernel System Audio Device SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
Microsoft Kernel Wave Audio Mixer SW\{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
Microsoft Streaming Clock Proxy SW\{97EBAACC-95BD-11D0-A3EA-00A0C9223196}\{53172480-4791-11D0-A5D6-28DB04C10000} 39
Microsoft Streaming Quality Manager Proxy SW\{DDF4358E-BB2C-11D0-A42F-00A0C9223196}\{97EBAACB-95BD-11D0-A3EA-00A0C9223196} 39
Microsoft Streaming Service Proxy SW\{96E080C7-143C-11D1-B40F-00A0C9223196}\{3C0D501A-140B-11D1-B40F-00A0C9223196} 39
Microsoft WINMM WDM Audio Compatibility Driver SW\{CD171DE3-69E5-11D2-B56D-0000F8754380}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
SigmaTel High Definition Audio CODEC HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801F5&REV_1022\4&35873B3A&3&010 1 39

LookinAround · #89 01-10-2009

ARGHHH!!!

I sooo expected different results!

(In earlier instructions i meant for you to re-run Dell's Sigmatel audio driver file. Sounds like you did)

For now,
=> Make a backup copy of file C:\Windows\setupapi.log and delete the original file
=> Copy code below into a .txt file. Save and then rename the file extension to .reg
=> Double click the file and allow it to update your registry

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"LogLevel"=dword:0800FF00

=> From Device Manager,
====> uninstall the sound card, uninstall the microsoft UAA bus controller
====> click Action->Scan for Hardware Change (easier then reboot) for windows to start re-install attempt
If problems after Windows re-install done also re-run Dell's sigmatel audio driver again

Finally, if still problems,
=> Re-run the script i sent you earlier that captured all that devcon data to a file it puts on your desktop
=> Send me: Copy of the current C:\Windows\setupapi.log (probably need be zipped or change its extension to .txt so can attach it to TechSpot)
=> Send me: the desktop file that script creates for you

Unless something jumps out at me, will probably proceed with the SP3 upgrade next. Will see..

TridentCrash · #90 01-11-2009

umm... I dont think i know how to make a copy of C:\Windows\setupapi.log??
so before i go on and mess anything up (I hope i dont) im gonna wait till i get further instructions before i do any of the requested things in your previous post

kimsland · #91 01-11-2009

To backup setupapi.log

Start->Run-> C:\Windows\setupapi.log

When Notepad opens up with setupapi.log; just click on File -> Save As

Then just give it another Filename, like setupapi.BAK

And press Save

TridentCrash · #92 01-11-2009

Thanks so very much Kimsland

and that did not seen to work LookinAround so here are the files you asked for.
The setup file was to large so i compressed it

kimsland · #93 01-11-2009

Quote:

Originally Posted by LookinAround

=> Make a backup copy of file C:\Windows\setupapi.log and delete the original file

Just wondering did you first delete the original setupapi.log as requested?

TridentCrash · #94 01-11-2009

umm... I dont think so?

kimsland · #95 01-11-2009

I see

Start->Run-> C:\Windows

Search for setupapi.log

Right click on it and delete it

Continue the above steps from there

TridentCrash · #96 01-11-2009

oh. Thanks Kimsland

LookinAround · #97 01-11-2009

THanks for the data (and thanks to Kimsland in the assist in getting the data).

I haven't looked through it yet, but want to point out something i noticed and just alluded to sometime before Among all that device data created by the script you run for me, reveals a filter driver is being applied to your sound card: LVUSBSta.sys. I found this is a Logitech filter.

When you installed your Logitech web cam drivers Logitech included their filter driver Don't know if this subtlety may be part of the larger problem we see . but at minimum...is an fyi you should be aware of. I have seen several run-time problems it can cause (we're still at loading problems) A couple references . See here and see here.

For now, this is just fyi... will follow up after looking at data tho fyi about filter drivers

Well known fact: a device has a device driver

Request sent to driver.........................Rqst
............................................................↓‏
Driver communicates with device........Driver <==> Device
............................................................↓‏
Driver sends back a response ..........Response
..(might include device data )

Lessor known fact: "Filters drivers" (simply called "filters") can also apply to a device in addition to its device driver

Request sent to driver..............................................Request
........................................................................... .......↓‏
One or more upper filters exist..................................Upper Filters
..Orig rqst may be modified by filters!............................↓
........................................................................... ......↓‏
Driver communicates with device…............................Driver <==> Device
..and sends back a response.......................................↓
........................................................................... .....↓‏
One or more lower filters exist.................................Lower Filters
..Driver response may be modified by filters!.................↓
........................................................................... .....↓‏
The return response finally makes it back .................Response

Is how a faulty filter driver (installed by a 3rd party) can interfere (without your realizing) and make it appear like it's the device not working

TridentCrash · #98 01-11-2009

While one the note of my web cam; like in the first link you stated, I also am havin problems with it. it acting funny and me unable to uninstall it!!! its very frustrating

LookinAround · #99 01-11-2009

most interesting..... will also look at that as well.. wouldn't it be interesting to see if, in fact, the two different devices and their problems are related due to Logitech's filter driver! (At the moment, is just wishful thinking. but will see....)

LookinAround · #**100** 01-13-2009

I’ve taken a look through the setupapi.log file

Not part of your problem but just happened to note, could see the timestamps and it took ya a good 10 mins to do all those uninstalls I requested! Thanks. At least the good news there, should we need do something similar again I think I can do all the device uninstalls from a single batch file. Make the task much simpler

(in addition to knowing of your fond memories of batch files from school!)

As for the log data itself, I need to tweak the log setting that controls which data is written. So, will have you create two .reg files
=> startlog.reg starts logging more verbose and detailed data. The detail may generate lots of disk writes when you’re testing and slow your machine down a bit. So you’ll want to use
=> stoplog.reg to stop all that detailed log data when you're done with any testing so you can use your machine normally without being slowed down by all the logging.

I’ll be sure to indicate when to Start/Stop Logging if it’s needed for a test.

So let’s create those .reg files and then try using them for a test
Start->Run, enter notepad startlog.reg
When notepad opens copy/past the code below into it

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"LogLevel"=dword:08006060

Then save startlog.reg to your Desktop (or wherever convenient for you)

Repeat for notepad stoplog.reg

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"LogLevel"=dword:00000000

Now let’s try it out
1. Delete C:\Windows\setupapi.log
2. Double click startlog.reg
3. Open device manager.
4. ====> Rt click your Sigamtel sound card and UNINSTALL it, next
5. ====> Rt click the Microsoft UAA Hi Def Bus Controller and UNINSTALL it
6. Now, run that Dell download file which extracts the sigmatel driver files and then tries to do the sigmatel driver install
7. Once it looks like any install activity has settled, why don't you try uninstalling any one or two of those WDM audio drivers you want then click (in Device Manager) Action->Scan for Hardware Changes to see if any reinstalls get started
8. Wait a few minutes (if other re-install attempts to complete and things settle down)
9. Double click stoplog.reg
10. Attach the C:\Windows\setupapi.log file to a post

Also, please generate detailed info about your current Windows system services and drivers by
=> Download and install Serviwin. (For info on the tool click here)
=> Start->Run, enter cmd
=> Copy/paste each line after the prompt

Code:

"C:\Program Files\Serviwin\serviwin.exe" /stab services "%USERPROFILE%\desktop\Services.txt"

"C:\Program Files\Serviwin\serviwin.exe" /stab drivers "%USERPROFILE%\desktop\Drivers.txt"

And provide me those .txt files which will appear on your Windows Desktop as well (you can zip them all into one, or attach the 3 files separately. whichever you find easier)

Similar Topics
Topic	Category	Replies	Last Post
Help on IDT or SIgmaTel Audio	Audio and Video	0	12-04-2008 11:42 AM
Major Audio Problems	Audio and Video	1	11-28-2008 01:42 PM
Audio Driver problems (major annoyance)	Audio and Video	23	03-13-2008 09:58 PM

TechSpot - PC Technology News and Analysis

Solved: Major problems with Sigmatel audio card