Surface Pro 3 Blue Screen due to Wifi?

Anonymous

You guys are lucky. The marvell network adapter is causing a BSOD for me. I linked some of my memory dumps for MS or anyone interested.

MiniDump

https://onedrive.live.com/redir?resid=63F5D6A6AB9AA87E!32762&authkey=!ADC7RkR1Ol-EjYU&ithint=file%2c.dmp

Full Memory Dump

https://onedrive.live.com/redir?resid=63F5D6A6AB9AA87E!32763&authkey=!AOpLL7cw2JTzqk4&ithint=file%2c.DMP

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 8 Kernel Version 9600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035

Machine Name:

Kernel base = 0xfffff8039b818000 PsLoadedModuleList = 0xfffff8039bae22d0

Debug session time: Fri Jun 27 12:21:18.597 2014 (UTC - 4:00)

System Uptime: 0 days 0:02:39.786

Loading Kernel Symbols

...............................................................

................................................................

.......................................................

Loading User Symbols

Loading unloaded module list

..........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd00098def340, ffffd00098def298, 0}

*** ERROR: Module load completed but symbols could not be loaded for mrvlpcie8897.sys

*** ERROR: Module load completed but symbols could not be loaded for wificlass.sys

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : mrvlpcie8897.sys ( mrvlpcie8897+18cdb )

Followup: MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Confirmed by Microsoft:

Solution Task || v-2sack || 08-Dec-2014 12/08/2014 11:12

Symptom:

Machine (Surface Pro 3) running with "Windows 8.1 Pro" crashes with the bugcheck "0x0000000a (0xfffff6f000cf5000, 0x0000000000000002, 0x0000000000000000, 0xfffff800bc365f66)" after you connected it to the employee network called "XXX" using CISCO wireless network and it crashed only if the feature Flexconnect (CISCO WIRELESS) was enabled.

Cause:

Cisco wireless Access Points was outdated.

Resolution:

Cisco updated the wireless Access Points to a new version of code which resolved the issue completely.

0 comments

Answer accepted by question author

Anonymous

Well after a couple weeks working with Microsoft Commercial Technical Support a situation arose that resolved this issue. Apparently our Cisco support vendor was having the same complaint at another of their customer's site. There was a firmware update for the Cisco 1142 access points. To be specific the version is 7.6.130.0. We applied this update to all of our APs and this fixed the BSOD on all of the Surface Pro 3 devices.

0 comments

155 additional answers

Anonymous

2014-11-13T18:55:37+00:00

I've been following this thread for a couple of months and I just want to keep it alive.

My SP3 BSOD's whenever connecting to the guest wireless at work and has since I got it. This appears to be related with the Marvell wireless driver and the Cisco AP previously mentioned in this thread.

Hope this gets some attention from Microsoft support.

Out of curiosity, does it not happen when you join to the corporate wireless? I've been doing a lot of testing lately and today seemed to have everything working ok on a newly imaged test machine with all of October's latest updates and testing on the guest network. When I joined it to our domain and connected to corporate network, nothing but bluescreens. We use Cisco APs as well.

Hi Toddo97,

I believe this has to do with some very specific configuration of the Cisco AP's. Back on Page 7 of this thread someone responded indicating that they fixed it with a back end change to Certificate Authentication in the Cisco AP configuration. I haven't seen any further comment from that user regarding the specific change... too bad.

To answer your question, I can't test connecting to the corporate network as my scenario is using a personal device at work. We don't have SP3's deployed to company users yet. I've also confirmed that others at the company with personal SP3's have the same problem.

I have, however, tested my personal device to the Guest Wireless at other company sites and confirmed that I can connect at some but not all. Unfortunately since this is a personal device issue our network admins aren't willing to go through a full troubleshooting process with me. Oh well... I now use the USB Wifi suggested by Barb Bowman.
Was this answer helpful?

0 comments No comments
Anonymous

2014-11-12T13:23:04+00:00
Download "Surface Pro - September 2014.zip" drivers pack from http://www.microsoft.com/en-us/download/details.aspx?id=38826

Extract "Surface Pro - September 2014.zip" somewhere.

Open Device Manager, uninstall "Marvell AVASTAR Wireless AC Network Controller", until it is completely gone and let it remove whatever Wifi drivers are currently installed.

In Device Manager, right-click "Network adapters" and scan for hardware changes. You should now see an item "Unknown device" (or something similar)

Right-Click the "Unknown Device", and install the driver from "Surface Pro - September 2014\Marvell\wlan"
Thank you very much! Although I had a different BSOD I have no bluescreen now for about 1 week. In the event log still the Wifi Adapter causes some errors but i don't care too much about this as far as it works!

For me "September 2014" was not the newest one, so i took the "October 2014" driver pack.

Hope, it will help you as well!
Was this answer helpful?

0 comments No comments
Anonymous

2014-11-12T12:37:32+00:00

Did the newest rounds of updates do it for anybody?

For me the following happened:

Installed today's updates, a whole bunch of 'em.

After reboot, the wireless connection is gone completely. Looking at the Device Manager, it says that the device (network adapter) is disabled because Windows determined there's a problem with it.

Now it gets interesting, because, well, how are you going to install any further updates? I simply uninstalled the driver and let Windows re-install it.

Now the wireless connection is back on, all working fine.

Another check for Windows updates reveals there's a new hardware update available (pretty small one).

Download, install, restart, all appears to be working fine until the next reboot.

Because after that, it's back to no wireless connection at all, and the network adapter is disabled again.

From this point on I can do it over and over again, re-install network driver, the hardware update becomes available again, install that, after second reboot, back to no wireless connection, just running in circles.

Anyone else getting similar results?
Was this answer helpful?

0 comments No comments