surface 4pro locks up

Surface 4 pro locks up on wifi. Does not lock up when connected via
ethernet. win 10 pro build 1607. There are no corresponding event log
errors to this occurrence. I have tried applying the MS surface tools
dock update, reset win 10 (in settings update and security recovery
reset/keep all files) and a network reset. Still locks up. any
other suggestions?

--

A nation of sheep will beget a government of wolves
- Edward R. Murrow

adminisatyr wrote:
Surface 4 pro locks up on wifi. Does not lock up when connected via
ethernet. win 10 pro build 1607. There are no corresponding event log
errors to this occurrence. I have tried applying the MS surface tools
dock update, reset win 10 (in settings update and security recovery
reset/keep all files) and a network reset. Still locks up. any
other suggestions?


iFixit lists the Wifi chip.

"Marvell Avastar 88W8897 802.11ac, NFC and Bluetooth SoC"

https://www.ifixit.com/Teardown/Micr...Teardown/51568

The SOC is pretty high tech. And this isn't an exclusive
to Microsoft, so that means other computer companies will
be tracking updates for it too. Unfortunately, one of my
leads, led to a Chromebook, so stealing the driver from
that isn't going to work.

http://www.marvell.com/wireless/avastar/88W8897/

Marvell has a driver download page but not for that thing.

*******

Microsoft has a support page for Surface...

https://www.microsoft.com/surface/en...-10&=undefined

Surface 4 Pro drivers

https://www.microsoft.com/en-us/down....aspx?id=49498

Version: 1.0 1/18/2017

SurfacePro4_Win10_1700501_0.msi 237.1 MB

SurfacePro4_Win10_1700501_0.zip 593.6 MB

Wintab_x32_1.0.0.20.zip 4.5 MB

Wintab_x64_1.0.0.20.zip 4.5 MB

The dates on the network files in the ZIP, are no newer than
Feb.2016 (a year old). And the driver format looks like
NDIS drivers, not a full package of some sort.

I don't know how the firmware for a thing like that
is delivered, as the files don't look all that big.

I've only ever had one bad Marvell driver here, which
was a driver for a wired NIC. And they fixed that a
few days later.

The video on the machine, is via the GPU inside the processor,
so it's an Intel driver for that part. Hard to see how using the
Wifi would trigger a video bug, but video is usually one
of the least reliable subsystems on a Windows machine.

And I cannot think of a plan, to debug the problem. Like,
what I/O is reliable enough on the machine, to use for
debugging ? If there is nothing in EventViewer, what
do you do next ?

Paul