BSOD after network sharing via Virtual Miniport Adapter, 0x0000009f

Ice · 08 Feb 2014

Hi everyone!

I have encountered the following problem with internet sharing: after using virtual miniport adapter to share my internet connection, when I want to shut down the pc, it won't. Just a BSOD.

When the connection is not shared, it works fine, no BSOD. But I need to share my connection to my girlfriends tablet.

I am connected to a free hotspot via a TP-Link TL-Wn7200ND ver 1.0 adapter and I have shared this connection using the Microsoft virtual miniport adapter. Everything works fine, till the moment I try to shut down the laptop. The system tries to shut down, but after 6 or 7 minutes it restars itself and get the message that an error occurred.

As requested, I attach the result of the sf diagnostic tool.

Arc · 08 Feb 2014

Hi Ice.

Update the driver to your TP-LINK 150Mbps Wireless Lite N Adapter from Download - Welcome to TP-LINK

Let us know the results.

Ice · 09 Feb 2014

Ok. First I have updated the driver using TL-WN7200ND_V1_130906 but at the end get an error message: 802.11n wlan not installed driver not found. so, now I will update to this:
TL-WN7200ND_100513. Is this ok? When I first installed the adapter got the same message. 802.11n wlan not installed, because driver not found.

Arc · 09 Feb 2014

If you cannot found the appropriate driver, better you get another adapter.

The adapter is old. TP Link never develops their drivers, they collect it from others.
The driver to your device was originally developed by Ralink. Over this time Ralink got sold to MediaTek. So it is all possible that an appropriate update to that device will not be found.

Ice · 10 Feb 2014

let me understand correctly: is it possible that bsod is caused by tp link driver? Microsoft has a hofix for BUG CHECK STRING

RIVER_POWER_STATE_FAILURE for win7. what about that?

Ice · 10 Feb 2014

I mean this one: "0x0000009F" Stop error when you restart a Windows 7-based or Windows Server 2008 R2-based computer that has certain Wi-Fi drivers installed

Ice · 10 Feb 2014

after installing the tp link driver with the mentioned error and tne above mentioned microsoft fix, I started a hosted network. the bsod at shutdown came up again. in attachment is the minidump file. The bsod happends only when I start a hosted network. the first 4 lines of the minidump were highlighted. It is getting me headaches.
so, what now?

Arc · 10 Feb 2014

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Ice · 11 Feb 2014

sorry. my bad. I have had run the sf debug tool. Results in attachments.
As far as I can see from the minidump files, it tis a change in parameters: in the first one: PARAMETER 3:0x84e804c0
PARAMETER 4:0x82d72b24 and on the second one, that occurred yesterday : Parameter 3: 0x84e7fd48
Parameter 4 : 0x82d40b24. The rest is the same.

Arc · 11 Feb 2014

The with such old WiFi driver, the BSOD will continue to occur.

Code:

8260c000 826e3000   netr28u    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\netr28u.sys
    Image name: netr28u.sys
    Timestamp:        Wed May 26 15:51:27 2010 (4BFCF627)
    CheckSum:         000D83C2
    ImageSize:        000D7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you cannot get any update to your driver, get a new network adapter.

No microsoft fixit or anything can do any good in this situation. The logic is simple ... the driver is too old to work.

Till you get a new adapter, disable USB selective suspend.
___________________________________________________________________________________________________

Code:

BugCheck 9F, {4, 258, 84e7fd48, 82d40b24}

Implicit thread is now 84e7fd48
Probably caused by : vwifibus.sys

Followup: MachineOwner
---------