"Naresh" <> wrote in message
news:044efa79-836f-428c-8ddb-...
> On Apr 29, 4:34 am, "Pavel A." <pave...@12fastmail34.fm> wrote:
>> Does the arg 2 (A pointer to Miniport block) really point to your device?
>> --pa
>>
>> "Naresh" <nar...@gmail.com> wrote in message
>>
>> news:bbe40073-db22-4a53-a841-...
>>
>> > Hi,
>>
>> > When i try to complete a Pending Reset with NdisMResetComplete, the
>> > system / verifier bugchecks with
>> > ***NDIS*** : Miniport (null) - Completing reset when one is not
>> > pending.
>>
>> > The AddressingReset value is set to FALSE and always return
>> > NDIS_STATUS_PENDING from the MiniportResetEx handler.
>>
>> > I try to complete the reset from a workitem.
>>
>> > Any help on this will be greatly appreciated.
>>
>> > This is the bug check code. (0x0000007c)
>>
>> > BUGCODE_NDIS_DRIVER (7c)
>> > This is the NDIS Driver Bugcheck for Windows Server 2003 and later.
>> > For Windows 2000 and Windows XP, see 0xD2, BUGCODE_ID_DRIVER.
>> > Arguments:
>> > Arg1: 000000000000000f, A Miniport driver is calling
>> > NdisMResetComplete without
>> > any pending reset request.
>> > Arg2: fffffa801bf25000, A pointer to Miniport block. !ndiskd.miniport
>> > on
>> > this pointer for more info.
>> > Arg3: 0000000000000000, Reset status.
>> > Arg4: 0000000000000000, AddressingReset BOOLEAN. (not much of a use).
>>
>> > Regards,
>> > Naresh
>> > (Microsoft India Community Star)
>
> Pa,
>
> Thanks for the reply.
>
> Yes the arg2 points to my ethernet adapter.
Then maybe you actually call NdisMResetComplete twice, because the work item
runs on two CPUs, or don't clear some flag, and so on.
-- pa
|