The BUGCODE_NDIS_DRIVER_LIVE_DUMP bug code has a value of 0x0000015E. This bug code indicates that NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
- Check out our website article: Update Drivers with Driver Updater: In th.
- While windows was installing I got a blue screen and 'BUGCODENDISDriver'. I can't boot into windows. I have an Asus Tuf Gaming plus wifi x570 motherboard with a ryzen 3900x. After the blue screen appears I am given the standard 'the computer restarted unexpectedly.' Message while the Asus TUF logo is in the background.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
I have windows server 2003 and ISA 2000 Installed on it, since four days the server abruptly shows blue screen with a message BUGCODENDISDRIVER and restrarts, please help me in this regard.
Bugcode Ndis Driver Windows 10
BUGCODE_NDIS_DRIVER Parameters
Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1. If a Parameter's value is '0,' that means it is not used.
Parameter 1 | Parameter 1 Value and Cause of Error | Parameter 2 | Parameter 3 | Parameter 4 |
---|---|---|---|---|
0x01 | NDIS_BUGCHECK_MINIPORT_FATAL_ERROR A miniport driver has encountered a fatal error and requested re-enumeration. | The address of the miniport block. Run !ndiskd.minidriver with this address for more information. | The address of the miniport's Physical Device Object (PDO) | The fatal error that caused this live dump to be taken. Possible values:
|
0x25 | NDIS_BUGCHECK_WATCHDOG An attempt to manage the network stack has taken too long. When NDIS calls out into other drivers, NDIS starts a watchdog timer to ensure the call completes promptly. If the call takes too long, NDIS injects a bugcheck. This can be caused by a simple deadlock. Look with '!stacks 2 ndis' or similar to see if any threads look suspicious. Pay special attention to the PrimaryThread from the NDIS_WATCHDOG_TRIAGE_BLOCK. This can be caused by lost NBLs, in which case !ndiskd.pendingnbls may help. Check for OIDs that are stuck using !ndiskd.oid. | The operation that took too long. Possible values:
| Cast to ndis!NDIS_WATCHDOG_TRIAGE_BLOCK. Useful fields:
| The value of Parameter 4 depends on the value of Parameter 2. Each number in this list corresponds to the same number in Parameter 2.
|
0x30 | NDIS_BUGCHECK_STUCK_NBL A miniport driver has not returned a NBL back to the stack for some time. | The address of the miniport block. Run !ndiskd.minidriver with this address for more information. | 0 | 0 |
Cause
Bugcode Ndis Driver Blue Screen Windows 10
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause. Parameter 1 indicates the specific cause of the BUGCODE_NDIS_DRIVER_LIVE_DUMP bugcheck.
Remarks
NDIS has detected and recovered from a serious problem in another network driver. Although the system was not halted, this problem may later cause connectivity problems or a fatal bugcheck.
This bug code occurs only in Windows 8.1 and later versions of Windows.