BSoD Crash: More info.

[Bryan Kadzban]

George S. Lockwood wrote:
> what could the service be doing to cause this behavior?

Using a version of WinPcap that blue-screens, would be my guess.  ;-)

> any idea to try?

WinPcap 4.0 beta?

The supplicant has no code that runs in kernel-mode, so it can't cause a
blue-screen.  (At least, not directly.)  However, WinPcap does (it has a
kernel-mode protocol driver that it uses to capture the frames), and
this driver (in WinPcap 3.1 and earlier) has at least one bug that
causes a BSOD when a driver is unloaded.

(Well, actually, the BSOD happens on the next NDIS OID request to a card
*after* that card's driver is unloaded.  But the supplicant seems to
make NDIS requests fairly often.)

In theory, the code that the latest supplicants have to listen for WMI
adapter-removal events should fix this, but there's still a race between
the WMI event being delivered and the supplicant making an NDIS request,
so it's not a perfect solution.  You need WinPcap 4.0alpha1 or later to
really fix the problem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060922/a5cbe952/attachment.pgp