Solved: Major problems with Sigmatel audio card

By TridentCrash · 130 replies
Dec 8, 2008
  1. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    Now that's pretty disturbing to know! seeing as how the installation was a miserable failure! But not going to spend time on it other then note (for anyone reading) that the Dell install package you ran was built with InstallShield version 10.1 (which as an older version. Don't know if that's still typical for "quiet" installs or a bug fixed in later versions. Quiet installs are install packages designd to run without requiring any user input other then Next and Finish type clicks) BUT that install you did was a little too quiet! :haha:

    Which makes me wonder.. How do you normally get / apply your Windows updates? Do you have it set to automatic or do you run it manually?

    Go to Microsoft Update, click Custom. Only apply the high priority updates AND make sure that XP SP3 is not included among them (if it is you can uncheck it so as to not install it yet).
  2. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    Yea i do that once a week and there seems to be nothing new at this point in time.
  3. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    OK. What's next is to try a manual install of the XP MS Hi Def Audio driver in your XP SP2 system (instead of using the dumb dell installer to do the first driver which is MS anyway) then we'll retry the installer for the sound card

    But first i'd like to be prepared with a couple things we might need later (it can be a pain to fix Windows stuff, huh? :D )

    Let;s get a snapshot in time of your current system setup and MS updates for reference
    ==> Download/install Belarc Advisor
    ==> Run it to create a report displayed in your browser.
    ==> If in browser, you click File->Print can you select a printer that's really a driver allowing you to save the browser display to a nicely formatted disk file you can later re-display??? If yes, please verify you can save it and re-display it.
    ==> If you need printer driver to allow this, try this freeware i found. install PDF Createor. . Then you should be able to see it as printer you can select and it will to file in .pdf format. And prove you can redisplay after saving

    Understanding the Device Manager icons
    These indicate a problem with the device
    ==> Black exclamation point (!) on yellow is a device error. These can occur even if the device appears to working (there’s still something wrong with it). Some help in troubleshooting XP error codes here
    ==> Yellow question mark. Windows can’t find the device driver. This icon often appears under Other Devices but look through all of Device Manager as can appear elsewhere (in particular, under USB)

    These may or may not indicate a problem with the device
    ==> Red "X". Device is disabled. (fyi.. Disabled devices still use resources)
    ==> Blue "i" on white.[/i] Resource usage for the device has been manually configured. (Windows isn’t controlling it for this device) Note: Forcing resource usage for any one device may affect other devices

    Compare problem devices you find in Device Manager vs. summarized by msinfo32
    msinfo32 should easily summarize Device Manager device problems for you. Just want to double check they’re currently matching like they're supposed to as will be easier for you to tell me details about problem devices by simply using msinfo32 and copy/pasting
    ==> Start->Run, enter: msinfo32
    ==> Expand Components (click + sign next to it)
    ==> Click Problem Devices. Anything appear? Do things match. When needed, you can just copy/paste from here to let me know what's showing up along with the detail msinfo32 provides

    Now if you could go through dev mgr to see problem and devices. Does that match the list given by msinfo32. (want to do a spot check as we;ll rely on that)​
  4. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    In a previous post i mentioned that there was 4 "problem devices" in my device manager but now there are 5
    -Audio Device on High Def Audio Bus
    -Base System Device
    -Ethernet Controller
    -Modem Device on High Def Audio Bus
    -SM Bus Controller

    in msinfo32 under Problem devices there are 5 problems. one of which is my printer because i have JUST installed it and have not rebooted yet.
    -Base System Device
    -Ethernet Controller
    -My printer (Just need a reboot)
    -Microsoft Kernel System Audio Device
    -SM Bus Controller

    And also i can not get it to save a "useable" copy of the report from Balarc?
  5. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    Well, please click on the info displayed in msinfo32 about the devices. Then simply copy/paste the info it displays. All that extra info (above and beyoned the device name is what i want to see. And is why will be easier for you to simply use/copy/paste all that by running msinfo32 when needed ;) )

    Did you try installing the PDF create tool? as it should have added a printer type you can select among your list of printers to print the file in PDF format (i assume you already have Adobe Reader installed to read them back? if not search Adobe Reader to find and download it)
  6. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    I went ahead and wrote further instructions so whenever you have the chance you’ll have the next few steps

    Let’s see.. in the last episode of our continuing saga….You were trying to save a copy of Belarc Advisor report as you couldn’t print to a file
    1. Apologies. I don’t know what I was thinking (was a long day!) when I decided you had to Save the report as .pdf (which meant extra steps). All you need to do save the Belarc report
    ==> In the report’s window: click File->Save Page As. Set the Save as type to Web Page, HTML only. Then save the file.
    ==> To attach the file to your next post. You’ll have to rename the file to change the file extension from .html to .txt and then attach it to next TS post

    2. Run msinfo32 again and copy its info on problem devices and paste into next post

    3. And an fyi about MS updates: After last post when you said you already run them:
    ==> Do you normally click Express or Custom when you run MS update? (I’m guessing you click Express).
    ==> Run MS update again and click Custom. Only when you run custom will you see optional Hardware and Software updates. Please review them all. Usually is good to install any hardware updates. Install what you want (only need tell me any specifics if any look like they apply to your sound problem or you have any question on anything you see)

    4. Re-install Dell chipset drivers. Click here to download. Save the file to disk and double click to run the install. Run msinfo32 again after the install. Any difference? Please post another list of problem devices as reported by msinfo32 after you've run the chipset install

    5. Try installing Hi Def Audio Bus Controller driver manually. We'll make two attempts (if they both should fail we will likely jump right to XP SP3 but want to see the attempt results first). I’ll be editing this post to add instructions for the two driver install attempts.Watch this space! (but probably not till tomorrow)

    /** EDIT 1 **/
    You are also missing a different driver. You must not use any IEEE 1394 /Firewire devices i guess and if you do i'll guess they're not working! In any case, best to get everything loaded/fixed while in the process of cleaning up your machine. Click here for the driver. After the install, check msinfo32 for problem devices again. That take care of Base System Device?

    Also: i also guess you only use your wireless connection to that computer as appears you're also missing driver to support wired connections. Has it always been this way?? (just curious) Will give you this driver in a later post
  7. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    OK, sorry took 2day for reply. Dad borrowed comp for work and left there =(

    here is what I got from msinfo32 the first run though befor the install of the chipset driver
    Base System Device PCI\VEN_1180&DEV_0843&SUBSYS_01F51028&REV_01\4&B216F0A&0&09A4 This device is not configured correctly.
    Ethernet Controller PCI\VEN_14E4&DEV_170C&SUBSYS_01F51028&REV_02\4&B216F0A&0&00A4 This device is not configured correctly.
    Microsoft Kernel System Audio Device SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4} 39
    SM Bus Controller PCI\VEN_1002&DEV_4385&SUBSYS_01F51028&REV_14\3&2411E6FE&0&A0 This device is not configured correctly.

    and here is after the install of the chipset driver
    Base System Device PCI\VEN_1180&DEV_0843&SUBSYS_01F51028&REV_01\4&B216F0A&0&09A4 This device is not configured correctly.
    Ethernet Controller PCI\VEN_14E4&DEV_170C&SUBSYS_01F51028&REV_02\4&B216F0A&0&00A4 This device is not configured correctly.
    Microsoft Kernel System Audio Device SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4} 39

    also attached is the balarc report. I hope that that works for you
    also for the MS Updates I ALWAYS click custom
  8. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    First, no apologies needed. Certainly there's other stuff that needs to (and should!) take a higher priortity. Be sure to tend to those things first.

    Some info
    The last chipset install was good! The ATI chipset driver reinstalled. The msinfo32 report in your last post no longer includes SM Bus Controller as a problem device.

    1. We try fixing: Base System Device. Click here for the Dell Driver. Please download/save to disk / Install
    2. When install finished run msinfo32 again. Tell me if Base System Device is gone or still there. If still there, paste that new msinfo32 list into next post. Whether gone or not continue with next step
    3. For the Ethernet Controller. Click here for the driver. Download/save/install. Check msinfo32. Ethernet Controller gone from the msinfo32 list?
    4. Click here to download/install a diagnostics thatfor that Ethernet controller should you ever need it (Probably best to get it all installed now should ever need it later)
    5. Now (if above went well) the only problem device(s) left are Audio related. But i'm not sure why the last msinfo32 report per your last post lists Microsoft Kernel System Audio Device which is NOT the Audio Bus Controller. (Audio Bus Controller may appear in Device Manager as Microsoft UAA Bus Driver for High Definition Audio).

    So i'd like you look in Device Manager to see if you find the Audio Bus Controller (aka that UAA Bus Driver....) listed and it's Device Status
    ==> In Device Manager, click View->Devices by Connection
    ==> Expand ACPI computer and expand a few levels down till you see PCI bus
    ==> Expand PCI bus to see the list of controllers
    ==> Are you seeing the Microsoft Audio Bus controller(or other name i gave for it) listed or no?
    ==> Rt click to select device and Properties. What is its Device Status?

    I have to look into Microsoft Kernel System Audio Device. And tell me how the above all goes when you have the time to do it
  9. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    OK thanks so much so far!
    Only thing left in problem devices in msinfo32 ins MS Kernel

    Not quite sure Im understanding what your asking for under Device Manager but this is what I see
    Under PCI Bus I see MS UAA Bus Driver for High Definition Audio and under that there is Audio Device on High Definition Audio Bus & Modem Device on High Definition Audio Bus

    Audio and Modem both have a big yellow question mark with a smaller black (!) over them
    Audio-This device is not configured correctly (code1)
    Modem-This device is not configured correctly (code 1)

    Again Im not sure if this is what your asking for but i hope this helps
  10. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    No worries about giving me the right info as you’ve been doing everything great!

    Your last post mentions seeing MS UAA Bus Driver for High Definition Audio (fyi this is the Audio Bus controller device for your machine). To double check a few things
    => Does this item have a yellow icon too? Or no?
    => Rt click this device, select Properties. What is device status? Info for the following may only appear when Status= Working
    => Click Driver tab. What is listed as Driver Version?
    => Then click Driver Details button. You get a window with one or more files listed. Please capture a screen shot of this Driver Details windows and attach

    Then for Audio Device on High Definition Audio Bus ( i think you also indicated one has the word Modem. You don't need do anything with that one)
    => Rt click for its device properties too
    => Then click Details tab. The pull down menu likely defaults to and already showing Device Instance Id (else select Device Instance Id) and do a screen capture and attach it to next post (and should you not see Device Instance Id i'm forgetting if XP SP2 needs the Windows "magic words" or not to see it. so just let me know)

    /** EDIT **/
    Also please tell me do you have XP installation CDs?
  11. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    First off, site is not allowing me to upload the screen shots

    MS UAA Bus Driver - Status= Working
    Details PCI\VEN_1002&DEV_4383&SUBSYS_01F51028&REV_00\3&2411E6FE&0&A2 (not sure if this is what your asking for)

    Audio Device - Status = Device is not configured correctly (code 1)
    Details HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801F5&REV_1022\4&35873B3A&3&0101 (again, not sure if this is what you wanted)

    Hope this helps
  12. kimsland

    kimsland Ex-TechSpotter Posts: 14,523

    Using the insert picture button -> [​IMG] you should be able to add pictures
    Unless the picture is just toooo big
    Try opening your picture with your picture viewing program and save it as GIF format
    Then upload it, then use the insert pic button to link to the picture url
  13. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    [​IMG] MS UAA Details
    [​IMG] Audio Device details
    thanks. Never occured to me to upload them to a third party site
  14. kimsland

    kimsland Ex-TechSpotter Posts: 14,523

    Well I've edited your pics above
    Here's what I did:
    1. Used your link to the actual picture, to actually then find the direct JPG links
    2. Saved your pics to a temporary location on my computer
    3. Resized both pics (ie they were - and still are, very big)
    4. Uploaded both the reduced sized pics, and saved their direct JPG links
    5. Used this button -> [​IMG] to insert the JPG pic thumbnail link normally
    6. Used this button -> [​IMG] after highlighting the entire IMG linked part, then adding your original JPG links (that I found earlier, in step1)
    7. Did the same for the other pic

    This entire process took me about 1 minute (if that) But will come with practice if you do want to do more yourself. Your original issue was not linking directly to the JPG specific link.

    Now at last what to do, about your actual issue you are having!
    Due to the size of this thread, it may have been lost somewhere in all the words
    But are you running Service Pack 2 or Service Pack 3 ?
    I have the strangest feeling, that you are going to say SP1 :confused:
  15. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    kimsland: thanks again for the assistance
    To both of you: that info was perfect! It nailed down some confusion i had

    And I don't want to be pre-mature or stir false hope... but i think we're close. Very close!
    Just couldn't wait to say it. Am hoping to be proven right soon (but there's still that chance otherwise)

    My followup post will be later today or maybe tomorrow. Will explain all in next post (along with next steps)
  16. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    HA! SP1!?! No im actully running SP2. Have not heard anything about SP3 (good or bad) so i havnt upgraded yet
    And also thanks for the uploading tips :grinthumb
  17. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    OK. Banged this out quickly so can post what's going on. (not alot of proof reading so bear with it please)

    Will followup with what next (which i hope proves what otherwise seems to fit the problem history so well)

    So here’s the history and problem.. to fill in the blank. Of course still needs to be tested!

    Something wasn’t making sense to me. When I read post #59 couple days ago it heightened a suspicion you later confirmed for me: I had an underlying fact wrong causing my approach to be a bit off path which i noticed when veered too much!

    1. Started troubleshooting by first asking to uninstall the 2 devices (pretty standard 1st step)
    - Audio Bus controller (named MS UAA Bus Driver for High Definition Audio) and
    - Sigmatel sound card

    2. You reported both devices kept re-appearing. I said no problem and explained
    a. Windows periodically scans to check for hardware change to its current config
    - Device detection doesn’t depend on drivers. No matter if device drivers are good or not
    . - The 2 uninstalled devices re-appear when hardware scanned and they’re detected
    b. Upon device detection, Windows then looks for a device driver. But we just uninstalled driver.. So is to be expected for Windows to report the device (because it's still detected) and say it's not working (cause it can't find the driver)

    3. The events just described are pretty common in Windows. So to be expected after uninstalling the drivers, right? Well,….. that depends!

    4. Windows needs something called the “driver install file” to provide it instructions on how and what files should be installed.

    5. Sigmatel sound card. When a vendor provides a driver (e.g. via Dell driver downloads or via the CD that came with new hardware) the vendor file is commonly called “the driver” but technically its really “the driver install package” as the vendor packages many needed things into the file:
    - the driver install file (install instructions for what’s to follow)
    - the driver files (the set of files to be installed all of which together make the driver)
    - Other (such as Control Panel applet to allow user to control/configure the driver)
    When new hardware is detected and you’re prompted for location of the driver, you’re really just pointing windows to the location of the install file which tell it the rest it need know.
    When new hardware is detected and Windows tries to automatically install the driver, it fails as it doesn’t know where to go find the install file

    So is normal and expected when we: uninstall Sigmatel sound card then see Windows detect it but the driver installation fails so the sound card device is reported as Not Working.

    6. Audio Bus Controller. So after uninstalling the Bus Controller we’d expect the same? And then also expect Windows say it's Not Working, right? NO! I had forgot something and that was my error.
    It’s a different case when Windows provides the default driver for a device (and recall that MS updates were released that are applied to XP SP1 and XP SP2 to add this driver to the Windows system library). ​
    So when this device is re-detected Windows knows where to find the install file as it keeps its own copy of it tucked away along with other things needed to complete driver installation.

    But I had been proceeding under the assumption that BOTH drivers weren’t working
    => Which I later realized and had you double check and sure enough the Audio Bus is working and the sound card is not working which are, in fact, what I should have expected!!
    ==> And in all fairness, I probably bashed the InstallShield when I thought what it was doing vs. result was out of whack! (I take back what I said about it, for now, but not gonna retest)

    So what the heck is the problem??? This is the real irony AND I’m going out a limb as I’ve written all this explanation as I think it now fits like a glove to my corrected theory but of course none of it’s proven yet

    I don’t think ANYTHING was wrong with the old drivers. Altho problems is those drivers is the almost obvious and natural guess for anyone to have. Uninstalling those drivers was standard 1st step but what follwed became, in part, a red herring tho did lead to "looking innocent" other problems we went on to fix

    And we fixied all the other problems but one without too much trouble. But the one about MS Kernel Audio which I initially guessed as a side-effect of the problems with other two drivers. After lots of Googling through the internet (not much detail) and eventually focusing on Microsoft’s own site and finally something meaningful in the Windows Developer;s Kit : I think this has been the problem the whole time!

    Not certain what package/when this and other media libraries get loaded but THEY’RE NOT PART OF THE STANDARD XP INSTALL YOU PUT ON YOUR MACHINE when you reinstalled. So it is THIS driver that's actually failing (parts missing) and making all the other sound stuff fail tho it appears at the user level as a sound driver problem which of course implies its Sigmatel sound card

    /* EDIT */
    Added note: so part of the problem is how MS has this packaged and does dependencies as one can reinstall XP followed by MS updates and have this unknown "hole" remain invisible and underneath it all
  18. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    OK I guess that makes some sence.
    So what do I do next then?
  19. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    The news in a nutshell and then back to our work…

    - Eventually tracked things back to something called Windows Driver Model (WDM) Audio library as source of Microsoft System Audio driver ( as learned what's listed by msinfo32)
    - The library also holds other drivers. Just which drivers, if any, a system needs from this lib varies based on what the system's sound vendor is trying to do
    - These extra drivers may be required and would be in addition to the the always required two: one for MS UAA Bus and one for sound card

    Next step (in next posts)
    - Steps to clean up after WDM and any other dependencies / pieces still lingering from older sound installs attempts
    - Cleanup means no DevMgr or msinfo32 references to Microsoft System Audio
    - And will provide a script so to capture a snapshot of Windows config/data both before and after cleanup

    And after that
    - Have you setup to run a trace
    - Run another / trace the next sound card install
    - (Hopefully) have better/different results after WDM cleanup. But in either case have some trace data to work with when done should it still be needed

    Will followup (probably tomorrow). And an fyi… With a clearer idea of what’s up and using somewhat different keywords in searches, i'm seeing hits from people with similar sound problems after SP2 reinstall (like you) and hits from people tryin to figure out and find how to fix different types of errors I now recognize as related to WDM (many other then the System Audio issue we saw here for you)

    P.S. Hope you've been having (and continue on having) a good holiday!@
  20. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    just as a footnote/fyi

    i started with a strong suspicion as to what versions of OS / Audio Bus / Sound card drivers were running together (and who still knows as still no final word / resolution) but will pass along some details not otherwise apparent. One thing i noted before:
    - MS releases KB1 update to add driver version 1.0 to XP SP1, then
    - MS releases KB2 update with driver changes (v1.0a) and adding it to SP2, then
    - MS includes a default driver in SP3 Windows system library

    I had noticed OP still using KB1 (the SP1) version driver and couldn't help thinking to try SP2 version or just going with SP3 but....

    i've since learned:
    - the driver install file in that Dell driver only applies the KB1 update. So i'd guess driver has been Windows Logo tested/proven to continue to work on the SP1 release
    - Almost made me a bit slower about suggesting we try applying the KB2 update and then taking it all to SP3
    - Have also found that SP3 is actually using the same SP2 software driver version only change is it;s now included in Windows system library
    /** EDIT **?
    And one more note: Also checked on a friend who i upgraded to SP3 long back (and remembered they run a Dell with XP and Hi-Def).. Turns out even with SP3 upgrade it still runs SP1 driver version! (MS never applied driver changes?) :confused: but still they've had NO sound problems either
  21. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    I looked some more into your problem. The more I look the more things point back to wdmaudio driver mentioned before. One of things found:
    ==> Driver file wdmaud.sys is installed / running on couple working systems I checked
    ==> The DriverView report you once ran for me: does not include any mention of wdmaudio driver!

    Also… just fyi… If misery loves company, I’ve seen others reporting your same problem: they lose sound after Windows reinstall. Some things you all have in common:
    => Always an XP SP2 reinstall
    => All using Hi Def sound cards (though the sound cards themselves vary)
    => Means you also all share some of the same Windows software for Hi Def support

    As to WHY wdmaudio driver isn’t running on your computer, will look at that next. An upgrade to SP3 might fix whatever Windows has screwed up now. But possibly not. So want to spend a little time looking/trying to fix in SP2 as info from doing that can also help if we find the SP3 upgrade only migrates the problem (not fix the problem) when going from SP2 to SP3.

    Things to do

    1. Run from a command window Start->Run, Enter: cmd.
    Note: Instead of re-typing a command, you can also copy text below then right click on command window's title bar (very top bar) then Edit->Paste
    • Verify swenum driver shows State= Running
      > sc query swenum
    • We’ll have Windows check protected system files (corrects if needed)
      Windows checks file version and file corruption. If any problem it replaces the file with a good copy. (for more info click here)
      SFC might take awhile. When its all done be sure note if any messages and what files (if any) were replaced

      > sfc /scannow
    • Dump registry settings for your sound drivers. Command below will create file RegDrv.txt on your Desktop
      (Command is one long text line. It might line break tho when displaying here)
      > reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32" /s > "%USERPROFILE%\DESKTOP\RegDrv.txt"
    2. Display all the wdmaud* files on your C: drive
    => Rt click Start->Search (to open search window)
    => Click Tools->Folder Options->View tab
    => Uncheck Hide extensions for known file types then OK

    => Click View->Choose Details
    => Check: Name, In Folder, File Version, Date Created, Date Modified
    => Note: Use Move Up and Move Down buttons to arrange ordering if you want
    => Click OK

    Set the search criteria as follows
    Attachment SearchWindow.gif displays search options and sample result
    => All or part of file name: wdmaud* (note the asterick symbol * is last character on that file name)
    => Look in: C:
    => Click More advanced options to see these options
    =====> Check box Search system folders
    =====> Check box Search hidden files and folders
    =====> Check box Search subfolders
    => Now, click Search

    Your search results:
    a) Since you’re running XP SP2 I think your File Versions will show 5.1.2600.2929
    b) Do a screen capture to keep for yourself
    c) If you can also attach screen capture to a post, is great. But if any problem w/attaching what's most important (you can just look and report back)
    ===> For the 4 files in the box below, see if the same file exists in the same folder on your machine. Note any version numbers.
    wdmaudio.inf	C:\WINDOWS\inf
    wdmaudio.PNF	C:\WINDOWS\inf
    wdmaud.sys	C:\WINDOWS\system32\drivers	 5.1.2600.5512
    wdmaud.drv	C:\WINDOWS\system32	 5.1.2600.5512

    3. Click here to download file devcon.exe. SAVE to disk, double click to open
    => When prompted for folder, enter C:\devcon click Unzip button
    => Copy file C:\devcon\I386\devcon.exe to folder C:\Windows\system32 (this is the 32bit version)

    4. Download the attachment DevQuery.txt
    => Save to Desktop. Change file extension to .bat so it's now DevQuery.bat
    => Double click DevQuery.bat. Will collect data and put file DevQueryData.txt on your Desktop

    If you could do these when you can, and then post back with
    => registry dump file plus
    => DevQueryData.txt file and
    => result of from wdmaud* file search

    i'm going to check a coupla things then post on how to install wdmaudio driver by hand and reinstall the other sound drivers so hopefully they can all run and work together again!

    Attached Files:

  22. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    OK I'm posting this as i do the work requested.

    sc query swenum-
    Status = Running

    scf /scannow-
    I ran through that (which took 10-15 min) and nothing happned. went throught the status load bar thing and then just pulled up the cmd prompt

    reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32" /s > "%USERPROFILE%\DESKTOP\RegDrv.txt"-
    I dont know if you need the file it created so i uploaded it anyways. better save than sorry

    OK for the files wdmaud.sys i have 6 of them. All in diffrent places as listed
    -C:\WINDOWS\Driver Cache\i386
    -C:\WINDOWS\Driver Cache\i386\

    And I have 4 wdmaud.drv but only 2 with that version number. Also out of the 6 .sys i have 2 also with that version number

    and on a lighter half-hearted note
    I rember having LOTS of fun makin batch files on the schools comps and pissing every one off! You can have WAYY to much fun with them :haha:
  23. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    Oh yea, fun with batch files! ;)

    Just did a quick once over need look further but:
    - When you ran the DevQuery script. Were you seeing error messages on your screen.
    - As the file you sent is empty (the couple lines you see in the output file don't count)
    - Implies the output from the devcon.exe tool You downloaded prior) called when script runs had errors as i didn't direct errors to the file, just normal output.

    You see errors displayed? if you simply type devcon at command prompt do you get see message about devcon usage? (is good) a general can't find something? (is bad)

    /* EDIT */
    is interesting as if you see wdmaud.sys in C:\WINDOWS\system32\drivers as you indicate means it at least getting installed now (wasn't before) tho still doesn't mean things are right. What version shows up this file in this folder??
    From a command prompt, also try
    > sc query wdmaud and it now shows state= Running?
  24. TridentCrash

    TridentCrash TS Rookie Topic Starter Posts: 68

    Umm... When i run the batch file it tries to run it like a million times?
    But i got a diffrent output file this time round.

    And as for the "sc query wdmaud" its showing state as "Stoped"

    oh wait... the tiredness is kickin in.
    i guess there is in error in that batch file or something cause it just like copied and pasted it over and over...?
  25. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    1) will look at the batch (still a problen thing) tomorrow
    2) and like i said before, we're gettin closer. wdmaud= Stopped means its definitely indicator wdmaud is a problem needs to fix. Thing with computers is hoping is the ONLY problem to fix! and NOT find another after it.

    but we;re for moving right direction for sure
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...