From: pg.gupta on

I found the problem. The union parameter that I passed to
NdisMSetMiniportAttributes
has wierd data (I wrote the union twice, for two different
structures). NdisMSetMiniportAttributes
returned success however. I think the bad data caused the ndis.sys to
bugcheck later.

After fixing the above problem in my code, the problem went away.

Thanks for your help.

/Piyush


On Feb 17, 2:54 pm, "Alireza Dabagh [MS]" <a...(a)online.microsoft.com>
wrote:
> Looks like at this point we have returned back from MiniportInitializeEx
> successfully which means this is most likely the deadman timer NDIS is
> trying to set up for the miniport. Make sure you call
> NdisMSetMiniportAttributes before you return from your MiniportInitializeEx
> otherwise NDIS would try to set a timer that has not been initialized. (and
> even if we don't bugcheck here, we will definitely bugcheck later).
>
> -ali
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> <rookie...(a)gmail.com> wrote in message
>
> news:1171634238.164989.97370(a)q2g2000cwa.googlegroups.com...
>
>
>
> > I am not creating these timers. What can be the possible reason ndis
> > wants to create timers?
>
> > On Feb 16, 4:30 pm, rookie...(a)gmail.com wrote:
> >> I am a newbie in driver development...How did you figure this? How do
> >> I proceed from
> >> here?
>
> >> Thanks.
>
> >> On Feb 16, 4:05 pm, "Stephan Wolf [MVP]" <stew...(a)hotmail.com> wrote:
>
> >> > Seems like NDIS is trying to set some timer but is using some NULL
> >> > pointer. Not sure why NDIS does this or why it uses a NULL pointer.
>
> >> > Stephan
> >> > --
> >> > On Feb 16, 10:57 am, rookie...(a)gmail.com wrote:
>
> >> > > Hi,
>
> >> > > I am writing a x86 ndis 6.0 miniport driver. I install the driver on
> >> > > x86 vista from device manager. When installing,
> >> > > Miniportinitializeex is called. Before returning status from
> >> > > miniportinitializeex, I log a line with status.
> >> > > In WinDbg, I see this log line and then a bug check
> >> > > (IRQL_NOT_LESS_OR_EQUAL in ndis.sys).
>
> >> > > Has anybody seen this? What could be the problem?
>
> >> > > Thanks.