Margaret runs a small pottery business from home. She takes orders online, manages her accounts in a spreadsheet, and prints her own shipping labels — nothing exotic, just a mid-range Windows laptop doing everyday work. She'd had it about four years without a moment's trouble. Then, a few months ago, it started crashing.
Not constantly. Not randomly. Predictably. Almost always on a Tuesday morning, usually sometime between nine and eleven. The screen would freeze, sometimes go blue for a split second, and then the machine would restart. By the time she came to us, she'd lost unsaved work three times and was genuinely worried the laptop was on its way out.
What She Thought Was Wrong
Margaret had done what most people do: she'd Googled the symptoms. The results pointed her towards hard drive failure. A few forums mentioned overheating. One rather alarming thread suggested a virus. She arrived half-expecting us to tell her the laptop was beyond saving and that she'd need a new one.
She'd also noticed — and this is the detail that turned out to matter — that the crashes always seemed to happen when she was in the middle of something. Never when the laptop was just sitting idle. Always when she was actively working.
What We Found on the Bench
We started with the obvious checks. The hard drive passed its diagnostics without complaint — no bad sectors, no signs of imminent failure. Temperatures were absolutely fine; the cooling fan was clear, the vents unblocked. A virus scan came back clean. The RAM tested fine too.
So we dug into the Windows Event Viewer — a built-in log that records everything that happens on a PC, including exactly what was going on in the seconds before a crash. This is often where the real story lives, and most people never look at it.
The crash logs pointed to a conflict during a background process called Windows Update. Specifically, the update service was downloading and staging a large update in the background, hogging disk and CPU resources, and when Margaret opened her accounts spreadsheet — which is a moderately demanding file — something tipped the system over the edge. The laptop simply couldn't juggle both at once.
Then came the "Tuesday" penny-drop moment. Windows Update, by default, checks for and downloads updates on a schedule — and on her laptop, that schedule happened to fall on Tuesday mornings. She'd never changed it. Why would she? She didn't even know it existed.
Why This Is More Common Than You'd Think
This kind of thing walks through the door more often than you might expect. The symptoms — crashes, freezes, sudden slowdowns — sound alarming. The natural assumption is hardware failure. But a surprisingly large proportion of these cases turn out to be software behaviour: a scheduled task fighting for resources at exactly the wrong moment.
Windows does a lot of things in the background without ever really telling you. As well as updates, it runs:
- Automatic backups (if you have Windows Backup or OneDrive sync turned on)
- Antivirus scans, often scheduled for a fixed time each week
- Disk indexing, which can be surprisingly heavy on older machines
- Telemetry and diagnostic uploads to Microsoft
On a newer, more powerful machine with plenty of RAM and a fast SSD, all of this usually happens invisibly. On an older laptop — especially one with a traditional spinning hard drive — it can bring everything to a grinding halt. Or worse, trigger a crash if the system is already under pressure.
How We Fixed It
The fix had a few parts. First, we changed the Windows Update schedule so that updates download and install outside of Margaret's working hours — late evening, when the laptop is plugged in but she's not using it. This is something anyone can do, and it takes about two minutes.
Second, we noticed the laptop still had its original spinning hard drive. We recommended — and she agreed — to upgrade it to an SSD. This isn't always the right answer, but in her case it made a real difference: the new drive is fast enough that even when Windows Update is doing its thing in the background, the laptop barely notices. What used to be a resource tug-of-war became a non-event.
Finally, we adjusted the antivirus scheduled scan to run at the same quiet time as the updates. No point having two heavy background tasks fighting each other either.
She took the laptop home on a Thursday. The following Tuesday morning, she sent us a short email: "It just... worked."
The Practical Takeaway
If your computer crashes, slows down, or behaves strangely on a suspiciously regular schedule — same time of day, same day of the week — don't immediately assume the worst. Hardware failure is rarely this punctual. Before you panic, ask yourself: is there a pattern? Does it always happen when you're doing something specific, or at a particular time?
A few things worth checking yourself:
- Open Settings → Windows Update and see when updates are scheduled. You can change the active hours so Windows knows not to do its housekeeping while you're working.
- Check your antivirus software for a scheduled scan setting — most let you pick a convenient time.
- If your laptop is more than three or four years old and still has a spinning hard drive, an SSD upgrade is often the single most cost-effective improvement you can make.
And if you've looked at all of that and you're still none the wiser, bring it in. Sometimes what looks like a drama turns out to be a scheduling quirk that took us twenty minutes to untangle. Better to know than to spend months dreading Tuesdays.