Your screen suddenly turns bright blue — or these days, black — and fills up with a wall of unfamiliar letters and numbers. This is what’s known as a blue screen. In most cases the screen shows a line of text called a stop code, and that’s your first clue for working out what went wrong. But a blue screen doesn’t automatically mean your PC is broken. In this article we’ll walk through it step by step: the types of causes, how to investigate, what you can fix yourself, and when it’s time to send it in for repair.
What Is a Blue Screen? And Why It Might Not Be Blue Anymore
A blue screen — officially called a stop error or bug check — is what happens when Windows detects a serious problem and shuts down as an emergency measure. It’s also widely known as the Blue Screen of Death, or BSOD. What the operating system is actually doing is deciding that carrying on would be risky, so it halts everything to keep your system safe. It doesn’t necessarily mean something is broken — sometimes a simple restart puts everything back to normal.
There’s also one thing that’s changed over the past couple of years. Around July 2025, Microsoft began rolling out an update that switches this stop screen to a simpler design with a black background, and its support pages now use both “blue screen error” and “black screen error.” So if you searched for “blue screen” and landed on this article while your own screen was actually black, that’s nothing unusual. Microsoft hasn’t officially confirmed whether the change has reached every setup, but blue or black, you can treat the way you diagnose and fix it as more or less the same.
The Main Causes of Blue Screens on Windows 11
According to Microsoft’s technical documentation, about 70% of blue screens are caused by third-party drivers and around 10% by hardware problems, while Windows’ own code is behind only about 5% of cases. The remaining 15% are cases where the cause is hard to pin down. In other words, most of the time the problem isn’t a fault in the machine itself, but a compatibility issue with software or peripherals you’ve added later on. Below we’ll go through the causes you’ll actually run into most often, starting with driver faults — by far the most common.
Driver Faults
The most common cause is a fault in a driver — the software that controls peripherals, graphics cards and the like. A driver connects your hardware to Windows, and if an update fails, or an old version ends up paired with a newer build of Windows, an error can occur deep in the core of the system. If blue screens started happening right after you updated your graphics driver, or after you plugged in a new printer or mouse, this is the likely culprit. Stop codes such as IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION also tend to point to a driver being involved.
Compatibility Problems After a Windows Update
If blue screens picked up right after you applied a Windows update, there may be a compatibility clash between the update and your existing drivers or software. With big feature updates in particular, it’s not unusual for peripheral drivers to lag behind and not fully support the newer version of Windows. If everything ran fine before the update but the symptoms started afterwards, this timing gap is the first thing to suspect. Rolling back the update or reinstalling the driver in question can sometimes clear it up.
Memory (RAM) Problems
When there’s a fault in your memory, you may see stop codes like MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA. One telltale sign is that it tends to happen at random rather than only during a particular task. The cause can be a compatibility issue with added memory or simple wear over the years, and mixing modules of different specifications makes errors more likely under load. If you suspect memory, remove any modules you’ve added and check whether the symptoms continue with the standard setup. The Windows Memory Diagnostic tool covered below is handy for narrowing this down.
SSD and Storage Issues
Worn or faulty storage can trigger stop codes such as INACCESSIBLE_BOOT_DEVICE. It tends to show up during startup or while reading and writing large files. Very low free space can cause the same symptoms, so start by checking how much room you have left.
CPU Temperature and Poor Cooling
If blue screens only happen when you’ve been running demanding tasks for a while, a rising CPU temperature from poor cooling is worth suspecting. When the stop code is WHEA_UNCORRECTABLE_ERROR, the cause is often hardware stability — heat, voltage and the like. Mini PCs and slim laptops in particular have limited space inside, so they tend to have less headroom for cooling. If it only happens during heavy work such as gaming or video editing, this is a possibility to keep in mind.
Peripheral Conflicts
Peripherals such as external hard drives, USB hubs and webcams are behind the problem more often than you’d think. If the symptoms only appear when a particular device is connected, unplug it and see how things go. It’s the easiest test to try when you’re isolating a cause.
Security Software Conflicts
Third-party security software can clash with your system and lead to a blue screen. In 2024, a fault in CrowdStrike’s security product Falcon caused stop codes 0x50 and 0x7E on Windows machines around the world. If this sounds like it might apply to you, update your security software to the latest version, and if that doesn’t help, try temporarily disabling it to see whether the symptoms change.
Likely Causes by Symptom, and What to Check First
| Symptom | Likely cause | What to check first |
|---|---|---|
| Happens right after startup | Storage issues, or a mismatch after a Windows update | Check whether you updated just beforehand |
| Happens while using a particular program or after connecting a peripheral | Driver faults, or a peripheral conflict | Unplug whatever you connected most recently |
| Happens during heavy tasks (gaming, video editing, etc.) | Poor cooling, or faulty memory | Switch to lighter tasks and see how it goes |
| Happens at random, regardless of time or task | Faulty memory | Run the Windows Memory Diagnostic |
| Keeps restarting and won't boot | Storage issues, or corrupted system files (damage to files Windows needs to start) | Try booting into Safe Mode |
How to Investigate the Cause of a Blue Screen
By default, Windows 11 restarts automatically right after a stop error. It's common for the screen to disappear before you've had a chance to look into the cause, so snapping a photo with your phone while the stop code is on screen will make the steps that follow a lot smoother.
Start by Sorting One-Offs from Repeat Offenders
A one-off is usually just a temporary clash between processes, and if everything works fine after a restart, there's not much to worry about. If the same symptom keeps coming back over a short period, though, there's a good chance something more fundamental is going on with a specific piece of hardware or a driver. Keep that distinction in mind as you move on to checking the stop code next.
Check the Stop Code
The stop code is the string of text on the stop screen made up of capital letters and underscores (for example, MEMORY_MANAGEMENT). Microsoft's technical documentation sets out the typical causes for each code. Use the quick-reference table below to get a sense of the cause from the code you saw.
| Stop code | Main cause | What to check first |
|---|---|---|
| MEMORY_MANAGEMENT | Faulty memory or a memory-management error | Remove any added memory and check |
| IRQL_NOT_LESS_OR_EQUAL | A memory-access error caused by a driver | Check any driver you recently updated or added |
| PAGE_FAULT_IN_NONPAGED_AREA | Corrupted memory or a driver problem | Run a memory diagnostic and check your drivers |
| SYSTEM_SERVICE_EXCEPTION | A fault in a driver or system process | Check recently added software or drivers |
| WHEA_UNCORRECTABLE_ERROR | Instability in hardware such as the CPU or memory | Check temperatures and cooling |
| KERNEL_SECURITY_CHECK_FAILURE | Corrupted kernel data or memory | Update drivers or roll back to an earlier state |
| CRITICAL_PROCESS_DIED | An important Windows process shut down unexpectedly | Consider a System Restore |
| DPC_WATCHDOG_VIOLATION | A delay in driver processing | Update the driver responsible |
| VIDEO_TDR_FAILURE | The graphics driver stopped responding | Update or roll back the GPU driver |
| INACCESSIBLE_BOOT_DEVICE | A problem with storage or boot settings | Check your SSD/HDD connection and settings |
*For more detailed explanations, see Microsoft's technical documentation.
Check in Event Viewer
If you missed the stop code, you can check the log from when the blue screen occurred in Event Viewer.
- Search for Event Viewer in the Start menu and open it.
- Open Windows Logs → System.
- Click Filter Current Log on the right and select Critical or Error.
- Check whether Event ID 1001 (WER-SystemErrorReporting) or 41 (Kernel-Power) has been logged.
1001 usually records that a blue screen occurred, while 41 often points to an abnormal shutdown or sudden restart — both help you narrow down the cause.
Use the Windows Memory Diagnostic
If the stop code or Event Viewer log points to memory, use the memory diagnostic tool built into Windows. Type "memory" into the taskbar search box and select Windows Memory Diagnostic. Choose "Restart now and check for problems," and your memory will be checked automatically when the PC restarts.
How to Fix a Blue Screen
Once you've got a sense of the cause, it's time to actually fix it. If software is to blame, you can often sort it out yourself; if hardware is the suspect, you'll need to weigh things up more carefully. And if it's happening so often that the PC won't even start, the steps themselves change.
Fixing a Software Cause
- 🔄 Happens after a driver update → Roll back the driver. Revert to the previous driver from Device Manager.
- 🪟 Happens after a Windows update → Uninstall the update. Reapply it once the fault is resolved.
- 🛠 Cause unknown → Run System Restore. Return to the state before the symptoms started.
If a driver looks like the cause, try a rollback. Open Device Manager, right-click the device in question and choose Properties → the Driver tab → Roll Back Driver. If this option is greyed out, there's no rollback data left, so try reinstalling the latest version instead.
If the symptoms started after a Windows update, the safe approach is to uninstall the update in question and reapply it once Windows has settled down.
If you can't narrow down a single cause, or several changes have piled up at once, System Restore is a good option. Go to Control Panel → Recovery → Open System Restore, or press Win+R and run rstrui.exe, then roll back to the state before the symptoms appeared.
Spotting and Handling a Hardware Cause
If the stop code is one tied to hardware stability, such as WHEA_UNCORRECTABLE_ERROR, or if you've worked through the software fixes without any improvement, it's worth suspecting the hardware. With added memory or cables, simply removing and reseating them can sometimes clear a loose connection. It's also worth checking whether dust has built up inside.
If it keeps coming back after you've tried all this, we wouldn't recommend taking things apart any further on a hunch. For a fault in an individual part, talking to one of the repair services covered in the next section often works out cheaper in the end.
When It Happens Constantly or Keeps Restarting Without Booting
If Windows won't start normally, boot into Safe Mode from the Windows Recovery Environment (WinRE) to isolate the cause.
- Start WinRE. (Interrupt the boot twice, or go to Settings → Recovery → Restart now.)
- Select Troubleshoot → Advanced options.
- Click Startup Settings → Restart.
- Press 4 or F4 on your keyboard to boot into Safe Mode.
Key check: if everything runs fine in Safe Mode, the cause most likely lies with a driver or software.
Rough Repair Costs and When to Consider Replacing
When hardware is behind a blue screen, the fix broadly splits into three paths. Parts like memory, an SSD, or a GPU (on a desktop) you can swap out yourself, which works out a fair bit cheaper than paying a technician. Many of GEEKOM's mini PCs open with no tools or a single screwdriver, and nothing in the official warranty terms says the warranty lapses purely because you've opened the case. A CPU can be replaced too, though socket compatibility and the like make it a touch harder. It's also worth remembering that most GPU-related blue screens come down to a driver problem, and with a CPU, unstable voltage can lead to the stop code WHEA_UNCORRECTABLE_ERROR — so poor cooling isn't always the only culprit.
The motherboard and data recovery, on the other hand, are best left to the professionals rather than tackled yourself. A fault in a GPU soldered directly onto the board is also treated as a motherboard repair. And if you can't get your data off the drive, the wrong move can make things worse, so talk to a specialist service.
If the repair bill starts creeping towards the price of a new machine, replacing it is worth a look — though it's worth knowing your rights first. Under the Australian Consumer Law, products come with automatic consumer guarantees, including that they'll be of acceptable quality and last a reasonable time for the price you paid. If a serious fault shows up sooner than you'd reasonably expect, you may be entitled to a repair, replacement or refund, so check with the retailer or manufacturer before paying for repairs yourself.
See the table below for specific price guides. (Independent repair shops often don't publish their rates, so they're not included.)
Repair Cost Guide by Symptom
| Symptom / repair | Rough cost (AUD) | When to consider replacing |
|---|---|---|
| Diagnosis / quote only | Around A$70 | — |
| Memory replacement | DIY: from A$155 (DDR5 from around A$410); Manufacturer: from around A$620 | When wear or compatibility issues keep recurring |
| SSD / HDD replacement | DIY: from A$90; Manufacturer: from around A$620 | When there are faults beyond storage as well |
| GPU replacement | DIY: cost of the card only; Shop: A$36–115 + parts | — |
| CPU replacement | DIY: from around A$410 to about A$1,240; Shop: A$52–115 + parts | — |
| Motherboard repair / replacement | Manufacturer replacement: A$620–720-plus; PC Dock 24: from A$70 (parts extra) | When the repair cost is more than half the price of a new unit |
| Data recovery | Logical failure, minor: around A$515; Physical failure, minor: from around A$2,060 (severe cases quoted individually) | When recovering data matters more than repairing the PC |
*Prices are based on information published by manufacturers, major repair chains and leading retailers as of July 2026. Parts and labour costs may change over time.
Everyday Maintenance to Prevent Blue Screens
For prevention you can build into your routine, the basics start with keeping your drivers and Windows updates up to date. Since most causes cluster around these two, simply not letting updates pile up already lowers your risk. Very low free storage can also lead to a blue screen, so keep some room spare. Dust in the vents drags down cooling efficiency, so mini PCs and laptops in particular are worth cleaning out from time to time. Not adding too many peripherals or security programs also helps head off unexpected conflicts.
FAQ
Is it OK to force a shutdown?
If the screen is frozen and nothing responds, it's fine to hold down the power button to switch it off. Once a blue screen is showing, Windows has already stopped and effectively said "I can't go any further," so forcing a shutdown from there won't break anything. That said, if you see something like "Preparing automatic repair," recovery work is running in the background — that's the one time to sit tight and let it finish rather than rushing.
Is it OK to just leave a blue screen alone?
If it only happened once and the PC has been running normally since, there's no need to panic. It's often just a temporary clash between software or drivers, so if a restart sorted it, keeping an eye on it is fine for now. Just make sure you note down or photograph the stop code. If the same symptom keeps coming back, we'd recommend narrowing down the cause sooner rather than later, using the "How to Investigate the Cause" and "How to Fix" sections of this article.
What causes frequent blue screens on Windows 11?
The most common one is a driver fault — Microsoft's figures put about 70% of cases here. If they suddenly picked up after a Windows update in particular, there's a good chance the update and your existing drivers have fallen out of step. If you get the sense something's off, checking the stop code first is the quickest way in. Once you know the code, the quick-reference table in this article will point you towards the cause.
Do blue screens happen on mini PCs too?
They certainly do. Inside, it's a Windows PC like any other, so driver, memory and storage problems are exactly the same as on a desktop or laptop. Because the case is compact, it's worth being a little more mindful of cooling. Dust in the vents makes it easier for heat to build up, so even an occasional clean-out makes a real difference.
