MiniportUnload called immediately after DriverEntry

NTDEV
1

I maintain an SDIO based native WiFi driver (NDIS 6.0, Windows 7 32-bit).

For some devices the driver loads and runs correctly. However for a different batch of the same devices MiniportUnload is called immediately after DriverEntry.

Have you seen this phenomenon before?
Please let me know if you have some insights about what could cause this behaviour.

Thanks!

2

>

I maintain an SDIO based native WiFi driver (NDIS 6.0, Windows 7
32-bit).

For some devices the driver loads and runs correctly. However for a
different
batch of the same devices MiniportUnload is called immediately after
DriverEntry.

Have you seen this phenomenon before?
Please let me know if you have some insights about what could cause
this
behaviour.

Does the checked build of ndis.sys give you any hints about what it is
doing?

James

3

What does Device Manager say about the device? I assume it has a
yellow-bang and a code hinting at why the device failed to initialize.

Since you don’t mention getting called at MiniportInitialize it can be
inferred that whatever the system does not like about that device, it is
being rejected by either NDIS (the wrapper code) or a filter in the stack.

I suggest starting with what DM has to say in addition to James’ suggestion.

Good Luck,
Dave Cattley

4

Thanks for your answers, and sorry for the late reply.

Indeed MiniportInitialize is not getting called at all. Rather DriverEntry is called, then MiniportUnload. No other callbacks are invoked.

I will look further into this issue (use the checked build of ndis.sys as James suggested etc) and will post here any additional findings.

Yariv