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-25T11:34:06+00:00
On Wed, 24 Sep 2014 21:27:30 +0000, SteveJXP wrote:

>>This happens to me on my i7 Surface Pro 3 pretty much daily. I am the joke of one of my clients because they have seen the BSOD SYSTEM_THREAD_NOT_HANDLED wificlass.sys so many times they actually decided not to buy any Surface Pros. And when I come in some people like to watch and see if it will BSOD. When it does they cheer.

>>

>>

>>

>>I am sure sooner or later this issue will be resolved with a firmware fix. It is a nice machine. Until then I just boot up, get the BSOD, shutdown when it says it cant fix my problem, reboot, then it usually works OK. I believe my pc is set to notify Microsoft so hopefully they see it. The limited wifi after sleep seems corrected recently.
1. do you have Hyper-V enabled or did you modify any registry keys to enable
hibernate?
1. Those reports let Microsoft get some data, but who knows how long it takes
them to actually analyze the data.

__________________________________________________________________________________________________

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-26T18:17:36+00:00

I'm also experiencing the BSOD issue at work with the S3. What's strange in my case is that it appears to be localized to just an area of one building. Every other location in the company works as desired, but if you carry the S3 within range of the APs that service that part of the evil building (apparently), they (the two that I've had time to test with) will immediately bluescreen. Turning off wifi allows them to work correctly. These were imaged via SCCM and all the latest drivers from MS were installed as well as all of the latest updates. The Hyper-V 'fix' did not work in my case

I had our network guys look at the APs to see if anything was different. They're all Cisco APs and each gets the same configuration (they checked the two in that location to make sure they were the same as the others) so there's no reason that they could see why the problem would be localized to that one area.
Was this answer helpful?

0 comments No comments
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator

2014-09-26T18:30:55+00:00

On Fri, 26 Sep 2014 18:17:36 +0000, toddo97 wrote:

>>They're all Cisco APs and each gets the same configuration (they checked the two in that location to make sure they were the same as the others) so there's no reason that they could see why the problem would be localized to that one area.

A few other people have reported issues specifically with Cisco AP's. It would

be good to see if there were differences in firmware versions for these AP's, if

they were on the same channel, what model number the hardware was, and of course

triple checking the configs. Even with all of that information available, I

don't know a way to get it to Surface Engineering.

__________________________________________________________________________________________________

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