BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED occurs regularly

Long story short, while I was not a very happy SB2 owner, my machine running 1709 was somewhat stable until about August (main issue was that I had to eject the screen every time I wanted to power on, and then re-attach after pressing the power button but I lived with it for about 8 months because everything else seemed to work). It has been down hill since then (August).

Around the time the power button issue was fixed via an update, my touchpad/cursor started freezing up (especially when two finger scrolling), my AC adapter stopped working/SB2 would not charge, and overall performance degraded with freeze ups and slow downs when there was plenty of available CPU and Memory according to task manager. These are all issues that others have also experienced. I made no software or settings changes other than allowing Windows Updates to install. I highly doubt its defective hardware or something not playing nice (other than my SB2 and Windows 10 which are both Microsoft products).

So now for the new-ish issue I have been struggling with...which I already submitted reports via Feedback Hub two months ago but have yet to hear back or see a resolution...

BSODs when powering on. Specifically "DRIVER_POWER_STATE_FAILURE"

I hibernate a few times a day. I power on a few times a day. It seems to happen every few days. The result is losing my place in what I was working on and sometimes losing actual work. I NEVER got BSODs before in my 11 months of running 1709. I am pretty certain they were introduced with 1803 but its possible that an update or patch pushed via Windows update is also the culprit (maybe KB4464330 since that was applied right before the BSODs started?). My initial thoughts also include that it is a Windows 10 issue and NOT a SB2 issue but I am not positive. Reason I am suggesting that is because I took a brand new Lenovo machine and loaded 1809 and it happens to have the same problem with BSODs every few power-ons with the same error message.

Hoping Microsoft actually does something about this but not holding my breathe

I rolled back to 1709 last night. Too many BSODs.

I mean if a fix js available to roll out with the December uodates, just push it out now. It should be an embarassmeemb to MicroaoMi for theit flagship hardware to BSOD on Windows.

This makes me miss MacOS.

Sorry this happened, Did you uninstall the update ? followed the workaround provided ?

Best thing for MSFT to do is put new leadership into place for the group that manages testing and promoting updates to production status. You guys are driving customers away. I am empathetic as to how hard a problem it is to solve, but not solving it isn't the answer. Put someone in charge who cares enough to make sure this stuff doesn't happen anymore please.

x100000

Its absolutely freaking ridiculous!

Every freaking time Microsoft releases an update, something major breaks, and it usually takes them months or close to a year to acknowledge or really fix, despite people reporting left and right. They do not listen to customer feedback because when you submit a bug report or contact support and ask for escalation or post here, you get no acknowledgement, or told it can't be escalated, or you don't see a fix.

My SB2 was rock solid on 1709. I tried to update to 1803 in Spring, the update failed, BSOD, I was one of the lucky few whose device reverted automatically. Others were not lucky and ended up with bricked devices. Microsoft ended up blocking the update for a long time.

I held off on 1803 but an update/patch pushed for 1709 started causing some weird behavior around August/September so I finally held my breath and updated to 1803. Guess what, I now get BSOD every few times I turn on my SB2. I had NEVER seen a BSOD on my SB2 on 1709, EVER. This causes me to lose my place in what I was working on and some times lose actual work. Lets see, five months since the botched release in April, yet they could not test and prevent yet another botched release (on their own hardware nonetheless)? Funny story is the issue carried over into 1809 because I deployed it on a test machine to see if it would correct (before 1809 was pulled). That is a HUGE fail Microsoft, HUGE.

Now yet again, another update pushed, more devices bricked, for 1803 which was first released 8 months ago, yet Microsoft cannot get their acts together. I am SCARED for every update now. I used to be excited for updates. I have tons of issues in 1803 that I did not have in 1709. Artifacts left on my screen from "tool tips", files that will not open without having to double-click several times (file cannot be found), and several other issues remain.

It took Microsoft, what, 8-9 months to fix the power button issue? (Background: Windows update almost a year ago made it so the power button stopped working on folk's SB2 devices). Many people reported the bug, there were posts here on this very forum. It happened at the same time as an update. Microsoft Support said there was no way to escalate the matter. They would only suggest a full hardware replacement which is what they say every time there is a major issue instead of actually investigating. Pro-tip: most of the issues have been software related, replacing hardware does not magically fix, and is a HUGE headache for the user to re-setup their PC and experience down time (a big disadvantage with a non-removable drive). The only way to power on my device for almost an entire year was to un-dock the screen from the base, press the power button, and re-insert, which is what I did the entire time. People would look at me crazy. Eventually Microsoft was able to fix via a software update.

Microsoft, it is time to start listening. You keep botching things. You have ruined your OS and hardware reputation. It is mind boggling that no one is testing your OS on your own hardware, there is no acknowledgment when there are issues, it takes months and months and months to issue fixes, more things break every time there is a new release, and the cycle repeats itself. I had zero major issues with Windows 7. I saw it run well in environments that had hundreds of thousands of workstations. The few times I have participated in testing of Windows 10 in both corporate and personal use, it has been a DISASTER.

Get your acts together! Listen to your customers. When a bug is reported whether via your Feedback hub, support, or this forum, at least acknowledge it, and don't take months and months to fix. Enough is enough!

Same issue with my 15" top end SB2. An additional symptom of mine is that the fans seem to be running far more; it's running hotter, battery or plugged in.

Once this is fixed, I'm going back to my old mantra of "never allow automatic Windows updates," sadly.