Surface 3, Pro 3 firmware update causing all sorts of problems

Topic

New Reply

Lengthy litany includes blue screens, lockups, Type Cover not working, and more. The Surface Pro 3 is at firmware update number 20. InfoWorld Woody on
[See the full post at: Surface 3, Pro 3 firmware update causing all sorts of problems]

Reply | Quote

Replies

Wow, what a god awful mess, that’s quite a litany of problems in your article….and to think, I was actually looking at Surface machines the other day. I must have had a case of heat stroke…
And MSFT’s stock price just keeps going up. When will this company behavior catch up with them??

Reply | Quote

I know that they’re saying the Surface calamity during the Patriots and Broncos game was due to infrastructure, but your post made me wonder if the update was a factor or not.

Reply | Quote

Makes me wonder if the NFL Surface breakdown might be related somehow. Network problems caused by firmware updates perhaps?

http://www.theguardian.com/technology/2016/jan/25/microsoft-surface-tablets-offline-during-broncos-patriots-nfl-playoff

Reply | Quote

Naw. Sounds like the Wi-Fi network went down.

I wonder if we’ll ever hear the whole story.

Reply | Quote

Naw. From what they’re saying, it sounds like a Wi-Fi problem.

Reply | Quote

If you’re looking at the Surface Pro 4 or Surface Book, there’s a hornet’s nest of problems. See Paul Thurrot’s description of Surfacegate.

Reply | Quote

@Woody…

Those Surface machines were blue screened. CBS had clear images of it. It was not a Network problem. No images on the screen at all, and, the Denver sideline still had working machines. Don’t let the MS spin off the hook.

Reply | Quote

I didn’t see blue screens….

Here’s the best picture I can find: http://www.geek.com/tablets/microsoft-surface-tablets-wrongly-blamed-for-patriots-sideline-breakdown-1645454/

But I found the CNet coverage interesting: http://www.cnet.com/news/patriots-belichick-says-microsoft-surface-breakdowns-are-commonplace/

Particularly interesting because CNET and ZDNet are sister publications…

Reply | Quote

Louis… it was indeed a network problem.

Each team is required by the NFL to be on an individual designated network, they can not share the same connection.

This was brought to light a while back during the “Deflategate” fiasco when some folks were suggesting the possibility of New England intercepting the opposing teams data now that they’re using the Surfaces.

Reply | Quote

@Ed,

I believe MSFT paid almost a half a billion dollars for the Surface product placement with the NFL. For that half billion, they received some of the worst “promotion” possible during the AFCC game when the Surface machines went down. The least the NFL could do was attempt to distract the blame to network connections.
If you believe in unrelated coincidences, the time line between the firmware update and the AFCC game Surface breakdowns is perfect.

And I saw the CBS shot that was not replayed of the Surface machines standing up on the bench showing BSs.

Either way, I’m sure we’ll never know the truth versus the spin. But Woody’s InfoWorld article regarding all the problems with the Surface update shouldn’t surprise any long term MSFT user.

Reply | Quote

Man, what I’d give to see a shot of the machines with “genuine” BSODs!

Reply | Quote