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-09-30T09:11:43+00:00
Ruud,

Thanks for suggestion. Yes, I should be all up-to-date when it comes to drivers and updates. I just find it so hard to bring myself to reset everything back to factory settings after wasting two full work days setting up my system and development environment.

However, I think found a workaround that seems to work for me:
1. Download "Surface Pro - September 2014.zip" drivers pack from http://www.microsoft.com/en-us/download/details.aspx?id=38826
2. Extract "Surface Pro - September 2014.zip" somewhere.
3. 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.
4. In Device Manager, right-click "Network adapters" and scan for hardware changes. You should now see an item "Unknown device" (or something similar)
5. Right-Click the "Unknown Device", and install the driver from "Surface Pro - September 2014\Marvell\wlan"
Done.

My system still can't find the network when it wakes up (I must manually turn the Wifi off and back on in order to reconnect), but at least I no longer get the BSOD (wificlass.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED), which is a HUGE plus. I can live with this for the time being, until MS finally provides us with drivers that actually work.

I hope this helps :)
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-30T03:54:04+00:00

I am not going to nuke the machine and start over. Sooner or later Microsoft will fix this problem Surface Pro 3 i7 crashes with wificlass.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. If MartinFL just got his and it is doing it then in effect he started with a clean machine, assuming he ran all the updates. Microsoft blew it bigtime and if they cant fix it then they should not be in the hardware business, which is hard for me to say because I have said they should be in the hardware business for 20+ years. They need new management to replace those currently responsible.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-30T03:41:39+00:00

Hi Martin,

i know how you feel! I had the same issue, what helped for me was to reset the surface to factory settings, perform all updates (bear in mind, you need to install a series of them, but if you install the first set you might have to wait before it finds the other update) and then install stuff like office and so on. Did that 2 weeks ago, it is now running smoothly.

regards,

Ruud
Was this answer helpful?

0 comments No comments