[SOLVED] BSOD Windows 8.1 x64

B

botinko

New member
Joined
Dec 2, 2014
Posts
4
· OS - Windows 8.1, 8, 7, Vista ?
Windows 8.1
· x86 (32-bit) or x64 ?
x64
· What was original installed OS on system?
Windows 8.1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Retail (Corporative)
· Age of system (hardware)
> 5 years SSD, HDD, Videocard, ram, power supply. < 6 month motherboard and cpu
· Age of OS installation - have you re-installed the OS?
< 6 month
· CPU
Intel Core i7-4820K
· Video Card
GeForce 8600 GT
· MotherBoard
P9X79
· Power Supply - brand & wattage (if laptop, skip this one)
Ascot A-460 (Ver 2.3)
· System Manufacturer
None
· Exact model number (if laptop, check label on bottom)
None
· Laptop or Desktop?
Desctop

After upgrade motherboard and CPU computer started getting BSOD. It occures usually on power off and awake from sleep. Please, help.
 

Attachments

Please disable Driver Verifier for now; open a Command Prompt and type the following command:

Code: 
verifier /reset
 
I need to install the new WinDbg version (my current version is 8.0) which is 8.1, and contains some libraries needed to debug 8.1 bugchecks.
 
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: 
[COLOR=#ff0000]BugCheck C4[/COLOR], {[COLOR=#0000cd]91001[/COLOR], fffff8013f28ee40, [COLOR=#008000]ffffe001462fb090[/COLOR], [COLOR=#ff8c00]ffffe001462fb118[/COLOR]}

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> [COLOR=#008000]!ruleinfo 91001 ffffe001462fb090 ffffe001462fb118[/COLOR]

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> [COLOR=#008000]!oid[/COLOR]


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> [COLOR=#008000]lmvm e1c64x64
[/COLOR]
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:        [COLOR=#ff0000]Thu Jun 20 22:59:00 2013[/COLOR] (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> [COLOR=#008000]!procdumpext.da fffff8013f28ee40[/COLOR]
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> [COLOR=#008000]!da fffff8013f28ee40[/COLOR]
This OID should only be completed with NDIS_STATUS_NOT_ACCEPTED, NDIS_STATUS_REQUEST_ABORTED, NDIS_STATUS_SUCCESS, or NDIS_STATUS_PENDING.




[TD="class: small"][/TD]
 
I uninstall e1c64x64.sys and other NDIS drivers in safe mode. It looks like it has helped! At least no BSOD when reboot. Thank you!
 
For anyone reading this thread, the ndiskd.dll debugging extension library is great for debugging NDIS related issues.
 
I've used it to track netbuffers when they've violated a rule. You have to use the .load ndiskd.dll file in Windbg, then run the ndiskd command to bring up different options.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top