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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-12-04T13:14:11+00:00

    Same here. Recently bought my SB2 and updated it and now I experience at least one BSOD per day. It seems it's the new update so I'd urge Microsoft to release a fix ASAP and keep us well updated. 

    This is unacceptable considering this is a top of the range laptop. 

    EDIT: also, yes, Windows Hello has stopped because of this too. I had to roll back the driver to fix the issue (at least temporarily). Do you guys not test your updates??

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-04T12:53:41+00:00

    SB2, having the issue.  The update mentioned is probably when it started but due to the randomness of the crashes it was difficult to get a sense of the root cause since the error reporting was pretty useless.  Reinstalling from the core image represents a path of hours of recovery work to get a working machine back to a work capable state and that is not confidence inspiring as a first solution recommended.  That should be a last resort - perhaps it is.

    There has been an update to the update as it reinstalled and created a dual entry in the update log.  Uninstalling and reinstalling reduced my occurrences but that could be anecdotal.  MS - this is a flagship device.  Be sure someone fixes this ASAP.  C Suite folks are using this device and they will have a simple response "take this thing away and never bring me one again".

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-12-04T10:43:19+00:00

    Same issue here. Also had trouble uninstalling too.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-04T08:02:49+00:00

    I uninstalled yesterday kb4467682 and it seems it fixed BSOD problem. However Windows Hello stopped working an I have always to log in with PIN. It says Windows Hello if I try to configure it again. Basically a "try again" screen in spanish:

    This happened to me too. What you want to do is stop the Windows Biometric Service under Services, then under System32/WinBioDatabase remove those files (back them up if you want to) and restart the service. Then you should be able to reconfigure Windows Hello.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments