Surface Pro 3 Blue Screen due to Wifi?

Anonymous
2014-06-30T17:19:17+00:00

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

Copyright (c) Microsoft Corporation. All rights reserved.

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


Surface | Surface Pro | Network

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 No comments
Answer accepted by question author
Anonymous
2014-12-11T00:01:14+00:00

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.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2014-12-09T13:12:54+00:00

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.

Was this answer helpful?

0 comments No comments

155 additional answers

Sort by: Oldest
  1. Anonymous
    2014-10-15T15:35:43+00:00

    Not going to hold my breath, but I saw this today.  I'm not sure how long 'in the coming weeks' means but I hope it's very soon because like some of you, I'm getting upper management heat about this awesome 'feature' in the S3.

    http://www.neowin.net/news/microsoft-rolls-out-surface-2-firmware-updates-promises-wi-fi-update-for-surface-pro-3

    Was this answer helpful?

    0 comments No comments
  2. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2014-10-15T17:00:26+00:00

    On Wed, 15 Oct 2014 15:33:22 +0000, clayton006 wrote:

    >>All of my wificlass BSODs have all been fixed by wiping out my surface pro 3 and reloading it after the latest firmware update. Not one BSOD since. All of my software has been reinstalled for at least two weeks and I haven't had a single issue.

    >>

    >>

    >>

    >>Not suggesting that you HAVE to go out and do a wipe, but so far so good for me.

    Glad you resolved this. I think it is dreadful that doing a reset seems to be

    the answer to issues like this. Worse, this thread, 9 pages of it has not had a

    single reply from official Microsoft staff and this thread started in July.

    __________________________________________________________________________________________________

    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
  3. Anonymous
    2014-10-15T20:37:39+00:00

    I think the answer may be to embarrass Microsoft in Social Media.  They are sponsoring the new season of the Walking Dead for example with some Twitter hashtag.  Point them to this forum.  I actually love Microsoft, even own stock, hoped their Surface machines would bring them back to the top but I think at this point they need to be publically embarrassed because I don't think they really care.

    Was this answer helpful?

    0 comments No comments