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
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
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

155 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-07-23T13:46:41+00:00

    Couldn't find the subscribe to thread option so I decided to reply and report that I believe I'm having this same issue with my Surface Pro 3 even after the July 16 update.  On the blue screen it says KMODE_EXCEPTION_NOT_HANDLED (nwifi.sys).  Is that what everyone here is seeing? I don't have this problem with my Surface Pro 2.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-07-23T20:43:06+00:00

    I'm the OP and for me I have not see the BSOD since the July 16 update.  However, I have seen the black screen issue when waking the tablet from sleep and I have also seen limited and/or no connection issues.

    DonalCo:  The pen not working is an issue that I have seen before on the original Surface.  One trick I have learned is to hold the power button and the volume up button for 15 seconds.  The Surface should reboot twice during this.  After the time is up, stop pressing the buttons and wait a few seconds and then turn it on.  I kid you not this works.

    DonalCo: Do you have Hyper-V enabled?  Power options should be hidden unless you have Hyper-V enabled.  Also, do not check off "allow computer to turn off this device to save power".  If you read some of these other posts that could lead to BSOD.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-07-25T15:54:47+00:00

    I've been getting a lot of BSODs since i unchecked the box that says allow windows to turn off this device to save power.  the blue screens i would get would blame the wificlass.sys.  anytime i would resume from standby.

    I also have been having the issue where i have limited to no connectivity when coming out of sleep mode as well.  It's what prompted me to uncheck that box for my wifi adapter as it seemed to solve that issue on a Sony Vaio with Win 8.1 installed on it.

    I have not checked that box and am going to monitor it to see if the BSOD stops.

    Driver is 15.68.3044.85

    Was this answer helpful?

    0 comments