Surface Pro 5 Frequent BoD


I picked up a surface pro 5 a few months ago from a microsoft store. I loved it. Probably the best laptop I’ve ever owned.

But in the last 2-3 weeks I’ve been getting ever more frequent BoD’s. Sometimes just minutes apart. Then it will go a day without any problems. But definitely at least one a day. Worst was five in one day.

No warning – things all of a sudden slow down and then – WHAM. No mini dumps are created. Just sits at 0% collecting data and then boots into the UFCI. Exception is almost always the same – UNEXPECTED_STORE_EXCEPTION. Everything is set up correctly to create dumps but nothing is created. All updates applied.

I haven’t yet reset the machine but I probably will this weekend to see if this fixes things.

Anyone else having these problems? Searching the web results in some hits but no effective resolution other than taking the machine back for an exchange.

Comments (9)

9 responses to “Surface Pro 5 Frequent BoD”

  1. waethorn

    Seems lots of people have started getting this in October with no definitive solution:

    Suggestions are:

    1) do a clean install

    2) update your drivers

    3) run (good) disk diagnostics to see if your drive is failing

    4) restore your registry from a backup

    ....basically, the same suggestions you always see because nobody has any clue of what they're talking about.

    • jimchamplin

      In reply to Waethorn:

      Let's not forget using the file check utility to make sure that the Windows installation is good.

      That's always super effective, because Windows only messes up because of bad files. /s

      • waethorn

        In reply to jimchamplin:

        I don't trust it anymore. DISM with the cleanup-image option is better than SFC in my experience, although neither will usually fix errors caused by shoddy updates. I use Malwarebytes Toolset (only available to MB partners) and it repairs more problems than the built-in MS tools.

  2. timo47

    The update history page for the SP5 shows a lot of updates, including in September and October.

    Chances are one of those updates is the culprit. Unfortunately, without a dump it will be difficult to see which driver exactly is causing the problem. I would recommend you go backwards (starting from the most recent) through that update list and one by one revert to a previous version of those drivers that were pushed as part of the recent "firmware" updates.

    If the problem is indeed in one of the drivers, a complete reinstall will not help.

    Edit: it might also be a good idea to check which applications you installed right before the problems began.

Leave a Reply