Crash in CMixer::SendNotificationToWinmm (wdmaud.drv) RRS feed

  • Question

  • Hello guys,

    I have a VoIP application which use waveXxx to communite with the speakers/microphone. I encounter a crash in  CMixer::SendNotificationToWinmm (wdmaud.drv) on WIN7 64bit system and it happens while we unplugged the microphone from the PC. I can reproduce the issue on all WIn 7 machines that I have.

    Have anybody found this issue so far?

    The call stack looks like :

         ntdll.dll!_RtlpWaitOnCriticalSection@8()  + 0x99 bytes    
         ntdll.dll!_RtlEnterCriticalSection@4()  + 0x16a38 bytes    
    >    wdmaud.drv!CMixer::SendNotificationToWinmm()  + 0x22 bytes    
         wdmaud.drv!CSessMixerControl::ControlChangeCallback()  + 0x33 bytes    
         wdmaud.drv!CSessMixerControl::OnStateChanged()  + 0x13 bytes    
         AudioSes.dll!CStateChanged::Invoke()  + 0x1c bytes    
         AudioSes.dll!CLockedList<ATL::CComPtr<IAudioSessionEvents>,0,1>::ForEachEntry()  + 0x84 bytes    
         AudioSes.dll!CAudioSessionControl::OnAudioSessionEvent()  + 0x18b bytes    
         AudioSes.dll!CAudioSessionControl::CAudioSessionNotificationDelegator::OnMediaNotification()  + 0x17 bytes    
         MMDevAPI.dll!CMediaNotifications::OnMediaNotificationWorkerHandler()  - 0x2f bytes    
         MMDevAPI.dll!CMediaNotifications::MediaNotificationWorkerHandler()  + 0x10 bytes    
         ntdll.dll!_TppSimplepExecuteCallback@8()  + 0x7b bytes    
         ntdll.dll!_TppWorkerThread@4()  + 0x5a4 bytes    
         kernel32.dll!@BaseThreadInitThunk@12()  + 0x12 bytes    
         ntdll.dll!___RtlUserThreadStart@8()  + 0x27 bytes    
         ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes    

    Any help is appreciated.

    • Moved by Mike Dos Zhang Monday, July 30, 2012 5:54 AM not a Windows Desktop dev question (From:General Windows Desktop Development Issues)
    Thursday, July 26, 2012 9:13 PM

All replies

  • It seems that the method call is in a audio driver module, wdmaud.drv.

    After that call the thread enter into a critical section and waiting on, so I think maybe it is caused by your audio's driver codes makes it crash based on multi-thread problem.

    For more research, I'm afraid you will need your audio driver product's company support.

    Mike Zhang[MSFT]
    MSDN Community Support | Feedback to us

    Friday, July 27, 2012 4:07 AM