Bug Check 0x1DE: BUGCODE_WIFIADAPTER_DRIVER
The BUGCODE_WIFIADAPTER_DRIVER bug check has a value of 0x000001DE. This indicates that the operating system encountered an error caused by a networking driver managed by WiFiCx. The Wi-Fi WDF class extensions (WiFiCx) supports KMDF-based Wi-Fi client driver for Wi-Fi devices. For more information, see Introduction to the Wi-Fi WDF class extension (WiFiCx).
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
BUGCODE_WIFIADAPTER_DRIVER Parameters
Parameter | Description |
---|---|
1 |
WiFiCx BugCheck subcode values listed here. 0x0 - The WiFiCx private globals have been corrupted. 0x1 : A driver called a WiFiCx API requiring passive IRQL at illegal IRQL. 0x2 : A driver called a WiFiCx API requiring IRQL less than or equal to dispatch at illegal IRQL. 2 - Size of struct passed by the driver. 3 - Size of struct used by OS's WiFiCx version. Note that it is not required that this matches exactly, with the passed struct, but the size of structs from older WiFiCx versions should be <= than those from newer versions. 0x4 : The driver reported and invalid wake reason. 0x5 : The driver passed an invalid or corrupted WIFI_POWER_OFFLOAD_LIST to a WiFiCx API.
0x6 : The driver passed an invalid or corrupted WIFI_WAKE_SOURCE_LIST to a WiFiCx API. 0x7 : The driver passed an invalid or uninitialized WIFI_INTERFACE_CONTEXT to a WiFiCx API. 0x8 : The driver passed a WIFI_ADAPTER_TX_DEMUX with an invalid WIFI_ADAPTER_TX_DEMUX_TYPE to a WiFiCx API. 0x9 : The driver passed a WIFI_ADAPTER_TX_DEMUX with an invalid Range to a WiFiCx API. 0xA : The driver reported a wake reason at an invalid time. Wake reasons should be reported from within the disarm wake callback. 0xB : The driver is using a deprecated field within a WiFiCx struct. |
2 |
Dependent on Param 1 |
3 |
Dependent on Param 1 |
4 |
Reserved |
Resolution
The !analyze debug extension displays information about the bugcheck and can be helpful in determining the root cause.
Parameter 1 describes the type of violation. Look at the call stack to determine the misbehaving driver.