In the middle of any job blue screen appears with a message bugcode ndis driver.
#Bugcode ndis driver windows 8.1 update driver
This bug code occurs only in Windows 8.1 and later versions of Windows.Download Now BUGCODE USB 3 BLUE SCREEN DRIVER Although the system was not halted, this problem may later cause connectivity problems or a fatal bugcheck. NDIS has detected and recovered from a serious problem in another network driver. Parameter 1 indicates the specific cause of the BUGCODE_NDIS_DRIVER_LIVE_DUMP bugcheck. The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause. Use !ndiskd.help to decode it.Ī miniport driver has not returned a NBL back to the stack for some time. 0x24 : The OID code of the stuck request.0x23 : The OID code of the stuck request.0x13 : The NDIS_STATUS code of the stuck indication.For possible values, see the previous list of values for item 2 in this list. 0x12 : The NET_PNP_EVENT_CODE of the stuck event.0x03 : The NDIS_STATUS code of the stuck indication.For more information about these codes, see NET_PNP_EVENT. 0x02 : The NET_PNP_EVENT_CODE of the stuck event.Each number in this list corresponds to the same number in Parameter 2. The value of Parameter 4 depends on the value of Parameter 2. Usually, this is the first place to look, although the thread may have gone elsewhere if the operation is being handled asynchronously. PrimaryThread is the thread on which NDIS initiated the operation.Run !ndiskd.protocol, !ndiskd.filter, or !adapter with this handle for more information. TargetObject is a handle to the protocol, filter module, or miniport adapter that NDIS is waiting on.TimeoutMilliseconds shows how long NDIS waited, at a minimum, before triggering this bugcheck.StartTime shows what time the operation started, in 100ns units, as returned by KeQueryInterruptTime.There was a timeout while canceling an idle request on a miniport adapter.Ĭast to ndis!NDIS_WATCHDOG_TRIAGE_BLOCK. There was a timeout while idling a miniport adapter.Ġx26 : NDIS_BUGCHECK_WATCHDOG_CANCEL_IDLE There was a timeout while delivering an OID request to a filter driver.Ġx25 : NDIS_BUGCHECK_WATCHDOG_MINIPORT_IDLE There was a timeout while delivering an OID request to a miniport adapter. There was a timeout while halting a miniport adapter.Ġx23 : NDIS_BUGCHECK_WATCHDOG_MINIPORT_OID There was a timeout while pausing a miniport adapter.Ġx22 : NDIS_BUGCHECK_WATCHDOG_MINIPORT_HALT There was a timeout while detaching a filter driver.Ġx21 : NDIS_BUGCHECK_WATCHDOG_MINIPORT_PAUSE There was a timeout while delivering a status indication to a filter driver.Ġx14 : NDIS_BUGCHECK_WATCHDOG_FILTER_DETACH There was a timeout while delivering a NET_PNP_EVENT_NOTIFICATION to a filter driver.Ġx13 : NDIS_BUGCHECK_WATCHDOG_FILTER_STATUS_INDICATION
There was a timeout while pausing a filter driver.Ġx12 : NDIS_BUGCHECK_WATCHDOG_FILTER_NETPNPEVENT There was a timeout while unbinding a protocol driver.Ġx11 : NDIS_BUGCHECK_WATCHDOG_FILTER_PAUSE There was a timeout while delivering a status indication to a protocol driver.Ġx04 : NDIS_BUGCHECK_WATCHDOG_PROTOCOL_UNBIND There was a timeout while delivering a NET_PNP_EVENT_NOTIFICATION to a protocol driver.Ġx03 : NDIS_BUGCHECK_WATCHDOG_PROTOCOL_STATUS_INDICATION There was a timeout while pausing a protocol driver.Ġx02 : NDIS_BUGCHECK_WATCHDOG_PROTOCOL_NETPNPEVENT Possible values:Ġx01 : NDIS_BUGCHECK_WATCHDOG_PROTOCOL_PAUSE Check for OIDs that are stuck using !ndiskd.oid. This can be caused by lost NBLs, in which case !ndiskd.pendingnbls may help. Pay special attention to the PrimaryThread from the NDIS_WATCHDOG_TRIAGE_BLOCK. Look with "!stacks 2 ndis" or similar to see if any threads look suspicious. If the call takes too long, NDIS injects a bugcheck. When NDIS calls out into other drivers, NDIS starts a watchdog timer to ensure the call completes promptly.
The address of the miniport's Physical Device Object (PDO) Run !ndiskd.minidriver with this address for more information. Parameter 1Ī miniport driver has encountered a fatal error and requested re-enumeration. 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. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
0 kommentar(er)
