Windows 10 Revised October Update (November) strikes Surface Book 2 Owners randomly with BSOD

[Maticks]

Users are reporting that after the revised Windows 10 October Update (November 27th Update) , The Surface Book 2 has been experiencing issues with random BSOD.

I personally only had mine update yesterday and experienced 2 BSOD at work and 5 BSOD this morning.

The error has been reported as the same for all users SYSTEM THREAD EXCEPTION NOT HANDLED.

 

All 30 Surface Book 2 machines at my work are having this issue. Reddit threads are popping up with a large number of users experiencing the issue.

The problem can be resolved by removing the update and system stability comes back.

 

Microsoft at this stage have made no comments to the cause, likely scrambling for a fix given all the issues with Octobers update deleting files.

 

Quote

“Bricks your Surface Book 2 to the point you have to reinstall Windows” is, curiously, not listed. Funny that.

However, this is what several users have found themselves doing as a last resort in order to get rid of the problem.

The BSOD headache manifests itself by throwing a SYSTEM THREAD EXCEPTION NOT HANDLED error and rebooting the computer. Some users reported seeing the error repeatedly, while others are luckier, losing their work only three times a day or so.

It isn’t a good look for Microsoft’s flagship laptop (which we, incidentally, rather liked). With an eyewatering price-tag, users would be forgiven for expecting that it should be a showcase of how Windows should be.

 

The Register Article

https://www.theregister.co.uk/2018/12/03/surface_book_2/

 

 

https://myitforum.com/surface-book-2-hammered-by-november-27-2018-kb4467682-windows-10-update/

 

Microsoft Thread

https://answers.microsoft.com/en-us/surface/forum/all/bsod-systemthreadexceptionnothandled-occurs/abbfff03-1694-432f-97fb-9a5ed6c54a20

 

[Ashley MLP Fangirl]

Microsoft should scrap Windows 10 at this point. it's an awful product breaking more and more with every update... 

[GoodBytes]

Sounds like the same problem that affected Intel users where a block was put. I guess the block didn't apply to Surface Book 2 users due to custom package (or these users did a force upgrade).

 

I don't know if Intel updated the drivers since, but if they did, I would try to uninstall the Intel drivers, restart and install the official latest Intel drivers (again, if the issue has been solved).

 

[EnergyEclipse]

Microsoft's own words

[Radium_Angel]

10 minutes ago, firelighter487 said:

Microsoft should scrap Windows 10 at this point. it's an awful product breaking more and more with every update... 

I'm very happy with my Win 7 box, and various *nix boxes. We were forced to update ~400 systems at work to Win10 and have had nothing but issues with them since.

 

Win10, the new WinME

[Maticks]

6 minutes ago, GoodBytes said:

Sounds like the same problem that affected Intel users where a block was put. I guess the block didn't apply to Surface Book 2 users due to custom package (or these users did a force upgrade).

 

I don't know if Intel updated the drivers since, but if they did, I would try to uninstall the Intel drivers, restart and install the official latest Intel drivers (again, if the issue has been solved).

 

I suspected that to start with and installed the offical ones from Intel. It ran fine last night till this morning. BSOD this morning. Then right after the reboot 3 times without opening anything. It's been stable an hour but anything can set it off. Mid email or even just clicking an application in the task bar. It's not impacting surface pro users. It doesn't appear to be Intel driver related.

 

I did notice one thing I believe a firmware update took place during that update. Not sure if it was part of the update or just my surface book 2 getting an update. It's only several weeks old. Need a bigger sample size to determine that.

[Ashley MLP Fangirl]

1 minute ago, Radium_Angel said:

I'm very happy with my Win 7 box, and various *nix boxes. We were forced to update ~400 systems at work to Win10 and have had nothing but issues with them since.

 

Win10, the new WinME

sadly i'm forced to run 10. on my laptop because of school, and on my pc because 7th gen...

[Speed Weed]

[kting15]

.... how do they screw up compatibility with even their own hardware? It's insane.

[Cyberspirit]

They need to admit that this isn't working and just give up on this update schedule.

 

[samcool55]

6 minutes ago, kting15 said:

.... how do they screw up compatibility with even their own hardware? It's insane.

I was wondering the same thing but, it's microsoft, should we even be surprised at this point?

I guess we can officially classify their attempt to improve windows 10 as a fail.

https://redmondmag.com/articles/2018/11/14/microsoft-transparency-windows-10-update.aspx

[GoodBytes]

2 minutes ago, samcool55 said:

I was wondering the same thing but, it's microsoft, should we even be surprised at this point?

I guess we can officially classify their attempt to improve windows 10 as a fail.

https://redmondmag.com/articles/2018/11/14/microsoft-transparency-windows-10-update.aspx

Yes, 'cause these kind of change takes 1 day.

 

[NunoLava1998]

Thankfully, a way to fix the issue has been found:

 

[samcool55]

Just now, GoodBytes said:

Yes, 'cause these kind of change takes 1 day.

 

Yes it takes time but what kind of message do you think they send to people when they push an update to their own damn devices that breaks it?

 

"We will make Windows 10 better!"

few weeks later

"we broke our own devices with our own software!"

 

Doesn't give me confidence when it has been going downhill for months...

[samcool55]

1 minute ago, Cyberspirit said:

They need to admit that this isn't working and just give up on this update schedule.

 

I doubt that, they are riding the "as a service" hype train hard and for some reason they still think windows 10 will end up "as a service" when we all know it just won't.

I agree that they should give up, but i doubt they will anytime soon.

 

Atm windows 10 is a mess and it's only getting worse. It's getting bloated with a bunch of software the average user doesn't care about and it gets worse with every single update. They can't keep this up because it will end up as a bloaty slow mess and they will realise one day they can no longer support it and need to start from scratch again.

That day will come, you can be sure of that. It's insane to think windows 10 will still be alive in 20 years, i just don't see that happening.

[Guest]

[kuhnertdm]

Wow, who would have guessed you'd have major bug issues if you fire your QA team and rely on crowdsourced bug reporting

[Blademaster91]

48 minutes ago, GoodBytes said:

Yes, 'cause these kind of change takes 1 day.

 

Well it wouldn't take Microsoft very long to change their update schedule and stop breaking PC's more with updates than it intends to fix. I mean at least make the Surface a priority to get stable updates.  I agree with @kuhnerdm , who would've thought relying on unpaid beta testers would result in broken updates.

[elfensky]

1 hour ago, Maticks said:

-snip-

 

 

Well... Shit. Then again the bug seems to be caused by the "cumulative" update, and these seem to be drivers.

 

[Maticks]

5 minutes ago, ElfenSky said:

 

Well... Shit. Then again the bug seems to be caused by the "cumulative" update, and these seem to be drivers.

 

I honestly think its that Firmware update thats causing the issue. But it doesn't explain why when you roll back the software the problem goes away.

Intel drivers i've tried changing with the update in place and that made no difference.

 

[DocSwag]

I have an SB2 and it happened to me too; I got like three BSODs in two days before I got pissed off enough to search it up and roll back the update. No BSODs since.

[mynameisjuan]

Meanwhile I am here with not a single problem since release day.

[GoodBytes]

1 hour ago, Maticks said:

I honestly think its that Firmware update thats causing the issue. But it doesn't explain why when you roll back the software the problem goes away.

Intel drivers i've tried changing with the update in place and that made no difference.

 

Microsoft likes to name drivers related to the Surface device as Firmware, which confuses things as you actually have  Firmware updates (UEFI updates). The question now is which driver or which combination of driver causes the problem.

[yian88]

microsoft its such <content removed>  this   could  have  beeen 100  times easier if  they didnt implement  uwp   and force  a hybrid  windows  its almoost   like win 8.0 never happened,  they learned  nothing  from it,  8.0 was pure trash until they managed to  fix it  a year later with  8.1

everywhere i look in windows  its  just full of   bloatware and increasing with every update,  there isnt  even  a shred of memeory mannagement,   frsh   booot  and os is eating  2.5/3gb ram with nothing open,  its ridiculous

Edited December 4, 2018 by SansVarnic
Content Removed

[Maticks]

6 minutes ago, GoodBytes said:

Microsoft likes to name drivers related to the Surface device as Firmware, which confuses things as you actually have  Firmware updates (UEFI updates). The question now is which driver or which combination of driver causes the problem.

Correct its hard to tell, but given that removing the update seems to fix the issue. it could be a combination of the update and something else that was changed.

I honestly would have expected a few things.

1.) this should have been tested by Microsoft in house on their own hardware before pushing he update out.

2.) this should have been rolled out to Microsoft Insider to identify the issue or at very least beta testing the update.