Fix Windows Registry Errors    |    Repair Windows Error 0x0000007C    |    BUGCODE_NDIS_DRIVER


STOP 0x0000007C : BUGCODE_NDIS_DRIVER

STOP Errors are usually the result of a hardware malfunction or device driver issue. It is also possible to receive a Blue Screen Error due to bad system memory, malfunctioning power supply, components overheating, or hardware overclocked beyond its specification. In older versions of the Windows OS you may also receive Blue Screen Errors due to incompatible DLL files.

Since the only option when receiving a Blue Screen Error is to reboot, any unsaved data is lost. With that in mind, it is very important to eliminate these errors to protect your data.

Basic Troubleshooting

Troubleshooting STOP Errors can be a difficult and time consuming process. Try these basic steps to fix your own Blue Scree Error. We hope it will help you avoid an expensive service call and provide a rewarding experience of solving the problem on your own.

Advanced Troubleshooting

The following details are for advanced users. These are provided for your convenience and may help those with advanced knowledge discover the root cause of their STOP Error.


Stop 0x7C: BUGCODE_NDIS_DRIVER

The BUGCODE_NDIS_DRIVER stop error code has a value of 0x0000007C. This stop error code indicates that a problem occurred with an NDIS driver.

Parameters

The following parameters appear on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.

Parameter 1Parameter 2Parameter 3Parameter 4Cause of Error
0x01The address of the miniport blockThe number of bytes that are requestedThe current IRQLA driver called NdisMAllocateSharedMemory at a raised IRQL.
0x02The address of the miniport blockThe shared memory page that was corruptedThe address of NDIS_WRAPPER_CONTEXT that keeps track of the driver's shared memory allocationsDuring a call to NdisMAllocateSharedMemory, NDIS detected that a previously-allocated shared memory page had been corrupted.
0x03The address of the miniport blockThe page that contains the shared memoryThe virtual address of the shared memoryA driver called NdisMFreeSharedMemory[Async] with a shared memory pointer that had already been freed.
0x04The address of NDIS_M_DRIVER_BLOCKThe address of DRIVER_OBJECT0AddDevice was called with a driver that is not on the list of drivers that are registered with NDIS.

(Enabled only on special instrumented NDIS.)

0x05
0x06
The address of the miniport blockThe address of the packet descriptor that the driver usesThe address of the packet array that contained this packet descriptor An Ethernet driver indicated that it received a packet by using a packet descriptor that the protocol stack is currently using.
0x07The address of the miniport blockThe address of the packet descriptor that the driver usesThe address of the packet array that contained this packet descriptor An FDDI driver indicated that it received a packet by using a packet descriptor that the protocol stack is currently using.
0x08The address of the miniport blockThe address of NDIS_MINIPORT_INTERRUPT0A miniport driver did not deregister its interrupt during the halt process.
0x09The address of the miniport blockThe address of the miniport driver's timer queue (NDIS_MINIPORT_TIMER)0A miniport driver stopped without successfully canceling all its timers.
0x0AThe address of NDIS_M_DRIVER_BLOCKThe address of DRIVER_OBJECTThe reference count for the miniport driverA miniport driver is getting unloaded prematurely.
0x0BThe address of the miniport blockThe address of NDIS_MINIPORT_INTERRUPT0A miniport driver failed its initialization without deregistering its interrupt.
0x0CThe address of the miniport blockThe address of the miniport driver's timer queue (NDIS_MINIPORT_TIMER)0A miniport driver failed its initialization without successfully canceling all its timers.
0x0DThe address of the miniport blockThe address of NDIS_MINIPORT_INTERRUPT0A miniport driver did not deregister its interrupt during the halt process. (The halt was called from the initialize routine after the miniport driver returned success from its initialize handler.)
0x0EThe address of the miniport blockThe address of the miniport driver's timer queue (NDIS_MINIPORT_TIMER)0A miniport driver stopped without successfully canceling all its timers. (The halt was called from the initialize routine after the miniport driver returned success from its initialize handler.)
0x0FThe address of the miniport blockThe reset statusAddressingReset (BOOLEAN) A miniport driver called NdisMResetComplete without any pending reset request.
0x10The address of the miniport blockThe address of NDIS_MINIPORT_INTERRUPT0After resuming from a low-power state, a miniport driver failed its initialization without deregistering its interrupt.
0x11The address of the miniport blockThe address of the miniport driver's timer queue (NDIS_MINIPORT_TIMER)0After resuming from a low-power state, a miniport driver failed its initialization without successfully canceling all its timers.
0x12The address of the miniport blockThe address of the packet descriptor that the driver usesThe address of the packet array that contained this packet descriptor A miniport driver indicated that it received a packet by using a packet descriptor that the protocol stack is currently using.
0x13The address of the miniport blockThe address of the packet descriptor that the driver usesThe address of the packet array that contained this packet descriptor A Token-Ring miniport driver indicated that it received a packet by using a packet descriptor that the protocol stack currently uses.
0x14The current IRQL value00An NDIS driver called NdisWaitEvent at IRQL > PASSIVE_LEVEL. The function must be called at IRQL = PASSIVE_LEVEL.
0x15The address of the miniport block00An NDIS 6 miniport driver was calling an NDIS 5 API. An NDIS 6 miniport driver cannot call NdisMQueryInformationComplete or NdisMSetInformationComplete.
0x16The address of the protocol blockThe address of the context area that is allocated by the protocol driverThe address of the open block NDIS encountered an invalid handle in a binding operation.

A protocol driver’s ProtocolBindAdapterEx function returned NDIS_STATUS_SUCCESS, either directly or asynchronously through NdisCompleteBindAdapterEx. However, the binding context information contains an invalid handle to a block that indicates the open state of the miniport adapter. In this case, the open handle is not NULL, but it cannot be referenced.



0x17The address of the interface provider block00The NDIS driver was attempting to deregister as a network interface provider while an interface was still registered.

Cause

Parameter 1 indicates the specific cause of the BUGCODE_NDIS_DRIVER stop error code.

If one of the stop error code parameters specifies the address of the miniport block, you can obtain more information by using the !ndiskd.miniport debugger extension together with this address.

If one of the stop error code parameters specifies the address of the packet descriptor that the driver uses, you can obtain more information by using the !ndiskd.pkt debugger extension together with this address.

Comments

This stop error code code occurs only on Microsoft Windows Server 2003 and later versions of Windows. In Windows 2000 and Windows XP, the corresponding code is stop error code 0xD2 (BUGCODE_ID_DRIVER).

Helpful Tools

The following products are free to try. We have found them to be of the highest quality and value. They have been extremely useful in our own pc troubleshooting and maintainance and we highly recommend trying them out for yourself.


Anti-Malware Pro

With a lightning fast free scan and the largest authentic spyware detection database we have seen, Anti-Malware Pro finds and removes threats to your PC stability and security. Download Anti-Malware Pro


DriverFinder

DriverFinder will scan your system for driver and software updates. Its easy to use interface makes keeping your drivers updated quick and simple. They will even send you an email notification when new driver updates are available for your system! It doesn't get any more convenient than this. Download DriverFinder





Browse STOP Error Codes:





Is a STOP error code missing?

Help us to make errorDecoder.com the best resource we possibly can by submitting you very own STOP error code details. If you have detailed information on any STOP error code please let us know by visiting the following link.

Submit Error Details Form

BUGCODE_NDIS_DRIVER    |    Fix Error Code 0x0000007C    |    Repair Windows Error 0x0000007C