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-07-11T15:47:12+00:00

Here is something new that happened today. I could not join my company's employee network without BSOD. I could connect to the Guest wireless with zero issue. Any time I would click on it, it looked like it was going to work but then BSOD. However, just now, I went into Desktop mode and connected to our employee network. It worked fine. It occurred to me that all of the times I had a BSOD was in the modern interface (metro/tiles) mode.

For me I think it happens 90% of the time on the Start Screen as soon as I sign in. My tablet is configured with a policy that sets up the wireless network automatically. But there is definitely something wrong here when it searches for networks.
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-11T15:38:28+00:00

Here is something new that happened today. I could not join my company's employee network without BSOD. I could connect to the Guest wireless with zero issue. Any time I would click on it, it looked like it was going to work but then BSOD. However, just now, I went into Desktop mode and connected to our employee network. It worked fine. It occurred to me that all of the times I had a BSOD was in the modern interface (metro/tiles) mode.
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-11T00:46:24+00:00

No you're probably right it should be unchecked except I had a group policy that had it set to enable. So I removed that this morning and I worked four straight hours today without one BSOD. I put it through a heavy workload and I wasn't in a fixed room either. That is by far the longest I have gone without one at work.

My theory behind that setting is that while connected to our work network which uses WPA2- Enterprise it would scan for other networks. These other networks use WPA2-Personal and a few that are public are open. I think while connected to a WPA2-Enterprise network the driver bugs out when searching for these other networks. I came to this conclusion based on my experience with a Surface Pro 3 that came right out of the box. During OOBE is crashed when it searched for networks. So I saw that setting and thought it might help.

Tomorrow I will reinstall Symantec Endpoint and try that out. If I get no BSOD by mid day Monday. I will deploy an image to our other Surface Pro 3 and take it from there.

This a very interesting information. Please keep us updated here.
Was this answer helpful?

0 comments No comments