I'm debugging a WaveCyclic-based driver. So far, it looks like the driver has successfully created the port and miniport objects and hooked everything up (at least I don't get any errors). The driver puts an entry in the Event Log that confirms this. The sequence of events so far looks like this: NewAdapterCommon(F9E7DD24, F966D390, 00000000, 0) NewMiniportWaveCyclic(F9E7DC2C, F966D4D0, 00000000, 0) CMiniportWaveCyclic::Init() CMiniportWaveCyclic::GetDescription(818062E8) NewMiniportWaveCyclic(F9E7DC2C, F966D4D0, 00000000, 0) CMiniportWaveCyclic::Init() CMiniportWaveCyclic::GetDescription(818030E0) NewMiniportTopology(F9E7DC2C, F966D4D0, 00000000, 0) CMiniportTopology::Init() CMiniportTopology::GetDescription(8175AC60) Next, I get a couple of property handler calls asking for my component ID: PropertyHandler_WaveMiniport(817FC380) CMiniportWaveCyclic::PropertyHandler_WaveMiniport(817FC380) PropertyHandler_WaveMiniport(817FC380) CMiniportWaveCyclic::PropertyHandler_WaveMiniport(817FC380) After this, there is an invalid memory reference at sysaudio!AddPinToFilterNode+5: sysaudio!AddPinToFilterNode+5 f5cb4b35 8b4b04 mov ecx,[ebx+0x4] (ebx=00000000) I'm sure the problem is in my code somewhere. My best guess is that something is wrong in my description tables, but I sure don't see anything obvious. Has anyone run into this before? Any suggestions? If I install checked builds of portcls and sysaudio, is that likely to provide any helpful debug info? Thank you! -Dan ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.de/