BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED occurs regularly

Anonymous
2018-12-02T09:50:25+00:00

My new SB2 arrived on Wednesday. Since Friday I had the same bluescreen for 3 times by this morning. There is no system file mentioned and every time I have to hold the power button to make the device restart.

When the first bluescreen occurred, I was able to find new updates on Windows update (despite the fact that I had done basically nothing but Windows updates for the past 2 days), but the last 2 bluescreens occurred within the last 10 hours and I checked a lot, there are no updates avaliable. It doesn't seem to matter what I do in Windows to cause this bluescreen, the last one happened after I closed Outlook and stared at the desktop for a bit.

I have a MEMORY.DMP as well as an evtx file of all events registered since the boot and the last bluescreen, these events were only 7 minutes apart.

I also have noted information from the reliability monitor from the last bs.

Basically the last event (and the only event immediately before the bs) is Warning: Event 37: Kernel-Processor-Power (Microsoft-Windows-Kernel-Processor-Power) and the details are as follows (translated): The speed of the processor "7" in group "0" is limited by system firmware. The processor is in this limited performace state since 71 seconds (measured since the last report).

The last entry from the reliability monitor is: Unexpected Shutdown: Problemsignatur: Problemereignisame: BlueScreen

Code: 1000007e

Parameter 1: ffffffffc0000005

Parameter 2: fffff8011ce3dbc9

Parameter 3: fffff30ad219a548

Parameter 4: fffff30ad2199d90

Betriebssystemversion: 10_0_17134

Service Pack: 0_0

Produkt: 256_1

Betriebsystemversion: 10.0.17134.2.0.0.256.48

Gebietsschema-ID: 1031

Even with all updates installed, Surface Base 2 Firmware Update, Surface System Aggregator, Surface ME still report driver issues in the device manager. There seem to be no updates available for these.

I have read that this bs was caused by Avast AV once, and I use Avast AV, but I also read that the issue was fixed on their end.

I have MS Office ProPlus through my university, 2/3 times the bs occurred I was using OneNote for Windows 10.

Since I bought the 13 inch SB2 with 500 GB of storage at an extremely low price, a refund is not an option for me.

If needed I can provide the files mentioned and a list of programs I installed.

//Edit: Just had the 4th bs, again doing absolutely nothing but being on the desktop.

Surface | Surface Book | Install and update

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
2018-12-04T21:07:22+00:00

Thank you for your feedback and the information you’ve shared. 

Update 12/11: This is now fixed in the December 11, 2018—KB4471324 (OS Build 17134.471) update.

Symptom Workaround
After installing November 27, 2018—KB4467682 (OS Build 17134.441) update<br>some users may get a blue or black screen with error code “System thread exception not handled.” Resolution for this issue will be available in the December 2018 security update release. <br><br><br><br><br><br><br>For customers who are currently experiencing this issue please follow these instructions<br>Troubleshoot Bluescreen Errors and uninstall KB KB4467682. <br><br><br><br><br><br>Note for Surface Book 2 customers:  We are blocking this optional update only.<br>You will receive the required December 2018 security update release.

Was this answer helpful?

9 people found this answer helpful.
0 comments

59 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-12-08T14:59:06+00:00

    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

    Why was this post merged into this thread? It is for a completely separate BSOD error that has existed for a few months.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-08T19:06:50+00:00

    Well I've uninstalled and reinstalled the update that was suspended (before it was suspended) and that lowered the problem.  Updates since seem to have eliminated the BSOD's.  So one user out here (SB2 15) using up to date updates is at a good state.  I've really got too much to get done before the end of the year to spend a lot of time digging into what cleared the issue (very sorry) but if no one reports back when things seem to be running ok, no one gets that message to mix with the ones still having trouble.  I did not update Nvidia drivers beyond the 391.xx ones that came down along with the firmware updates.  I have seen firmware updates and a couple of windows updates in the last few days.  Only careful point to note is that I do not yet have the Oct update, still running 1803.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-12-08T19:27:42+00:00

    I downloaded the Windows Update Assistant and installed 1809, working pretty well ao far. No BSODs after a few hours.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-08T22:19:42+00:00

    According to 

    https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376

    patch day is in 3 days (though this issue would technically justify an out-of-band release). I read an article which suggested that the update will be released then.

    Was this answer helpful?

    0 comments