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: Most helpful
  1. Anonymous
    2014-06-28T11:59:36+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


    FYI I had BSOD with this issue only when I went to the wireless driver in device manager and on the power management tab, tried unchecking "allow computer to turn off this device to save power."  When I set that back the way it was by checking it again, I haven't had the BSOD since.  Hope it helps.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-28T01:07:58+00:00

    me too.

    my BSoD minidump is here: https://onedrive.live.com/redir?resid=E492034285479031%2167878

    A problem has been detected and Windows has been shut down to prevent damage

    to your computer.

    The problem seems to be caused by the following file: wificlass.sys

    KMODE_EXCEPTION_NOT_HANDLED

    If this is the first time you've seen this stop error screen,

    restart your computer. If this screen appears again, follow

    these steps:

    Check to make sure any new hardware or software is properly installed.

    If this is a new installation, ask your hardware or software manufacturer

    for any Windows updates you might need.

    If problems continue, disable or remove any newly installed hardware

    or software. Disable BIOS memory options such as caching or shadowing.

    If you need to use safe mode to remove or disable components, restart

    your computer, press F8 to select Advanced Startup Options, and then

    select Safe Mode.

    Technical Information:

    *** STOP: 0x0000001e (0xffffffffc0000005, 0xfffff8009bba5e71, 0xffffd000a88e8388, 

    0xffffd000a88e7b90)

    *** wificlass.sys - Address 0xfffff8009bba5e71 base at 0xfffff8009bb8f000 DateStamp 

    0x532c9fc8

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-06-27T18:27:13+00:00

    Ooof. I hate to call these issues lucky. But in that context, yes I will call us lucky. haha. Good luck to all of us, I guess. :)

    Was this answer helpful?

    0 comments No comments