Bugcode ndis driver windows 8.1 update drivers#
Bugcode ndis driver windows 8.1 update code#

NDIS_BUGCHECK_INIT_FAILED_WITHOUT_CANCEL_TIMERĪ miniport driver failed its initialization without successfully canceling all its timers. NDIS_BUGCHECK_INIT_FAILED_WITHOUT_INTERRUPT_DEREGISTERĪ miniport driver failed its initialization without deregistering its interrupt. The reference count for the miniport driver The address of the miniport driver's timer queue (NDIS_MINIPORT_TIMER)Ī miniport driver is getting unloaded prematurely. The address of the NDIS_MINIPORT_INTERRUPTĪ miniport driver stopped without successfully canceling all its timers. NDIS_BUGCHECK_HALT_WITHOUT_INTERRUPT_DEREGISTERĪ miniport driver did not deregister its interrupt during the halt process. NDIS_BUGCHECK_RECVD_PACKET_IN_USE_BAD_REF_COUNTĬaught by checking packet reference count.Īn FDDI driver indicated that it received a packet by using a packet descriptor that was currently in use by the protocol stack. The address of the packet array that contained this packet descriptor Run !ndiskd.pkt with this address for more information. The address of the packet descriptor used by the driver. NDIS_BUGCHECK_RECVD_PACKET_IN_USE_BAD_STACK_LOCATIONĪn Ethernet driver indicated that it received a packet using a packet descriptor that was currently in use by the protocol stack.Ĭaught by checking stack packet location.

Bugcode ndis driver windows 8.1 update drivers#

NDIS_BUGCHECK_UNLOAD_DRIVER_INVALID_PARAMETERĪddDevice was called with a driver that is not on the list of drivers that are registered with NDIS.Įnabled only on special instrumented NDIS. The page from which this shared memory was allocated The address of a NDIS_WRAPPER_CONTEXTE that keeps track of shared memory allocations by the driverĪ miniport driver called NdisMFreeSharedMemory ( Async) with a shared memory address that had already been freed. The shared memory page that was corrupted The length of the requested shared memoryĭuring a call to NdisMAllocateSharedMemory, NDIS detected that a previously-allocated shared memory page had been corrupted. Run !adapter with this address for more information. The address of the specific miniport adapter block. NDIS_BUGCHECK_ALLOCATE_SHARED_MEM_HIGH_IRQLĪ driver called NdisMAllocateSharedMemory at a raised IRQL.

If a Parameter's value is '0,' that means it is not used. The meaning of the other parameters depends on the value of Parameter 1. Parameter 1 indicates the type of violation.

Bugcode ndis driver windows 8.1 update code#

If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors. For more information, see Using the !analyze Extension.This topic is for programmers. This is most likely a bug or memory corruption that eventually manifests itself as a bad pointer.Īnother common issue is Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE.įirst step with all bug checks is to locate a good dump file, load it in the Windows debugger and use the !analyze command. For a complete list of its parameters, see Bug Check 0x7C.Ī common NDIS misbehavior related bug check is Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL which can be caused by the driver code itself. There is also a NDIS-specific bug check code, bug check 0x7C (BUGCODE_NDIS_DRIVER). The NDIS team blog archives are available at The NDIS blog. NDIS Debugging ResourcesĮpisode 175 of the Defrag Tools show covers NDIS debugging - Defrag Tools #175 - Debugging the Network Stack. For more information, see Rules for NDIS Drivers and Static Driver Verifier. Driver VerifierĪnother useful tool for testing an NDIS driver is NDIS Verifier. For general information about getting started with the WinDbg, see Getting started with Windows Debugging. This information can be useful for debugging hangs and stalls. For example, entering !stacks 2 ndis! displays all threads in the stack beginning with ndis!. 1: kd> !adapterįfffdf8015a98380 ffffdf8015aa11a0 Microsoft ISATAP Adapter #2įfffdf801418d650 ffffdf80140c71a0 Microsoft Kernel Debug Network AdapterĪn additional tool for debugging a network driver is the collection of regular debugging extensions, which are useful for obtaining debugging information. Then the adapter kernel debugger command is a good place to start to investigate the current set of the drivers. Use the report command to generate a visual report showing the current adapters and protocols. For more information on the NDIS debugging extensions, see NDIS Extensions, which provides a complete list of the extension commands found in the extension module Ndiskd.dll. For more information on debug tracing, see Enabling NDIS Debug Tracing. The two primary tools for debugging a network driver are debug tracing and the Network Driver Interface Specification (NDIS) extensions.