Surface Pro 3 Blue Screen due to Wifi?

Anonymous

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

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

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

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.

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

155 additional answers

Anonymous

2014-10-16T22:46:17+00:00

I have a Surface Pro 3 that is attached to a Microsoft Docking Station.

When I leave the Surface idle for a long period of time (2+ hours) when I come back it has restarted. I am getting numerous BSOD dumps. If it has not restarted, it will not wake up/start until I hold the power button twice (turn off, then on).

I have been able to reproduce a BSOD on command by unchecking the "allow the computer to turn off this device to save power" in the "Surface Pen Driver" driver entry. I've uninstalled/reinstalled network and bluetooth drivers, but it still crashes. The Pen BT driver goes to "STATUS_DEVICE_POWER_FAILURE" with the yellow caution symbol.

I have restored to factory settings once, but it was in late July before the latest FW and WiFi driver updates. Although one of the Surfaces with the sleep issue has been updated recently and is showing issues.

Here is a link to the latest MiniDump upload (after running Driver Verifier): http://1drv.ms/1ze4bMT

I'm also getting quite a few "Kernel-Power" Critical errors (ID - 41).

We have about 8 in our environment, but 2 of them are displaying these sleep/wake issues and also power issues. I'm not sure the issues software or hardware related, so I'm looking for help. I've spent days trying to find answers but nothing seems to work.

Any help would be appreciated.

Thanks!
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-17T14:13:42+00:00

Forgot to mention....I found a "Band-Aid" fix that I have been using. I disabled CsEnabled in the Registry and also enabled Hyper-V to disable all forms of sleep/hibernation. This configuration never gave me BSOD or errors for months. I finally decided I'd like to be able to put my Surface to sleep and that's why I started this post.

P.S. Came into work today with my Surface restarted and a new BSOD minidump....Yesterday I re-enabled CsEnabled and turned off Hyper-V....

Sleep/hibernate seems to be my issue.
Was this answer helpful?

0 comments No comments
Anonymous

2014-10-23T15:20:33+00:00

Just to add 4 more Surface 3 Pro's to the list of suffering from this issue. I tested Surface pro2 and have never had an issue. So I started to rollout Surface 3's to staff. :(.

This is a real issue that needs to be resolved. Our BSOD are all somehow related to wifi.

For me, its switching from one wifi source to another (home / work) Other staff are reporting similar findings
Was this answer helpful?

0 comments No comments