Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Wireless network adapter miniport driver receives incorrect MediaSpecificWakeUpEvents value

Wireless network adapter miniport driver receives incorrect MediaSpecificWakeUpEvents value

View products that this article applies to.

Summary

Consider the following scenario:
  • You install a driver for a wireless network adapter on a Windows 8.1-based computer.
  • You select the Allow this device to wake the computer option on the Power Management tab under the properties page of the wireless network adapter.
  • You put the computer into sleep mode (S3).
  • Windows sends the OID_PM_PARAMETERS object identifier (also known as OID) to the network adapter driver in order to enable the current hardware capabilities of the network adapter.
In this scenario, the MediaSpecificWakeUpEvents value of the OID_PM_PARAMETERS object identifier is incorrect. This issue occurs even when the wireless network adapter miniport driver advises this capability correctly.

↑ Back to the top

Workaround

To work around this issue, disable and then re-enable the wireless network adapter.

↑ Back to the top

Cause

This issue occurs because Network Driver Interface Specification (NDIS) does not update the MediaSpecificWakeUpEvents value when NDIS checks the Wake-up On LAN (WOL) option.

↑ Back to the top

More Information

When the miniport driver is loaded, NDIS will initialize the Power management capability based on different factors.

The system will only honor the WOL setting when the Allow this device to wake the computer option is selected. If the option is not selected, the system does not check the hardware WOL capabilities. 

The hardware WOL capabilities cause failures of the later OID_PM_PARAMETER that is sent from the upper native wireless network adapter driver during the binding phase. When this issue occurs, NDIS does not copy the enabled WOL patterns onto the miniport current power configuration parameters. This causes the system to send OID_PM_PARAMETER without the expected value for MediaSpecificWakeUpEvents to the miniport driver. When the Allow this device to wake the computer option is selected, NDIS should have updated MediaSpecificWakeUpEvents to the miniport driver by using the current power management parameter. 

You can work around this issue by disabling and then re-enabling the wireless network adapter. If the Allow this device to wake the computer option is selected and the miniport is disabled and then re-enabled (or is rebound for other reasons), NDIS will set the miniport WOL capability based on the advised one from the miniport driver and the native wireless network adapter driver. Then, NDIS successfully sends OID_PM_PARAMETER and MediaSpecificWakeUpEvents values that are copied to the current power management parameters on the miniport driver. After that, NDIS sends expected MediaSpecificWakeUpEvents values in OID_PM_PARAMETER to the miniport driver. 

↑ Back to the top

Keywords: kbtshoot, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2926064
Revision : 1
Created on : 1/7/2017
Published on : 2/11/2014
Exists online : False
Views : 276