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-04T07:54:38+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:

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-04T07:26:25+00:00

    Same thing here, problem started right after the kb4467682 was installed.

    Never had this issue before than, now it happends 4-5 times every day.

    Here's the last logged error I've got before bluescreen. (Kernel-Processor-Power)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-12-04T04:20:43+00:00

    Same issue here.  Only had the SB2 for a week and have seen multiple BSODs per day.  Found the Reddit page tonight and rolled back 1803.  We'll see if that helps, or what it breaks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-04T01:55:21+00:00

    Well this has been a fun day of crashes, losing work and trying to recover files! 

    Windows installed updates this morning on my SB2 and had EIGHT BSOD today.  I took the advice of others in this thread and uninstalled KB4467682  - so far no blue screens for the last 30 minutes, fingers crossed! 

    UPDATE:  12 hours with no blue screens - uninstalling KB4467682 seems to have fixed the problem for now.

    ******************************************************

    Error 12/03/2018 5:51:02 PM BugCheck 1001 None

    Error 12/03/2018 5:49:20 PM BugCheck 1001 None

    Error 12/03/2018 4:10:52 PM BugCheck 1001 None

    Error 12/03/2018 3:06:14 PM BugCheck 1001 None

    Error 12/03/2018 2:58:50 PM BugCheck 1001 None

    Error 12/03/2018 1:51:20 PM BugCheck 1001 None

    Error 12/03/2018 1:00:55 PM BugCheck 1001 None

    Error 12/03/2018 9:00:51 AM BugCheck 1001 None

    ******************************************************

    Log Name:      System

    Source:        Microsoft-Windows-WER-SystemErrorReporting

    Date:          12/03/2018 5:51:02 PM

    Event ID:      1001

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      WLM-SB2

    Description:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff802c00d3bc9, 0xffff8702ba4e7548, 0xffff8702ba4e6d90). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 04544045-c799-4c8d-b41b-1f08039128d4.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

        <EventID Qualifiers="16384">1001</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2018-12-03T23:51:02.044004500Z" />

        <EventRecordID>28048</EventRecordID>

        <Correlation />

        <Execution ProcessID="0" ThreadID="0" />

        <Channel>System</Channel>

        <Computer>WLM-SB2</Computer>

        <Security />

      </System>

      <EventData>

        <Data Name="param1">0x0000007e (0xffffffffc0000005, 0xfffff802c00d3bc9, 0xffff8702ba4e7548, 0xffff8702ba4e6d90)</Data>

        <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>

        <Data Name="param3">04544045-c799-4c8d-b41b-1f08039128d4</Data>

      </EventData>

    </Event>

    Was this answer helpful?

    0 comments