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

Barb Bowman 80,805 Reputation points MVP Volunteer Moderator

2014-09-27T11:39:57+00:00

On Fri, 26 Sep 2014 18:45:16 +0000, toddo97 wrote:

>>Some more detailed info about the configuration I got from the senior engineer are that there are 2 Cisco 5508 (500 APs) controllers running 7.4.100.0 code. The department that contains the 'problem APs' are model AP AIR-CAP3502I-A-K9 installed, but there are 11 other identical APs in the department that do not cause the problem.

>>

>>

>>

>>If I end up opening a case with MS, I'll post results here. The network engineer also did some searching for Cisco controller related issues that could cause this, but did not find anything.

there are threads in this forum about enterprise Cisco AP's like:

http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfnetwork/cisco-enterprise-wifi-support-broken-on-surface/37eb2abf-3887-4083-a3e7-ada545270c09

http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfnetwork/cisco-anyconnect-nam-v3105170-troubles-with/edb9966d-761a-4c87-bb37-8b4028ad8882

there's obviously something about the Marvell drivers and Cisco that isn't right

(but considering the scope of issues with the Marvell drivers, who knows if

Surface Engineering is even aware of the issue you have, and the only way to

insure that they become aware is to open a ticket with IT Pro Support or

Premium Support - NOT assisted Surface Support).

__________________________________________________________________________________________________

Barb

Windows Entertainment and Connected Home MVP

My Blog - http://digitalmediaphile.com/

Please mark as answered if this answers your question
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-26T21:51:33+00:00

I had to turn on my Surface Pro 3 to see if I have Hyper-V enabled which I have never heard of. I have not modified any registry keys at all. Once the BSOD came up and it rebooted I searched for Hyper-V, went to Hyper-V manager and no, I have not virtual machines setup. I have Visual Studio, SQL Server but this problem is obviously some glitch in Microsoft hardware/software. WHen I say "Microsoft" I mean anything in the Surface Pro 3 regardless of the actual manufacturer.

I don't get the error near as much as I used to but that is because I don't use the Surface Pro 3 near as much as I used to. I have started using an Asus Vivotab for OneNote note taking at my clients. That way no one sees me have to fumble with reboots to connect to the wireless.
Was this answer helpful?

0 comments No comments
Anonymous

2014-09-26T18:45:16+00:00

Some more detailed info about the configuration I got from the senior engineer are that there are 2 Cisco 5508 (500 APs) controllers running 7.4.100.0 code. The department that contains the 'problem APs' are model AP AIR-CAP3502I-A-K9 installed, but there are 11 other identical APs in the department that do not cause the problem.

If I end up opening a case with MS, I'll post results here. The network engineer also did some searching for Cisco controller related issues that could cause this, but did not find anything.
Was this answer helpful?

0 comments No comments