Prev: How to query available bluetooth devices in the room
Next: send commands to the keyboard controller
From: Tulup on 22 Jun 2005 05:23 Hi. Can anybody describe situations when using avssamp (AVStream example based virtual video capture driver) generates BSD with this error ? BSD doesn't clarify what sys file has generated the problem, i supose that is because of my new video capture driver...
From: Gary G. Little on 22 Jun 2005 10:11 If you are asking as a developer, I'd say your driver is completing an IRP twice. In this case, you completed what you thought was your IRP, which had already been completed by an as yet unkown function in your code, and reassigned to the AV driver, which then completed it again. If you are asking as a user, then I'd say this is not the proper forum for such a question. The personal opinion of Gary G. Little "Tulup" wrote: > Hi. > Can anybody describe situations when using avssamp (AVStream example based > virtual video capture driver) generates BSD with this error ? > BSD doesn't clarify what sys file has generated the problem, i supose that > is because of my new video capture driver... > > >
From: Tulup on 23 Jun 2005 01:02 Thank for your comments, Gary. It was developer question. I haven't seen such problem myself, but some user emailed me BSD screenshot. I can't catch the same problem (repeat it) within my hardware (PC). So i am trying to ask here, maybe somebody can help... "Gary G. Little" <GaryGLittle(a)discussions.microsoft.com> wrote in message news:2A4CEA06-0883-42BA-A15B-AD2E85B1AE24(a)microsoft.com... > If you are asking as a developer, I'd say your driver is completing an IRP > twice. In this case, you completed what you thought was your IRP, which > had > already been completed by an as yet unkown function in your code, and > reassigned to the AV driver, which then completed it again. > > If you are asking as a user, then I'd say this is not the proper forum for > such a question. > > The personal opinion of > Gary G. Little > > > "Tulup" wrote: > >> Hi. >> Can anybody describe situations when using avssamp (AVStream example >> based >> virtual video capture driver) generates BSD with this error ? >> BSD doesn't clarify what sys file has generated the problem, i supose >> that >> is because of my new video capture driver... >> >> >>
From: Gary G. Little on 23 Jun 2005 10:14 Then as a developer you need to go look at your code and check for synchronization problems in completing an IRP. If you do ANYTHING with an IRP pointer after IoCallDriver has been called you have a problem. The classic errer here is seen on SMP with two paths that can complete the same IRP. One path needs to be emliminated, or access to the IRP must be synchronized, typically with a spinlock. The personal opinion of Gary G. Little "Tulup" wrote: > Thank for your comments, Gary. > It was developer question. I haven't seen such problem myself, but some user > emailed me BSD screenshot. I can't catch the same problem (repeat it) within > my hardware (PC). So i am trying to ask here, maybe somebody can help... > > "Gary G. Little" <GaryGLittle(a)discussions.microsoft.com> wrote in message > news:2A4CEA06-0883-42BA-A15B-AD2E85B1AE24(a)microsoft.com... > > If you are asking as a developer, I'd say your driver is completing an IRP > > twice. In this case, you completed what you thought was your IRP, which > > had > > already been completed by an as yet unkown function in your code, and > > reassigned to the AV driver, which then completed it again. > > > > If you are asking as a user, then I'd say this is not the proper forum for > > such a question. > > > > The personal opinion of > > Gary G. Little > > > > > > "Tulup" wrote: > > > >> Hi. > >> Can anybody describe situations when using avssamp (AVStream example > >> based > >> virtual video capture driver) generates BSD with this error ? > >> BSD doesn't clarify what sys file has generated the problem, i supose > >> that > >> is because of my new video capture driver... > >> > >> > >> > > > >
|
Pages: 1 Prev: How to query available bluetooth devices in the room Next: send commands to the keyboard controller |