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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-12-06T18:06:53+00:00

    Try to switch off windows hello, seems like that it helps. Did that last night. No crashes yet

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-06T17:35:41+00:00

    I have been seeing this blue screen today and yesterday, and I do not have the referenced update installed.

    Last night I received several SB2 updates (along with updates for 1803), around 3 BSODs since then.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-12-06T17:27:56+00:00

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-06T14:34:39+00:00

    Therefore, please let me know if I MUST uninstall KB4467682 in order for the problem to be fixed by the resolution coming in the December security update.

    Thank you!

    Sean

    I got rid of the constant BSODs by simply using nVidia's GeForce Experience App and updating my nVidia drivers from 416.34 to 417.01 five days ago (nVidia has pushed v417.22 since, which I'm currently running). I have not had a single BSOD since, and my machine runs 24/7. Besides, you should always keep your drivers up-to-date, so it won't hurt to try that first to see if it also works for you.

    The Fall Creators update rolled-out the capacity for OEMs and others to conform to the new "Modern Windows Driver" specification. Intel took advantage of that in the 1803/1809 update by pushing several drivers for multiple chipsets, including an update for the integrated GPU in the SB2. Also, there was a firmware update included. There are users out there reporting that they have bricked their SB2 when rolling-back this update. Here is a link to a PCWorld article outlining the new driver specification that Microsoft introduced and Intel took advantage of in the latest update, highlighting the warnings from Intel about trying to back-out: https://howrahdailynews.com/2018/11/30/intel-publishes-its-first-modern-windows-driver-for-pcs-and-theres-no-going-back-pcworld/

    I would suggest updating the nVidia first; basically, it won't hurt anything. If it works for you, your SB2 will be running on 1803/1809 with up-to-date drivers all-the-way-around without having to go through the hassle of rolling-back. This is the current state of my SB2 while we all wait for the fix. If it doesn't work for you, no harm, no foul, and your nVidia dGPU is up-to-date.

    Was this answer helpful?

    0 comments