PC Blue or Black Screen Right After an Update: Your First 30 Minutes
In plain English: If your PC shows a blue screen or a black screen right after a Windows update, do not try random fixes. The timing points to that update, a driver it changed, or a file it replaced.
First safe step: First, write down the stop code exactly as shown, or note that there is no code on a black screen.
If your PC shows a blue screen or a black screen right after a Windows update, do not try random fixes. The timing points to that update, a driver it changed, or a file it replaced. Work in order for the first 30 minutes, and stop if the screen changes.
This triage page sits inside the plain English guide to blue screen and black screen stop codes. It does not repeat the fixes for each code. Instead, it helps you capture the code, get to recovery safely, and then follow the one page that owns your fix.
First, write down the stop code exactly as shown, or note that there is no code on a black screen. Next, reach the recovery screen without forcing repeated shutdowns. Then roll back the recent update, quality update first, before trying anything else.
Part of the Blue Screen and Black Screen Stop Codes in Plain English series, the pillar guide for this cluster.
First, work out which screen you are actually looking at
A real blue screen takes over the whole screen. It says 'Your device ran into a problem;' and that it is gathering information, then the PC restarts on its own. It may show a stop code near the bottom, and it never shows a support phone number.
A black screen is not one single problem. Spinning dots mean Windows is still trying to load. A screen stuck on the maker logo, such as Dell or HP, stops before Windows loads at all. Each one points to a different next step, so note which one you see.
A black screen where you signed in and can move the mouse is different again. The desktop has not loaded, even though Windows partly has. For that case, follow the separate route for a black screen with a cursor after you sign in, rather than the rollback steps later on this page.
Treat any blue screen that appears inside a browser window, or that carries a phone number, as fake. Do not call the number, click links on it, or pay anyone it names. Check how to tell a fake blue screen with a phone number from a real one before you do anything else.
Write down the stop code before the screen disappears
If the blue screen is still showing, take a phone photo before you touch anything. Get the whole screen in frame, close enough that the text stays sharp, and take a second photo if glare hides part of it.
Check that the photo is readable before the screen restarts. It should show the stop code name in capital letters, any hex code shown with it, and any driver or file name listed under 'What failed;'. Keep every letter of a name ending in .sys, as one wrong letter points to a different file.
Next, write down when it happens, in plain words beside the photo. Note if it happens on every start, only after you sign in, in a loop back to the same screen, or once after an update had just finished. That timing helps decide the next route, so do not rely on memory later.
On a black screen, write down what is missing instead. Note that there is no stop code, whether you can see a cursor or no cursor at all, and whether the maker logo appeared first. A cursor after sign in matters, because it follows the separate route for a black screen with a cursor after you sign in.
Match the code to the page that owns its fix
Use the name from your photo, spelled exactly as the screen showed it. Start with the two codes that show up most often right after an update in this list. If yours points to a driver, follow the driver route for IRQL_NOT_LESS_OR_EQUAL after an update. If Windows cannot reach its own drive, follow the drive route for INACCESSIBLE_BOOT_DEVICE.
If the code names a stopped system process, see what to do when the stop code reads CRITICAL_PROCESS_DIED. For a memory crash, use the memory checks behind a MEMORY_MANAGEMENT crash, and for a crash that starts as a long freeze, read why DPC_WATCHDOG_VIOLATION freezes before it crashes.
Timing you noted in the last section is what separates this route from a general driver crash. One code depends on timing as much as on the name. If the crash happens when the PC sleeps, wakes, or is opened again, take the sleep and wake route for DRIVER_POWER_STATE_FAILURE, even if the update finished hours earlier.
If your code is not listed here, or your black screen showed no code at all, do not pick the closest match. Go back to the full stop code guide, find the exact name or the no code route there, and follow that page instead of guessing. That keeps one exact route in front of you.
Get to the recovery screen without making things worse
Turn the PC on once and let it run. Do not hold the power button down, unplug it, or keep pressing keys while Windows tries to restart and repair itself. That first attempt often ends on its own at the recovery screen, and cutting the power short can leave you with the same crash again.
Watch for a blue screen headed 'Choose an option;'. That is the recovery screen. From there, the next screen you need is Advanced options, where the update rollback sits. Do not select an option just to see what happens next. If the wording looks unfamiliar, read what every option on the Your PC did not start correctly screen means before you select anything.
If instead the PC restarts, crashes, and starts over in a loop, do not keep forcing it off at random. Follow starting Windows in Safe Mode when your PC will not boot for the timed interruption method, and see getting out of an automatic repair loop safely if repair keeps repeating without reaching recovery.
If a BitLocker screen appears instead, stop there. Do not guess the key or keep restarting. Use finding your 48-digit BitLocker key if the recovery screen asks for it, then return to recovery. And leave 'Reset this PC;' alone for now. It is not a first 30 minutes step.
Roll back the update from recovery, in the right order
You are already on the Advanced options screen from the last step. Select 'Uninstall updates;'. This is the recovery route built for this exact timing, a crash that began right after an update, and it works even though the desktop will not load, so use it before you try other recovery tools in these first 30 minutes.
Choose one target only, not both in a row: if the crash followed a recent monthly update, choose 'Uninstall latest quality update;'; if it followed a big version change, one that gave your PC a new look or added new features, choose 'Uninstall latest feature update;'. If you cannot tell which type just installed, start with the quality update.
Before you confirm, plug the PC in and leave it plugged in until the process has finished. Expect at least one restart and a wait while Windows removes the update, and do not cut the power to hurry it along. Keep a phone or another PC handy for finding your 48-digit BitLocker key if the recovery screen asks for it.
For the screens that follow your choice, follow the full guide to uninstalling a bad Windows update and when not to. That guide covers the full steps, the cases where an update should stay in place, and how to pause updates so the same one does not come back at once. Stay with that one route until Windows either loads again or returns to recovery.
If Windows comes back, or if the screen comes back too
If Windows loads to the desktop, do not install anything again yet. Start with reading your update history to find the failed update and its code, then write the KB number on the same note you kept with your photo.
Keep that photo, your timing note, and the KB number together. If the desktop stays up after the rollback, that record points to the update you removed as the likely cause, and it gives the next page you open the exact code to work from.
If the same blue or black screen returns, do not repeat the rollback and hope for a different result. Return to the stop code in your photo and follow the matched page for that code, where the next steps for that fault are set out.
If the PC now restarts into the same repair screens again and again, your next step is getting out of an automatic repair loop safely. If, after you sign in, all you see is a cursor on a black screen, your next step is the separate route for a black screen with a cursor after you sign in. Both routes start from the photo and note you kept.
Conclusion
A crash that starts minutes after an update gives you one useful clue before anything else: timing. Keep that clue, and the photo and note you made from it, and you have a clear record for whichever page you follow next, whether Windows is back or the fix is still ahead.
Do not start over with a new search or a new fix each time the screen returns. One code, one rollback, and one result tell a cleaner story than ten tries at once, and that story is what points you, or anyone helping you, to the right next step.