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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-17T22:38:32+00:00

    My problem was corrected finally and was due to a setting on the Cisco AP at work with certificate authentication.

    The network admin said it was a simple checkbox,

    No change on the surface side and no more BSOD.

    However this could indicate a driver issue on the surface in that hundreds of machines connected to this AP with no issues and the SP3 was the first one to BSOD.

    Was this answer helpful?

    0 comments
  2. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2014-09-17T22:06:08+00:00

    I am having exactly the same issue with a Surface Pro 3, i7 8/512.

    It has all the latest drivers including Sept 2014 firmware.

    I cannot connect to corporate Cisco access points without a BSOD.

    The dumps all points to mrvlpcie8897.sys.

    At this point, I may have to return what is otherwise a pretty good machine.

    Tech Support tells me it might be months before a corrected driver is released. Really? How did this desktop replacement get tested anyway?

    1. Is the issue ONLY with Cisco AP's? Do you connect at home ok?
    2. Do you have a case number from Microsoft support?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-17T21:39:22+00:00

    I am having exactly the same issue with a Surface Pro 3, i7 8/512.

    It has all the latest drivers including Sept 2014 firmware.

    I cannot connect to corporate Cisco access points without a BSOD.

    The dumps all points to mrvlpcie8897.sys.

    At this point, I may have to return what is otherwise a pretty good machine.

    Tech Support tells me it might be months before a corrected driver is released. Really? How did this desktop replacement get tested anyway?

    Was this answer helpful?

    0 comments