Marvell WLAN BSOD on Windows shutdown

[wmb@…]

Under Windows SP3, if the wireless driver is enabled and associated with an access point, when you shutdown Windows, you usually get a blue screen of death, citing the MV83X8 driver as the source.

Driver version: 8.72.706.716 and .717 behave identically in this respect

Firmware version: the version that was submitted to Microsoft

BIOS version: OFW Q2E27 and Insyde BIOS behave identically in this respect

OS version: Windows XP SP3 (SP2 doesn't exhibit the BSOD, but sometimes hangs during shutdown, possibly related)

Analysis:

The problem happens when NDIS calls back into the driver via the SetInformation miniport handler after the adapter data structure has already been freed via the Shutdown miniport handler. When the data structure is freed, the memory behind it is removed from the page tables, so the later attempts to use that pointer result in unhandleable page faults.

According to my reading of the NDIS miniport API, the adapter structure is supposed to be freed by the Halt miniport handler, not by the Shutdown handler.

[rchokshi]

More information from Tony @ Microsoft today:

We get a blue screen when connecting to a wireless network provided by a Microtik RB133 AP (details below). No problem with other MicroTik AP model RB433, same configuration, or other APs.

IRQL_NOT_LESS_OR_EQUAL

*** STOP: 0x0000000A (0XFE9E9000,0X00000002,0X00000000,0X804D9A69) or *** STOP: 0x0000007E (0XC0000005,0XF78F045D,0XF9FD35E8,0XF9FD32E4)

MV83X8.SYS - Address F78F045D base at F78E0000, DateStamp 485bb0d1

AP Model MicroTik RB133 firmware v3.7 Mixed B/G mode 2.4Ghz

Wireless network SSID: Escuelita Open authentication, encryption disabled

Marvell MV83x8 Wireless LAN USB Adapter Driver version: 8.72.706.715 Date: 06/04/2008

[wmb@…]

Marvell supplied a new wireless driver that fixes this problem. The new driver is in the sanctioned XP image.