>From the small amount of data that Erik presents here, this is consistent with >the crashes that he's been seeing consistently for several months: The 1394 >driver is completing an Isochronous Receive using a bad transaction handle.
This is either a bug in the 1394 driver, or a bug in the Flex driver. Based on the weight of the evidence from several of these crashes, it's starting to look MORE like the 1394 driver. Has anybody at Flex or the IHV brought these crashes to the attention of Microsoft support? Is there an open case number? If so, and I could get that case number, I could probably talk to some friends and find out what the story is... Peter K1PGV ---------------- Stack: nt!KeBugCheckEx df01000!imp_WdfDmaTransactionRelease+0x34 1394ohci!IsochRx::WdfEvtNotificationDpc+0x1ce Wdf01000!FxDpc::FxDpcThunk+0x78 nt!KiRetireDpcList+0x1bc nt!KyRetireDpcList+0x5 nt!KiDispatchInterruptContinue Some !analyze -v output: > WDF_VIOLATION (10d) > The Kernel-Mode Driver Framework was notified that Windows detected an > error > in a framework-based driver. In general, the dump file will yield > additional > information about the driver that caused this bug check. > Arguments: > Arg1: 0000000000000005, A framework object handle of the incorrect type > was passed to > a framework object method. > Arg2: 0000000000000000, The handle value passed in. > Arg3: 0000000000001401, Reserved. > Arg4: fffffa8004d4a010, Reserved. > _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
