none
Sound has stopped working; failed to play test tone; format not supported by the device (Vista x64 Ultimate)

    General discussion

  • I can no longer hear any sound from my speakers/headphones. This happened suddenly yesterday without any hardware changes or noticeable software updates.

    -- The sound is not muted and the volume is set to full.
    -- In the device manager, my SigmaTel HD Audio device has no warnings or errors.
    -- I can't find any related messages in the Event Viewer.
    -- The primary audio device is selected as the default for playback. The mixer shows my media player as being mixed properly to the device.
    -- In the sound control panel, under Playback > Speakers/Headphones > Properties > Advanced:
     - I get the error message "failed to play test tone" when I try to Test my Default Format (dvd quality)
     - I get the error message "format not supported by the device" when I try to change my Default Format
    -- Note that unlike others who have similar problems, I'm not joined to a domain

    I've tried
    *  rebooting
    *  uninstalling and reinstalling the driver for the sound card
    *  "disable all enhancements" in the sound control panel
    (http://social.msdn.microsoft.com/forums/en-US/windowspro-audiodevelopment/thread/b09e43ba-3ffa-4a45-9593-8eee686f124a/)
    *  looking in the registry for some registry key (not found)
    (http://www.consumingexperience.com/2009/04/failed-to-play-test-tone-no-sound-on.html)

    Computer details
    Dell XPS M1530
    Vista Ultimate x64 SP1 with current updates
    SigmaTel driver version 6.10.0.5866

    **Update**
    I followed the following steps:
        * using regedit, go to HKLM\System\CurrentControlSet\Control\WMI\AutoLogger\Audio and change the “Start” value from 0 to 1.
        * Reboot the machine
        * Try to play an audio file.
        * Post a link to the generated log file which you can find in: %WINDIR%\system32\LogFiles\Audio

    but don't know where to post the resulting AudioSrv.Evm.001 file. It's also not human readable and I can't find what utility parses it for reading.

    **Another update**
    Still can't read the EVM. logparser 2.2 can't parse it.
    Found this thread which interested me but isn't applicable to x64 (I think):
    http://social.msdn.microsoft.com/Forums/en-US/mediafoundationdevelopment/thread/94cdc662-e974-43de-8feb-6eb156924347

    **YAU**
    Dell confirms it's an OS issue after troubleshooting with me for a couple of hours (wow)
    Is there a way to look at this EVM file _without_ installing the Windows Driver Kit??
    Friday, June 12, 2009 1:52 PM

All replies

  • Hi,

     

    Thanks for posting in Microsoft TechNet Windows Vista Forum.

     

    Upon your description, I see that you have done a lot of research and tests. Unfortunately, none of these troubleshooting works.

     

    Based on my experience, this issue related to "failed to play test tone" can be related to several reasons. It also includes hardware defect. I am confusing why Dell confirms that the issue is related to Operating System. Could you let me know what operation Dell had troubleshot with you?

     

    Meanwhile, here I just provide more troubleshooting except what you performed. If it doesn't work, I may also need to recommend that you contact Dell for support.

     

    1. Microsoft has released a Hotfix to troubleshoot related to "Failed to play test tone".

     

    http://support.microsoft.com/kb/930883

     

    2. Make sure that these services are started.

     

    Windows Audio

    Multimedia Class Scheduler

    Remote Procedure Call

    Windows Audio Endpoint Builder

     

    3. I noticed that this issue occurred not long ago, I may need to suggest that you perform a System Restore to the previous restore point when the computer without any problem.

     

    System Restore

    ==============

     

    1)     Please click on Start and choose All Programs, Accessories, System Tools, and then Windows Backup.

    2)     Click Restore on the left pane.

    3)     Choose Basic Restore.

    4)     Follow the wizard and click Next.

    5)     If you would like to restore everything in the backup, we can check the box “Restore everything in this backup” on the top of the window.

    6)     We can also browse and choose certain files and folders to restore. Then, click Next.

    7)     Then choose the folder to save the recovered files and click Next.

    8)     When we see a “Restore is complete!” message, click Finish.


    Meanwhile, as I know, I'm afraid that there is no other way to look at EVM file except Windows Driver Kit. Maybe there are some third-party software that out of my mind can look at EVM files, you may need to perform more research on Internet.


    Hope this helps. Thanks.
    Monday, June 15, 2009 9:38 AM
  • Ahh, it seems there is now a 64bit version of that hotfix. I'll try it and report back.

    I just checked and the services you mentioned are all running.

    The Dell technician essentially repeated one of my troubleshooting steps, but with a bit more thoroughness. He uninstalled the driver, deleted the remaining related files in Program Files and Program Files (x86) and deleted the associated registry keys in the Software sections of HKLM and HKCU. Then he reinstalled the driver. The problem remains.

    I suppose he decided it was an operating system issue because both my "Headset Earphone" (bluetooth) and "Headphones/Speakers" (onboard audio) give the "failed to play test tone" error. Oddly enough, the third playback device, "HDMI" (onboard also) does not give this error.

    Honestly, I believe it is an operating system (and not hardware) problem for the same reason. If I dig around in that EVM file, I wouldn't be surprised to see that the problem is with some kind of digital-to-analog conversion process. (What else is different between HDMI and Analog output handling in Windows?)

    Unfortunately (in this case) I don't use System Restore because my HDD is small and it "wastes" too much space. I do semi-regular disk images instead (my last one was after my last significant software change, 2 months ago). I would rather resolve this issue without restoring for two reasons:

    1) the onset was seemingly unprovoked by hardware or software changes; so, I would rather be able to fix this problem than resort to restoring every time this happens

    2) many others have had this problem and seem dissatisfied with the support they've gotten (I figure I can help a bit)

    Btw, thanks Dale for getting back to me on this. I would have replied sooner but I didn't get an email when you posted (I have notification on already).

    **update** The hotfix says "this update does not apply to your system".
    from the KB article: "Applies to ... Windows Vista Ultimate 64-bit Edition"
    hotfix filename: Windows6.0-KB930883-x64.msu
    from my system information:
        OS Name    Microsoft® Windows Vista™ Ultimate
        Version    6.0.6001 Service Pack 1 Build 6001
    • Edited by RipT Thursday, June 18, 2009 11:48 PM
    Thursday, June 18, 2009 11:34 PM
  • Hi,

     

    Thanks for your update.

     

    Unfortunately, neither of above works. Based on my experience, there might be some system files corrupted or unexpected deleted. Thus we may need to perform a System Repair to fix it, as I know, Dell provides an installation disc with each customer.

     

    Note: Please ensure that the DVD-ROM is the first booting device, and back up your files from System disk to another none system disk.

     

    1.     Please insert the Windows Vista DVD and reboot the computer.

    2.     When we are prompted to press a key to boot from the DVD, please press Enter or the space bar.

    3.     Choose your language settings, and then click Next.

    4.     Click Repair your computer.

    5.     Select the operating system you want to repair, and then click Next.

    6.     On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

     

    Hope this helps. Thanks.

    Friday, June 19, 2009 7:17 AM
  • I used a retail Vista Ultimate x64 DVD to install the OS myself (I have 4GB of RAM and Dell provided Vista x32; so, I upgraded).

    I guess I should slipstream SP1 into my Vista x64 DVD it and then use it to repair? How does that work with updates that have come out since SP1?

    I'll report back on my progress.

    Thanks Dale.

    **Update**

    I created a DVD with SP1 and tried "Startup Repair". It reported that it couldn't find any problems.

    I guess I'll install that Windows Driver Kit and look at the windows sound system log.

    **Update**

    On a whim I used the Ubuntu 9.04 Desktop CD to boot Ubuntu Live (not installed)
    Sound works in Ubuntu...
    Then I split my HDD into two partitions and I'm now dual-booting Windows 7 RC x64 . Sound is working with the same Vista x64 SigmaTel drivers.

    I've also been told to try sfc /scannow; so, I'm going to try that on the Vista partition before installing the Windows Driver Kit

    **Update**

    I tried sfc /scannow and it found corruption that it couldn't fix:

    C:\Users\Rip>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 55% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    CBS.log error lines:

    2009-06-30 17:47:13, Error                 CSI    0000014a (F) STATUS_OBJECT_NAME_NOT_FOUND #2947664# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (STANDARD_RIGHTS_READ|FILE_READ_ATTRIBUTES), oa = @0x20dd0d0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[124]"\??\C:\Windows\WinSxS\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.6001.18000_ar-sa_c225f582a3cec90c"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x20dd0b0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = 0x00004000, eab = NULL, eal = 0, disp = Invalid)
    [gle=0xd0000034]
    2009-06-30 17:47:13, Error                 CSI    0000014b@2009/6/30:22:47:13.692 (F) d:\longhorn\base\wcp\sil\merged\ntu\ntsystem.cpp(1849): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    [gle=0x80004005]
    2009-06-30 17:47:16, Error                 CSI    0000014c (F) STATUS_OBJECT_NAME_NOT_FOUND #2947663# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
    2009-06-30 17:47:16, Error                 CSI    0000014d (F) STATUS_OBJECT_NAME_NOT_FOUND #2947662# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x20dd9c8->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.6001.18000_ar-sa_c225f582a3cec90c"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
    [gle=0xd0000034]
    • Edited by RipT Tuesday, June 30, 2009 9:54 PM
    Friday, June 19, 2009 5:24 PM
  • Im having the same exact problem but with my Dell XPS 420 running Vista Ultimate. I stayed with multiple technicians for hours and they all came up with the same answer. The problem is from the OS. 

    Any lucky with finding a solution? 
    Saturday, August 15, 2009 4:18 AM
  • No...

    I installed the Windows 7 RC and everything works okay.
    Saturday, August 15, 2009 6:14 AM
  • I realize this is an old thread, but I just encountered the same problem on my Dell laptop, after using it for 2 years.  

    I found a couple of solutions that are not mentioned here.  

    The simplest and the one that worked for me is:

    1. On your Start Menu, in the StartSearch Box, type:  services.msc
    2. When the Services Window pops up, find: Windows Audio and Windows Audio Endpoint
    3. Right click on these two services and Restart.  
    Voila, Sound.  :)  

    That solution and several others are given with easy, pictorial, non-techie instructions here:  http://www.consumingexperience.com/2009/04/failed-to-play-test-tone-no-sound-on.html



    It could also be a problem with your permissions.  To correct a permissions problem, go to:
    1. Windows Start menu, choose 'Run...'.
    2. In the pop-up box, type: regedit.
    3. Navigate to 'Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
    4. Delete the registry key 'DefaultAccessPermission'. (If it isn't there, chances are this isn't the problem causing your lack of sound.)
    Beware that fiddling with your registry can cause system problems if you modify important settings.

    This info was found on the Windows Vista Forums here: http://www.vistax64.com/vista-general/119350-failed-play-test-tone-other-assorted-bugs-quirks-2.html#post565089


    This is a particularly frustrating issue when it happens, and when googling for answers, people have to search through a lot of unresolved forums.  Just thought I'd update this old one with a solution for anyone looking in the future.  

    Saturday, October 23, 2010 10:36 PM
  • I'm having the same problem.

    Services are all started, and restarting them doesn't help.

    Uninstalled sound drivers (IDT HD) and reinstalled them, but it doesn't help.

    Vista is updated with the latest patches including SP2.

    Almost completely the same as RipT:

    -- The sound is not muted and the volume is set to full.
    -- In the device manager, my IDT HD Audio CODEC device has no warnings or errors.
    -- I can't find any related messages in the Event Viewer.
    -- The primary audio device is selected as the default for playback. The mixer shows my media player as being mixed properly to the device.
    -- In the sound control panel, under Playback > Speakers/Headphones > Properties > Advanced:
     - I get the error message "failed to play test tone" when I try to Test my Default Format (dvd quality)
     - I get the error message "format not supported by the device" when I try to change my Default Format (except for DVD and CD quality)
    -- Note that unlike others who have similar problems, I'm not joined to a domain

    I've tried
    *  rebooting
    *  uninstalling and reinstalling the driver for the sound card
    *  "disable all enhancements" in the sound control panel
    (http://social.msdn.microsoft.com/forums/en-US/windowspro-audiodevelopment/thread/b09e43ba-3ffa-4a45-9593-8eee686f124a/)
    *  looking in the registry for some registry key (not found)

     

    The sound is working in Ubuntu, so it's not a hardware failure.

    SFC found errors which couldn't be fixed which include audio files:

    2010-11-26 13:10:01, Info                  CSI    000001ca [SR] Verify complete
    2010-11-26 13:10:01, Info                  CSI    000001cb [SR] Repairing 2 components
    2010-11-26 13:10:01, Info                  CSI    000001cc [SR] Beginning Verify and Repair transaction
    2010-11-26 13:10:01, Info                  CSI    000001cd Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.0.6002.18005_none_788b3d32e1c18b26\AUDIOKSE.dll do not match actual file [l:24{12}]"AUDIOKSE.dll" :
      Found: {l:32 b:UhGjMHFSaSxWwebZYBoid1LPGSorSN6848P+5mmO2XE=} Expected: {l:32 b:ZfVptykTB/0rD3goiPGOIwJ6j5hs+3txnKU+k/o7E2c=}
    2010-11-26 13:10:01, Info                  CSI    000001ce [SR] Cannot repair member file [l:24{12}]"AUDIOKSE.dll" of Microsoft-Windows-Audio-AudioCore, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-11-26 13:10:01, Info                  CSI    000001cf Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-11-26 13:10:01, Info                  CSI    000001d0 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-11-26 13:10:01, Info                  CSI    000001d1 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-11-26 13:10:01, Info                  CSI    000001d2 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-11-26 13:10:01, Info                  CSI    000001d3 [SR] This component was referenced by [l:160{80}]"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"
    2010-11-26 13:10:01, Info                  CSI    000001d4 Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-11-26 13:10:01, Info                  CSI    000001d5 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_d278d2aaa749970e\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
      Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
    2010-11-26 13:10:01, Info                  CSI    000001d6 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
    2010-11-26 13:10:01, Info                  CSI    000001d7 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.0.6002.18005_none_788b3d32e1c18b26\AUDIOKSE.dll do not match actual file [l:24{12}]"AUDIOKSE.dll" :
      Found: {l:32 b:UhGjMHFSaSxWwebZYBoid1LPGSorSN6848P+5mmO2XE=} Expected: {l:32 b:ZfVptykTB/0rD3goiPGOIwJ6j5hs+3txnKU+k/o7E2c=}
    2010-11-26 13:10:01, Info                  CSI    000001d8 [SR] Cannot repair member file [l:24{12}]"AUDIOKSE.dll" of Microsoft-Windows-Audio-AudioCore, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-11-26 13:10:01, Info                  CSI    000001d9 [SR] This component was referenced by [l:160{80}]"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-113_neutral_GDR"
    2010-11-26 13:10:01, Info                  CSI    000001da Hashes for file member \??\C:\Windows\System32\AUDIOKSE.dll do not match actual file [l:24{12}]"AUDIOKSE.dll" :
      Found: {l:32 b:UhGjMHFSaSxWwebZYBoid1LPGSorSN6848P+5mmO2XE=} Expected: {l:32 b:ZfVptykTB/0rD3goiPGOIwJ6j5hs+3txnKU+k/o7E2c=}
    2010-11-26 13:10:01, Info                  CSI    000001db Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.0.6002.18005_none_788b3d32e1c18b26\AUDIOKSE.dll do not match actual file [l:24{12}]"AUDIOKSE.dll" :
      Found: {l:32 b:UhGjMHFSaSxWwebZYBoid1LPGSorSN6848P+5mmO2XE=} Expected: {l:32 b:ZfVptykTB/0rD3goiPGOIwJ6j5hs+3txnKU+k/o7E2c=}
    2010-11-26 13:10:01, Info                  CSI    000001dc [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"AUDIOKSE.dll"; source file in store is also corrupted
    2010-11-26 13:10:01, Info                  CSI    000001dd Repair results created:
    POQ 87 starts:
     
    POQ 87 ends.
    2010-11-26 13:10:01, Info                  CSI    000001de [SR] Repair complete
    2010-11-26 13:10:02, Info                  CSI    000001df [SR] Committing transaction
    2010-11-26 13:10:02, Info                  CSI    000001e0 Creating NT transaction (seq 1), objectname [6]"(null)"
    2010-11-26 13:10:02, Info                  CSI    000001e1 Created NT transaction (seq 1) result 0x00000000, handle @0x654
    2010-11-26 13:10:02, Info                  CSI    000001e2@2010/11/26:12:10:02.159 CSI perf trace:
    CSIPERF:TXCOMMIT;3
    2010-11-26 13:10:02, Info                  CSI    000001e3 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

     

     

    Any ideas?

    Friday, November 26, 2010 1:13 PM
  • Fixed it by replacing the AUDIOSKE.dll with a version of another vista SP2 32bit computer.
    Sunday, November 28, 2010 10:34 PM
  • I've just had this happen on Windows 7 Ultimate 64 bit. WTF?!? Tried everything here (restarting services, checking reg entries). Obviously not gone for the hotfix as this is for Vista. Any help with this appreciated. Motherboard is Asus w6t6 with i7, plugged into green speaker jack, but even my skype headset (Netcom GN9330) plugged into usb is not working!

    This is definitely a software issue, only happened today. Haven't installed anything. Last updates installed were earlier in the week. Come on Microsoft, please fix it..

    < edit >

     Ok, found the fix on another thread, turned out its permissions, still doesn't explain why it suddenly happened though..

    http://social.msdn.microsoft.com/Forums/en-US/windowspro-audiodevelopment/thread/b09e43ba-3ffa-4a45-9593-8eee686f124a/?prof=required

    < /edit >

    Saturday, December 25, 2010 2:05 PM
  • OH MY GOD SRYITERSIUVGNAGWVTUNG IT WORKED DRYINUSHERIGUNERTVU THANK GOD FOR YOU BLESS YOU I HOPE YOU HAVE THE MOST SUCCESSFUL LIFE.

    you just saved mine lol. i wouldve died if my parents came back and found that the sound didnt work anymore.

    dude you're my savior.

    Tuesday, September 03, 2013 12:13 AM
  • Brilliant. Works a treat.
    Wednesday, December 25, 2013 8:23 PM