[wdmaudiodev] Re: BSOD issue for portcls.sys
- From: "Lionberger, Brad" <brad.lionberger@xxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Tue, 6 Nov 2007 08:51:44 -0800
Thanks for the help. It pointed me in the right direction. It turned
out to be a synchronization issue that causes just what you describe.
Brad
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Pages
Sent: Monday, November 05, 2007 1:42 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: BSOD issue for portcls.sys
I don't know if this helps, but in my own case I got caught by calls to
FreeAudioBuffer while the stream was still in a running state - from
memory I think this happens if the application is abruptly closed
(Ctrl-C in the case of a command line app). I added a call to stop my
DMA hardware before processing FreeAudioBuffer and that fixed it.
Jeff
----- Original Message -----
From: Lionberger, Brad <mailto:brad.lionberger@xxxxxxxxx>
To: wdmaudiodev@xxxxxxxxxxxxx
Sent: Tuesday, November 06, 2007 7:03 AM
Subject: [wdmaudiodev] BSOD issue for portcls.sys
Hi all,
I am seeing a BSOD issue where audiodg.exe calls my Close
handler, I forward the IRP to the port class as it is an IRP I don't
handle, the portcls!DispatchClose then calls
portcls!CPortPinWaveRT::Close+0x87 which causes a BSOD.
The BSOD occurs with a paused active stream on the device during
sleep stress tests. Any thoughts on what my audio driver is not
doing/should be doing? Thanks in advance.
Brad
Other related posts:
