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-05T15:31:29+00:00

    @Sil_V

    I've noticed this at https://support.microsoft.com/en-gb/help/4467682

    At the end of the page there is:-

    I've not investigated "Troubleshoot blue screen...." All you have to do is boot your machine! 

    Good Luck with getting this sorted and your exams.

    Hope this helps.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-05T23:54:29+00:00

    My SB2 is in this blue screen since 10 minutes.

    Until this problem it was my best laptop ever.

    I am a developer and I need this laptop for work. It's unbelievable how bad the testing on Windows Updates has become (see the latest Windows Fall Update troubles).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-12-06T11:12:30+00:00

    Hi Laya,

    Thank you for keeping us informed, I do hope the issue gets resolved soon.

    In the meantime, I have a question about the workaround: it suggests uninstalling KB4467682, but is this absolutely necessary to do before the resolution comes in the December security update?

    I ask because although my Surface Book 2 has been suffering from the same issue (I got a BSOD on the 1st right after the update installed, and 3 more BSODs on the 3rd), it seems to have calmed down for now (for me, the audio always glitched as it was crashing, so I'm trying to limit audio use as much as possible just in case, and not listening to Spotify as I work, at least in my mind, seems to have soothed the savage beast).

    On the other hand, I see that uninstalling KB4467682 has caused even more/worse problems for other people, and I would rather wait patiently with my Surface Book 2 in a usable state until the official fix comes through.

    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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-06T13:14:19+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.

    Certainly not. But most people who work on a SB2 don't want to risk loosing data, and that's why it is absolutely worth uninstalling the update.

    For me the bluescreens got worse every day and started to happen while I was working.

    If you want to have a software bug decide whether you can listen to music, that is absolutely your decision. But if it was me thinking about downgrading, I would disable and remove Windows Hello, downgrade and reenable Windows Hello after making sure drivers are up to date on the spot. Because that is the only issue you will definitely have when downgrading.

    Bluescreens freezing the currently playing audio is not unusual by the way. Just make sure your volume is not set too high when you're expecting a bluescreen.

    Was this answer helpful?

    0 comments