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-24T12:08:17+00:00

On Tue, 23 Dec 2014 23:07:30 +0000, Wired64 wrote:

>>I agree that it's likely not the r7000. I use the wired adapter from the dock, however, it will happen if the system is connected to the network via the wired connection through the dock, or if it's out of the dock and using a wireless connection.

>>

>>

>>

>>I use the standard Microsoft VPN that comes included with Win 8.1, but do not always have it active (in fact, most of the time, it is not active. Problems occur both if I'm connected to the VPN, or not.

Please verify that there are no Windows Updates pending (try this both docked and undocked). Also, try the two button reset (undocked) - this is non destructive:

Make sure that you have shut down your Surface first!

Then, press and hold the volume-up button and the power button on your Surface at the

same time for at least 15 seconds, and then release both.

The screen may flash the Surface logo, but continue holding the buttons down

for at least 15 seconds.

If the above doesn't help ---

Can you try an experiment? Delete the wired adapter while docked in device

manager. Then undock. Restart. Don't use VPN.

See if you can duplicate.

I'll try to get someone to look at this, but with the holiday's, no promises.

Also, anything interesting in event viewer?

__________________________________________________________________________________________________

Barb

Windows Entertainment and Connected Home MVP

My Blog - http://digitalmediaphile.com/

Please mark as answered if this answers your question
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-24T23:41:44+00:00

First off - thanks for the responses! I didn't expect to hear anything before Christmas. It's heartening to know that folks are trying to work out the kinks...

All updates are applied - both docked and not and the two finger salute was used as well.

From Device Manager, I did delete the wired network device (called "Surface Ethernet Adapter") then undocked, rebooted, redocked and the driver was re-installed. I've had the system in idle mode much of the afternoon and no reboot!

I will, however, sheepishly say that I made two changes to the system - this one was one, but I also removed the NetGear Genie app as I didn't find it particularly useful.

I will monitor the system and let you know results after an overnight experiment... Can't say if it was the removal and re-install of the ethernet driver, or removal of NetGear Genie app, but either way, it's looking good.

Only other issue I'm having is the DisplayPort not working upon reboot. I do have a work around to this - remove power to the monitor for 5 - 10 seconds, then power the monitor back up. This has not been on the priority list as yet, so I've done no research... If I can fix that issue, I'd say this is a near perfect device and form factor!

Thanks for the Help!
Was this answer helpful?

0 comments No comments
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator

2014-12-25T13:07:53+00:00

On Wed, 24 Dec 2014 23:41:44 +0000, Wired64 wrote:

>>I will, however, sheepishly say that I made two changes to the system - this one was one, but I also removed the NetGear Genie app as I didn't find it particularly useful.

>>

>>

>>

>>I will monitor the system and let you know results after an overnight experiment... Can't say if it was the removal and re-install of the ethernet driver, or removal of NetGear Genie app, but either way, it's looking good.

The Genie app probably installs a HIDDEN network adapter that attaches to the

stack.

__________________________________________________________________________________________________

Barb

Windows Entertainment and Connected Home MVP

My Blog - http://digitalmediaphile.com/

Please mark as answered if this answers your question
Was this answer helpful?

0 comments No comments