Okay I've installed the new version, and had to edit the registry to remove from old file associations. The analysis of the bugcheck can be found below:
Code:
BugCheck C4, {91001, fffff8013f28ee40, ffffe001462fb090, ffffe001462fb118}
Probably caused by : wfplwfs.sys ( wfplwfs!LwfLowerOidRequest+6e )
The first parameter, third parameter and fourth parameter are all arguments which can be passed to the
!ruleinfo extension.
Code:
4: kd> !ruleinfo 91001 ffffe001462fb090 ffffe001462fb118
RULE_ID: 0x91001
RULE_NAME: NdisOidComplete
RULE_DESCRIPTION:
This rule verifies if an NDIS miniport driver completes an OID correctly.
Check RULE_STATE for Oid ( use !ndiskd.oid ), which can be one of the following:
1) NULL,
2) Pending OID, or
3) Previous OID if no OID is pending.
MSDN_LINK: http://go.microsoft.com/fwlink/?LinkId=278802
Failed to read the rule state (check the second argument).
Since this is a Minidump, not many of the debugger extensions are going to be available. It seems that the NDIS Miniport driver has failed to complete a NDIS OID Request correctly. The
!oid extension doesn't provide much information for reasons stated before.
Code:
4: kd> !oid
ALL PENDING OIDs
[Next link in list is not readable; aborting the list traversal]
No pending or queued OIDs were found.
To my knowledge, OID is Object Identifier, and the
NdisOidRequest function is used to communicate with other adapters in the system and check their states before completing a certain request. The list of rules for correct operation of NdisOidRequest can be found here -
NdisOidComplete rule (ndis) (Windows Drivers)
I would look at updating Intel(R) Gigabit Adapter NDIS 6.x driver from the Intel Support Page or your motherboard/model support page.
Code:
4: kd> lmvm e1c64x64
start end module name
fffff801`41f4b000 fffff801`41fbf000 e1c64x64 T (no symbols)
Loaded symbol image file: e1c64x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1c64x64.sys
Image name: e1c64x64.sys
Timestamp: Thu Jun 20 22:59:00 2013 (51C37B24)
CheckSum: 00079928
ImageSize: 00074000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
From the raw stack, using
!dpx extension, I was able to find some interesting strings:
Code:
4: kd> !procdumpext.da fffff8013f28ee40
This OID should only be completed with NDIS_STATUS_NOT_ACCEPTED, NDIS_STATUS_REQUEST_ABORTED, NDIS_STATUS_SUCCESS, or NDIS_STATUS_PENDING.
This rules out the possiblity of a OID_PNP_SET_POWER request.
The same string can be found in the second parameter of the bugcheck:
Code:
4: kd> !da fffff8013f28ee40
This OID should only be completed with NDIS_STATUS_NOT_ACCEPTED, NDIS_STATUS_REQUEST_ABORTED, NDIS_STATUS_SUCCESS, or NDIS_STATUS_PENDING.
