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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-11-14T00:45:59+00:00

    I am still amazed this is not fixed.  I nuked my Surface Pro 3 and with only Microsoft Office installed I have not had any BSOD or wireless connection problems but I still need to setup Visual Studio, SQL Server, IIS, and a few other things that will make this a machine I can use.  I have been waiting for a firmware upgrade to hit that sounds like a fix.  Nothing so far. 

    As Mattgbiz so eloquently puts it "network admins aren't willing to go through a full troubleshooting process" for single machines.  Certainly the City of Huntington Beach open wifi, or Starbucks open wifi, or Barnes & Noble open wifi, or any other entity wont do so.

    To quote Mattgbiz once again "Oh Well..."

    To be fair, I'm also not pushing our network admins to fix this because it's clearly a Surface problem... no other guest machine, mobile phone, tablet or other computer has the problem so why try fix the Cisco AP?

    It's on MS to work with Marvell to fix the driver issue.  I do have faith it will be fixed... just think it's low on the list.

    I've provided MS Support with my verbose dumpfile from the BSOD so they have the info.  I can recreate it at will.  : )

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-11-13T22:32:21+00:00

    Let me give an update on what I know so far:

    Background - IT Professional and Project Manager

    Device - Surface Pro 3 - i7 - 8/512 GB 

    Purchased - Sept 2014

    BSOD almost every time I access a corporate Cisco Access Point, but works on every other Access Point to date and I travel a lot.

    I have a case open with MS Professional Services @ $250 because regular support refused to take my case because they consider the Cisco access point a business only issue.

    I have had a back and forth with PS going on several weeks. Multiple firmware updates, drviers, etc. configuration changes, multiple uploads of 8GB dumps, all to no avail. I still BSOD if I cannot to that darn Cisco.

    Finally, I have determined with netsh wlan profiles that the Cisco AP is configured to broadcast one SSID, but access either WPA/TKIP or WPA2/AES authentication. This *is* the issue. The drivers for the Marvel Wireless simply cannot handle this correctly and BSOD.

    I just need to get MS to start working on this angle.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-11-13T19:11:20+00:00

    I am still amazed this is not fixed.  I nuked my Surface Pro 3 and with only Microsoft Office installed I have not had any BSOD or wireless connection problems but I still need to setup Visual Studio, SQL Server, IIS, and a few other things that will make this a machine I can use.  I have been waiting for a firmware upgrade to hit that sounds like a fix.  Nothing so far. 

    As Mattgbiz so eloquently puts it "network admins aren't willing to go through a full troubleshooting process" for single machines.  Certainly the City of Huntington Beach open wifi, or Starbucks open wifi, or Barnes & Noble open wifi, or any other entity wont do so.

    To quote Mattgbiz once again "Oh Well..."

    Was this answer helpful?

    0 comments