What's new

Surface Book will not automatically connect to Wifi after resuming from Hibernation

brosenz

Member
I will have a Yellow Triangle together with the Wifi icon on the taskbar, it will say "No Internet, Secured", If I check properties there will be an IP assigned by the DHCP server. If I check network properties it will say "Unidentified Network, Public Network" and I am at home on a private network. The only way to fix it is to Disable/Enable the Network Adapter, some times after 3-5 min it will self recover and will connect. If I turn OFF/ON the Wifi icon on Action Center nothing happens, problem remains.


Even if I try to manually connect to it it will fail, the only way to fix it is to turn OFF and ON Wifi and then it will reconnect. I do not have any problem when resuming from Sleep, is there a way to fix this problem?


I did remove it but now it appears in Device Manager as an Ethernet Controller instead of Marvell AVASTAR Wireless-AC Network Controller, is there a way to fix this?

Last night I had a crash (reboot) due to NDIS driver, also Network Related, I re-installed the driver today though
 
Last edited:
OP
B

brosenz

Member
I did a Debug of the Dump file from the last Shutdown I had last night and the issue seems to be with the NDIS driver :

Probably caused by : ndis.sys ( ndis!KWaitEventBase::Wait+22 )

Here is the output from WinDbg:

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff802`dec8b000 PsLoadedModuleList = 0xfffff802`def90060
Debug session time: Mon Jan 2 00:08:52.506 2017 (UTC - 6:00)
System Uptime: 0 days 2:02:25.317
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe382903d8740, fffff802e0bd28e0, ffffe382a02eb010}

CompressedPageDataReader warning: failed to get _SM_PAGE_KEY symbol.
CompressedPageDataReader warning: failed to get _SM_PAGE_KEY symbol.
Implicit thread is now ffffe382`88482040
Page f00 not present in the dump file. Type ".hh dbgerr004" for details
Page f00 not present in the dump file. Type ".hh dbgerr004" for details
Page f00 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ndis.sys ( ndis!KWaitEventBase::Wait+22 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe382903d8740, Physical Device Object of the stack
Arg3: fffff802e0bd28e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe382a02eb010, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffe382`88482040
Page f00 not present in the dump file. Type ".hh dbgerr004" for details
Page f00 not present in the dump file. Type ".hh dbgerr004" for details
Page f00 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.576.amd64fre.rs1_release_inmarket.161208-2252

SYSTEM_MANUFACTURER: Microsoft Corporation

SYSTEM_PRODUCT_NAME: Surface Book

SYSTEM_SKU: Surface_Book

SYSTEM_VERSION: D:0B:14F:1C:03P:38

BIOS_VENDOR: Microsoft Corporation

BIOS_VERSION: 90.1380.768

BIOS_DATE: 11/04/2016

BASEBOARD_MANUFACTURER: Microsoft Corporation

BASEBOARD_PRODUCT: Surface Book

DUMP_TYPE: 1

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe382903d8740

BUGCHECK_P3: fffff802e0bd28e0

BUGCHECK_P4: ffffe382a02eb010

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: 88482040

CPU_COUNT: 4

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: SURFACE

ANALYSIS_SESSION_TIME: 01-02-2017 09:22:29.0155

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff802decf0f5c to fffff802dedda506

STACK_TEXT:
ffffcd00`bdef0480 fffff802`decf0f5c : fffff802`defcd180 fffff802`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffcd00`bdef05c0 fffff802`decf09ff : ffffe382`a02e9680 ffff4be7`bbd68885 00000000`00000000 fffff802`dece09d1 : nt!KiSwapThread+0x17c
ffffcd00`bdef0670 fffff802`decf27c7 : ffffe382`00000000 fffff802`be71610d ffffe382`a02e9680 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffcd00`bdef0710 fffff802`be79de6e : ffffe382`8d5ee618 fffff802`00000000 ffffcd00`bdef0800 00000000`00000000 : nt!KeWaitForSingleObject+0x377
ffffcd00`bdef07c0 fffff802`be7a56df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!KWaitEventBase::Wait+0x22
ffffcd00`bdef0800 fffff802`be79d808 : ffffe382`8d5ed1a0 ffffe382`8d5ed1a0 ffffe382`a02eb680 fffff802`be7778f8 : ndis!Ndis::BindEngine::ApplyBindChanges+0x5f
ffffcd00`bdef0850 fffff802`be711450 : ffffe382`8a3b78e0 ffffe382`8d5ed1a0 ffffe382`a02eb010 00000000`00000003 : ndis!ndisIssueNetEventSetPowerEvent+0x60
ffffcd00`bdef0950 fffff802`be731590 : 00000000`00000800 ffffe382`a02eb010 ffffe382`a02eb010 fffff802`dece09b0 : ndis!ndisPrepForLowPower+0x38
ffffcd00`bdef0a20 fffff802`be79d302 : 00000000`00000000 ffffe382`8d5ed1a0 ffffe382`a02eb680 00000000`00000000 : ndis!ndisSetDevicePower+0x204cc
ffffcd00`bdef0a90 fffff802`be71fc28 : ffffe382`a02eb010 ffffe382`903d8740 ffffe382`a02eb680 fffff802`def8b620 : ndis!ndisSetPower+0x56
ffffcd00`bdef0ac0 fffff802`deda51c2 : ffffe382`88482040 ffffcd00`bdef0b70 fffff802`def8b600 ffffe382`8d5ed050 : ndis!ndisPowerDispatch+0xa8
ffffcd00`bdef0af0 fffff802`dec8d729 : 00000000`00000000 fffff802`deda4fe4 00000000`00000000 00000000`0000004b : nt!PopIrpWorker+0x1de
ffffcd00`bdef0b90 fffff802`deddabb6 : ffffcd00`bdf00180 ffffe382`88482040 fffff802`dec8d6e8 ffffc28d`00000000 : nt!PspSystemThreadStartup+0x41
ffffcd00`bdef0be0 00000000`00000000 : ffffcd00`bdef1000 ffffcd00`bdeea000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .thread 0xffffe38288482040 ; kb

THREAD_SHA1_HASH_MOD_FUNC: 3816aecaf706bb13db2af94abf3442783a78ddec

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7c88fb659d7ca57c42bd9625762c96156940327c

THREAD_SHA1_HASH_MOD: 2e7463c4a06613ca32bf00f4fe630ce53f51e143

FOLLOWUP_IP:
ndis!KWaitEventBase::Wait+22
fffff802`be79de6e 4883c438 add rsp,38h

FAULT_INSTR_CODE: 38c48348

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ndis!KWaitEventBase::Wait+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 57f4c58d

BUCKET_ID_FUNC_OFFSET: 22

FAILURE_BUCKET_ID: 0x9F_3_ndis!KWaitEventBase::Wait

BUCKET_ID: 0x9F_3_ndis!KWaitEventBase::Wait

PRIMARY_PROBLEM_CLASS: 0x9F_3_ndis!KWaitEventBase::Wait

TARGET_TIME: 2017-01-02T06:08:52.000Z

OSBUILD: 14393

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-12-09 03:23:02

BUILDDATESTAMP_STR: 161208-2252

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252

ANALYSIS_SESSION_ELAPSED_TIME: 634

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_ndis!kwaiteventbase::wait

FAILURE_ID_HASH: {37b67c78-0c57-7222-0ec7-71f6203e422c}

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

jnjroach

Administrator
Staff member
Assuming you are fully updated, a couple things to investigate:

When did it start? After an update or new software install? If you roll back does it fix it?

Are you using 3rd Party Security Software? Does it include Network or Firewall Protection? If you disable it does It fix it?

Uninstalling the driver for the Marvell WLAN Adapter and reinstalling dies that fix it?
 
OP
B

brosenz

Member
Yes, fully updated.

Started 2-3 days ago, no relevant event.

No third-party AV software.

I did remove it but now it appears in Device Manager as an Ethernet Controller instead of Marvell AVASTAR Wireless-AC Network Controller, is there a way to fix this?

Last night I had a crash (reboot) due to NDIS driver, also Network Related, I re-installed the driver today though

I will have a Yellow Triangle together with the Wifi icon on the taskbar, it will say "No Internet, Secured", If I check properties there will be an IP assigned by the DHCP server. If I check network properties it will say "Unidentified Network, Public Network" and I am at home on a private network. The only way to fix it is to Disable/Enable the Network Adapter, some times after 3-5 min it will self recover and will connect. If I turn OFF/ON the Wifi icon on Action Center nothing happens, problem remains.
 
Last edited:

jnjroach

Administrator
Staff member
It sounds like you're getting a generic drive, download the .ms driver package and remove it from Device Manager and Uninstall the driver (its a checkbox)
 

Members online

Top