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

Barb Bowman 80,805 Reputation points MVP Volunteer Moderator

2014-12-23T22:29:04+00:00

Would love to see an update for NetGear R7000 Nighthawk...

I found a workaround that is as ugly as sin, but it may help in the resolution of this issue if a developer is reading this... If I can help resolve the issue by providing more details, please PM me and I'd be happy to provide details such as dumps and what I've tried so far...

I've not had any issues with WiFi slowdown, or lack of connectivity after I come back from sleep. What I've experienced is that whenever the system would go into connected standby mode (regardless if it's on a wired or WiFi network), the system would crash with a BSOD and reboot. This would happen multiple times overnight and could be stopped by not allowing sleep, but that's not particularly effective for how I use the tablet (I need it to be mobile). Dump file always indicated PCI bus issue and in particular WiFi driver crash.

Tried numerous things - including not believing it's WiFi and removing all USB connected items, no luck.

What worked - if I disable the driver for WiFi when I'm on a wired network - the system does not crash when it goes to sleep - been running a whole 24 hours so far without one critical reboot showing up in the event log (and also without losing data that I forgot to save prior to one of these unexpected reboots). I expect to need to enable the driver when I need WiFi, then to disable it before I put the system to sleep - it's a pain, it's ugly, but it will apparently resolve the reboot issue.

My environment - my Primary WiFi environment - Nighthawk R7000 with AC. Using either 5 or 2.4 (or wired network for that matter - being connected to a WiFi AP was not a requirement, the only requirement was that the driver was active). I do have the November firmware installed and all device drivers are up-to-date.

As far as I know, your issue is not related to the r7000. No one else has reported a crash here with that router. I use one myself. Which wired adapter do you have? Are you using a dock? Do you have any VPN software installed?
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-23T22:15:18+00:00

Would love to see an update for NetGear R7000 Nighthawk...

I found a workaround that is as ugly as sin, but it may help in the resolution of this issue if a developer is reading this... If I can help resolve the issue by providing more details, please PM me and I'd be happy to provide details such as dumps and what I've tried so far...

I've not had any issues with WiFi slowdown, or lack of connectivity after I come back from sleep. What I've experienced is that whenever the system would go into connected standby mode (regardless if it's on a wired or WiFi network), the system would crash with a BSOD and reboot. This would happen multiple times overnight and could be stopped by not allowing sleep, but that's not particularly effective for how I use the tablet (I need it to be mobile). Dump file always indicated PCI bus issue and in particular WiFi driver crash.

Tried numerous things - including not believing it's WiFi and removing all USB connected items, no luck.

What worked - if I disable the driver for WiFi when I'm on a wired network - the system does not crash when it goes to sleep - been running a whole 24 hours so far without one critical reboot showing up in the event log (and also without losing data that I forgot to save prior to one of these unexpected reboots). I expect to need to enable the driver when I need WiFi, then to disable it before I put the system to sleep - it's a pain, it's ugly, but it will apparently resolve the reboot issue.

My environment - my Primary WiFi environment - Nighthawk R7000 with AC. Using either 5 or 2.4 (or wired network for that matter - being connected to a WiFi AP was not a requirement, the only requirement was that the driver was active). I do have the November firmware installed and all device drivers are up-to-date.
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-19T14:35:02+00:00

Where do I find this firmware update and how do I apply it to my surface pro 3.. because I just got this crash, so clearly it isn't on my surface pro 3.. ???
Was this answer helpful?

0 comments No comments