A blue screen with a stop code, or a computer that simply locks up with no warning at all, are two versions of the same underlying problem: something made Windows unable to keep running safely. The code on screen is a clue, not the full answer. What actually tells us what happened is the memory dump Windows saves at the moment of the crash.
Working out which one you've got
Crashes that keep naming the same driver, or that started right after installing something new, point at software, a bad driver, a conflicting program, or a Windows update that didn't land cleanly. Crashes that happen at random, with no pattern, especially alongside a hot-running machine or one that's been dropped, point more toward failing memory or another hardware fault. See our overheating and fan repair page if heat looks like part of the picture.
How we actually diagnose it
-
Pull the crash logs remotely
Windows keeps a record of what was running and what failed. We read that first, not just the code on screen.
-
Look for a pattern
Same driver every time, or completely random, changes what we check next.
-
Fix what's fixable remotely
Driver conflicts and software causes are usually sorted in a single remote session.
-
Book on-site if it's hardware
Failing memory or another component needs hands on the machine, and we'll tell you plainly if that's where this is heading.
What it costs
$150 per hour. Diagnosing the crash and fixing a software cause is usually one session. If it turns out to be memory or another hardware fault, we'll quote the part separately before doing anything further.
Common questions
What does the error code on the blue screen actually mean?
It names the specific type of failure Windows detected, a driver conflict, a memory error, a corrupted system file, among others. Windows also saves a memory dump of what was happening at the moment of the crash, which is what we actually read to diagnose it, not just the code on screen.
Is this a hardware problem or a software one?
Could be either, and that's exactly what the crash dump tells us. A pattern of crashes tied to one specific driver or program points at software. Crashes that happen randomly under any kind of load, especially paired with overheating or a computer that's been dropped or knocked, point more toward failing memory or a hardware fault.
Can this be diagnosed without bringing the computer in?
Often, yes, the first pass at least. We can remotely pull the crash logs and memory dump and narrow down the likely cause. If it turns out to be a hardware fault, like failing memory, that part of the fix does need a technician on-site.
My computer just freezes completely, no blue screen at all. Is that different?
It's a close cousin. A full freeze with no crash and no error usually points at the same kind of causes, overheating, a failing component, or a driver that's hung rather than crashed cleanly, and we investigate it the same way.