#Windows 8.1 bugcode ndis driver drivers
#Windows 8.1 bugcode ndis driver driver
#Windows 8.1 bugcode ndis driver software
#Windows 8.1 bugcode ndis driver code

Wi-Fi Protected Access (WPA) in Windows XP SP1.

Offloading the Processing of UDP-Encapsulated ESP Packets (Windows Server 2003 only).

#Windows 8.1 bugcode ndis driver drivers

Packet stacking for intermediate drivers.

Scatter/gather support for both serialized and deserialized miniport drivers.

See Download kits for Windows hardware development

Scatter/gather DMA support for deserialized miniport drivers.

New INF file format compatible with Windows 95/98/Me.

Windows NT DDK with updated NDIS header and library Windows NT 4.0 DDK or Windows 98 DDK for Vxds Operating systemĪdded support for miniport drivers and Plug and Play.Īdded support for Power Management and WMI.

#Windows 8.1 bugcode ndis driver driver

Windows operating system, Microsoft Windows Driver Kit (WDK), and Driver Development Kit (DDK) version support for NDIS versions, as well as support for major NDIS features across NDIS versions, are described in the following table.

See any reference to this in the miniport adapter states diagram.A driver can query the NDIS version by calling the NdisReadConfiguration function with the Keyword parameter set to NdisVersion. or it will cease the interaction with the miniport until the actual reset trigger? I don't

So what happens in the window between the reset request by the driver and the actual reset trigger? Will the OS continue behaving as usual, sending OIDs, traffic etc.

#Windows 8.1 bugcode ndis driver software

No amount of hardware brokenness is a valid excuse for a driver that leaks software resources or becomes nonresponsive. Resetting the hardware doesn't work, then If your hardware is broken, then reset the hardware and get back into a working state. That is to say, you should always be able to clean up the software-side resources, even if your hardware is broken. If you fail the OID because you encounter a failure while talking to your hardware, you should mark the hardware as failed, request a reset, clean up software-side resources, and succeed the OID. We reserve the right to add the bugcheck for other cleanup-style OIDs, if we see them being a problem in the future. In OS versions up to Windows 8.1, this bugcheck happens to be implemented only for OID_RECEIVE_FILTER_CLEAR_FILTER. OS, potentially causing an inconsistent driver state with respect to the OS. The alternative is to return successful status to the Forcing a bugcheck prevents the driver from attempting a recovery via reset. This behavior seems a bit odd to me - there can be proprietary reasons for failing oid, besides receiving it when unexpected. So this bugcheck will occur for other 'cleanup' oids as well, such as OID_DOT11_DELETE_MAC?

NDIS won't bugcheck if you fail any allocation-type OID, like OID_RECEIVE_FILTER_SET_FILTER, since we understand that memory allocation or device I/O can always fail. Where failing the OID means something got leaked. It's only used in 'cleanup' type OIDs, like OID_RECEIVE_FILTER_CLEAR_FILTER, The 7c/1c bugcheck is not about enforcing that receive filtering works correctly the bugcheck is there to prevent leaks. None of those other OID requests will trigger the 7c/1c bugcheck.

#Windows 8.1 bugcode ndis driver code

(If you want to write defensive code, you can still have your code return NDIS_STATUS_INVALID_PARAMETER in those cases, but that's essentially dead Therefore, you won't hit the case where you need to fail an OID_RECEIVE_FILTER_CLEAR_FILTER request. That means that your miniport will only see OID_RECEIVE_FILTER_CLEAR_FILTER if the miniport had previously succeeded an OID_RECEIVE_FILTER_SET_FILTER request. NDIS won't allow an invalid OID_RECEIVE_FILTER_CLEAR_FILTER to reach your miniport.