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-07-01T15:59:22+00:00

    All drivers are updated for me.  All firmware updates are also installed.  We are on WPA-2 Enterprise here.  It would boot for me fine but during use it will crash. At home I use WPA-2 Personal but it seemed to work fine there.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-07-01T15:27:31+00:00

    Same exact thing happened on 3 different Surface Pro 3 tablets when connecting to my employee wireless network. If I connect to our guest network it works fine. This was during the initial setup and after completing the setup. The moment I switch from the guest network to employee network (which is WPA-2 Personal) it would BSOD. I was able to get them working after all available Windows updates including a firmware update that was available. I thought it was working fine but every time I restart after an update it will bluescreen. But then after that it will boot up ok.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-07-01T14:45:19+00:00

    So I unboxed my second Surface Pro 3 and during the OOBE when it asked to check for a wireless network it BSOD on me.  So obviously there is something in that driver that does not like my work wireless network.  Now before you think my APs are configured strangely, we have over 200 laptops spanning multiple OEMs going back to 2011 on our network with zero connectivity issues. 

    The driver on the Surface I just unboxed was the older driver too.  Version 15.68.3036.67.  The updated driver on the first Surface Pro 3 is 15.68.3040.75.  So hopefully someone would like to do more diagnostics with me on this issue.

    Was this answer helpful?

    0 comments