Fix Microsoft Surface blue screen issues [Go, Pro 3, Pro 4]

Madalina Dinita
by Madalina Dinita
Former Managing Editor
Download PDF
Affiliate Disclosure

  • If you happen to be bothered by repeated Microsoft Surface blue screen issues, this guide is perfect for Go, Pro 3, and Pro 4 users.
  • To solve them in no time, don’t hesitate to use Command Prompt or enter Safe Mode.
  • As scary as they may seem, BSoD errors can be addressed when using the appropriate fixes.
  • We encourage you to bookmark this Windows 10 Troubleshooting Hub for further reference.

Microsoft’s firmware updates are long-awaited by users who know that the tech company eventually fixes all the bugs they had been complaining about on its forums.

Unfortunately, for some Surface Go, Pro 3, and Pro 4 users, the update process doesn’t go smoothly and they often experience the annoying blue screen of death.

How can I fix Microsoft Surface blue screen issues?

1. Use Command Prompt

The BSOD appears when installing the update. After restarting the system, users get another error in the Windows Update page: Error – 0x800f0203.

Judging by the current activity on Microsoft’s Forum, the number of users who got this installation error message is quite significant:

While applying today’s updates, I received a Blue screen. After it restarted, it applied updates before continuing into Windows startup.
Went into Windows Update and clicked on Install for the remaining ones that were yet to be applied. Then I get this error:
* Intel Corporation driver update for Intel(R) Control Logic – Error – 0x800f0203
I clicked Retry, it says no updates available.

According to Surface Go, Pro 3, and Pro 4 users, if you’re getting a BSOD after the Surface firmware update, you might be able to fix the problem simply by examining the log file and running a couple of commands in Command Prompt.

To do that, follow these steps:

  1. Open the logfile from c:windowsinf.
  2. Find the error Failed to install device instance.
  3. Above this error, it will say which inf file caused the issue. (example: oem90.inf)

After you find the problematic file, you need to run a single command from Command Prompt. To do that, follow these steps:

  1. Press Windows Key + X to open Win + X menu. Now select Command Prompt (Admin) or PowerShell (Admin) from the left pane.
    Microsoft Surface blue screen of death
  2. Now run pnputil -d oem90.inf command. Of course, if you got a different file, be sure to use that file name in this command.
  3. Close Command Prompt and run Windows Update once again to install the update.

After doing that, the problem should be resolved and you’ll be able to install the update without any issues.

Microsoft’s reaction to this error came only a day later and did not offer specific information:

Thank you for reporting this error message and the difficulty installing recent (4/19/2016). We understand that some customers are experiencing this and we are actively investigating and will provides updates to this thread when available.

2. Enter Safe Mode

If you’re getting BSOD after the Surface firmware update, you might be able to fix the problem simply by entering Safe Mode.

In case you don’t know, Safe Mode is a special segment of Windows that runs with default settings and drivers, so it’s perfect for troubleshooting.

To enter Safe Mode, just do the following:

  1. Open the Settings app. You can do so instantly by using Windows Key + I shortcut.
  2. Navigate to Update & Security section when Settings app opens.
    Surface Pro blue screen of death
  3. Choose Recovery from the left pane. In the right pane, click the Restart now button.
    Surface Book BSOD
  4. You should now see a list of options. Select Troubleshoot > Advanced options > Startup Settings. Now click the Restart button.
  5. After your PC restarts, you’ll see a list of options. Select the version of Safe Mode that you want to use by pressing the appropriate keyboard key.

After you enter Safe Mode, you should be able to troubleshoot the issue. If you can’t boot to Windows at all due to the BSOD, you can enter Safe Mode by doing the following:

  1. Let your PC restart a few times during the boot sequence. If you want, you can restart it manually as well.
  2. Now you’ll see a list of options, like in Step 3 above. Just follow the same instructions and you’ll enter Safe Mode.

Both methods are just as effective, and you can use either of them.

3. Update your video card drivers

BSOD Surface firmware critical process died

According to users, your drivers can sometimes cause BSOD after the Surface firmware update, and in order to fix it, it’s advised that you update your drivers.

To do that, simply visit your graphics card manufacturer and download the latest drivers for your model.

This can sometimes be a complicated task, especially if you don’t know how to find the model of your graphics card, or if you have other outdated drivers on your system.

However, you can easily fix that by using TweakBit Driver Updater software. This tool will automatically update all your drivers, so if you don’t want to search for drivers manually, be sure to try this tool.

Several users are also suggesting to completely remove your graphics card driver before installing the latest drivers.

You can do that from Device Manager, but you can also use tools such as Display Driver Uninstaller to completely remove your drivers.

Once you remove the driver, restart your PC and the default driver will be installed. After doing that, you can update your driver if you want and check if that solves your problem.

4. Remove the DisplayLink driver

remove DisplayLink driver

If you’re getting BSOD after the Surface firmware update, it’s possible that your DisplayLink drivers are causing the issue.

It seems that DisplayLink drivers aren’t fully compatible with Intel drivers, and that is causing the problem to appear.

To fix the problem, be sure to remove DisplayLink drivers from your PC and check if that solves your problem.

Several users reported that the issue was fixed for them after removing the DisplayLink drivers, so we advise you to try that.

5. Perform a System Restore

If you keep getting BSOD after the Surface firmware update, you might be able to fix the issue simply by performing a System Restore.

System Restore will revert any recent changes and fix various issues along the way. To perform a System Restore, do the following:

  1. Press Windows Key + S and type system restore. Now choose Create a restore point from the menu.
  2. Click the System Restore button in System Properties window.
  3. When System Restore window opens, click Next to proceed.
  4. Check Show more restore points option, if it’s available. Select the desired restore point and click Next.
  5. Follow the instructions on the screen to restore your PC.

After your PC is restored, check if the problem is still there.

6. Disable Windows Hello

Windows Hello is a security feature that allows you to sign in to your PC using your fingerprint or by using facial recognition. This is a great security feature, but sometimes this feature can cause issues to appear.

According to users, Windows Hello is the cause for BSOD after the Surface firmware update, and in order to fix this problem, it’s advised to disable Windows Hello.

To do that, just follow these simple steps:

  1. Open the Settings app and go to Accounts.
    Surface Pro 3 blue screen at startup
  2. Select Sign-in options from the menu on the left. In the right pane locate Windows Hello and click the Remove button.

Once you disable Windows Hello, the problem with BSOD should be resolved.

We can only hope that this guide was of use to you. Microsoft Surface is a great device, but many users complain about getting a BSOD after a firmware update and not only.

Keep in mind that when it comes to blue screen errors, the solutions above may be applied to all the common problems reported for Surface devices:

  • Surface Pro blue screen  – There are many reasons for this error and sometimes the cause might be just a single file. To fix it, you just need to find the problematic file and run a quick command in Command Prompt.
  • Surface Pro 4 blue screen – This problem can occur right on startup or in the middle of the process. Once more, use Command Prompt.
  • Surface Go blue screen after update –  This problem can occur on Surface Go as well. If you encounter it, try updating your graphics card drivers or access Safe Mode.
  • Surface Pro 3 blue screen after update – Once again, you know what’s your best bet. Safe Mode alone won’t fix the problem, but it will allow you to investigate the issue. Moreover, there’s a chance that your DisplayLink drivers are causing this problem.
  • BSOD Surface firmware critical process died – Usually, a BSOD error will be followed by an error message. To see how to fix the problem, you’ll have to do a bit of research and see what does the error message means.
  • Surface Book BSOD – BSOD errors can appear on Surface Book as well. If you encounter such an error, try using the solutions from this article.

FAQ: Learn more about Microsoft Surface blue screen issues

  • Why does my Surface Pro keep blue screening?

There can be several reasons behind the Microsoft Surface Pro blue screen issues. Outdated video card drivers and security features such as Windows Hello are both included.

  • What happens to Bitlocker after Windows Surface blue screen?

BitLocker is a special technology that easily encrypts your hard drive while still allowing transparent access to authorized users.

Sadly, it often fails to unlock using the correct key after Windows Surface blue screen errors.

  • How to sign out of the blue screen after a Surface firmware update?

The confirmed solutions from this dedicated guide might help you out; you can use Command Prompt, enter Safe Mode, and not only.

Editor’s Note: This post was originally published in October 2018 and has been since revamped and updated in June 2020 for freshness, accuracy, and comprehensiveness.

Was this page helpful?
Thanks for letting us know! You can also help us by leaving a review on MyWOT or Trustpillot.
Get the most from your tech with our daily tips
Tell us why!
  • I got this error. I was lucky that I had a backup with Rollback Rx so I just restored the computer. Still, this is not a permanent fix, and hopefully Microsoft can solve this problem soon…