BUGCODE_ID_DRIVER    |    Fix Error Code 0x000000D2    |    Fix Windows Registry Errors


STOP 0x000000D2 : BUGCODE_ID_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 0xD2: BUGCODE_ID_DRIVER

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

Parameters

Before this stop error code occurs, a message is sent to the DbgPrint buffer. If a debugger is connected, this message will be displayed.

This message indicates the type of violation. The meanings of the stop error code parameters depend on this message.

Parameter 1Parameter 2Parameter 3Parameter 4Message and Cause
Address of the miniport blockNumber of bytes requested01Allocating shared memory at raised IRQL. A driver called NdisMAllocateSharedMemory with IRQL >= DISPATCH_LEVEL.
Address of the miniport blockThe Status value submitted to NdisMResetCompleteThe AddressingReset value submitted to NdisMResetComplete0Completing reset when one is not pending. A driver called NdisMResetComplete, but no reset was pending.
Address of the miniport blockMemory page containing address being freedAddress of shared memory signatureVirtual address being freedFreeing shared memory not allocated. A driver called NdisMFreeSharedMemory or NdisMFreeSharedMemoryAsync with an address that is not located in NDIS shared memory.
Address of the miniport blockAddress of the packet that is incorrectly included in the packet arrayAddress of the packet arrayNumber of packets in the arrayIndicating packet not owned by it. The miniport's packet array is corrupt.
Address of the MiniBlockAddress of the driver object00NdisAddDevice: AddDevice called with a MiniBlock that is not on the NdisMiniDriverList.
Address of the MiniBlockThe MiniBlock's reference count00NdisMUnload: MiniBlock is getting unloaded but it is still on NdisMiniDriverList.
Address of the miniport blockMemory pageWrapper contextAddress of shared memory signatureOverwrote past allocated shared memory. The address being written to is not located in NDIS shared memory.

In the following instances of this stop error code, the meaning of the parameters depends on the message and on the value of Parameter 4.

Parameter 1Parameter 2Parameter 3Parameter 4Message and Cause
Address of the miniport blockAddress of the miniport interruptAddress of the miniport timer queue1Unloading without deregistering interrupt. A miniport driver failed its initialization without deregistering its interrupt.
Address of the miniport blockAddress of the miniport timer queueAddress of the miniport interrupt2Unloading without deregistering interrupt. A miniport driver did not deregister its interrupt during the halt process.
Address of the miniport blockAddress of the miniport interruptAddress of the miniport timer queue1Unloading without deregistering timer. A miniport driver failed its initialization without successfully canceling all its timers.
Address of the miniport blockAddress of the miniport timer queueAddress of the miniport interrupt2Unloading without deregistering timer. A miniport driver halted without successfully canceling all its timers.

Comments

This stop error code code only occurs on Windows 2000 and Windows XP. In Windows Server 2003 and later, the corresponding code is stop error code 0x7C (BUGCODE_NDIS_DRIVER).

On the checked build of Windows, only the Allocating Shared Memory at Raised IRQL and Completing Reset When One is Not Pending instances of this stop error code can occur. All the other instances of stop error code 0xD2 are replaced with ASSERTs.

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

Repair Windows Error 0x000000D2    |    STOP 0x000000D2    |    BUGCODE_ID_DRIVER