A customer came in recently with a mystery. His desktop PC was perfectly fine every morning when he sat down — it was on, Windows loaded, everything looked normal. But he kept finding that files he'd saved the previous afternoon weren't there. Tasks he'd left running overnight had never finished. And once, his accounting software had generated a corrupted report that took him two hours to redo.
He hadn't seen a single crash. Hadn't heard any error beeps. The machine had never once shown him a warning. And yet something was going wrong — repeatedly, silently, invisibly — every few nights.
This turns out to be more common than most people realise. And the reason it's so tricky is precisely because you're not there to see it.
Why Overnight Shutdowns Are So Easy to Miss
Most people assume their computer is either working or obviously broken. But there's a whole category of failures that happen quietly, during off-hours, and then partially recover before you sit back down. The machine restarts itself. Windows boots up cleanly. And unless you were in the middle of something that depended on that session staying alive — a download, a scheduled backup, a rendering job — you'd never know.
What are the most common culprits? In our experience, it tends to be one of these:
- Overheating. PCs and laptops thermal-throttle and eventually shut down when they get too hot. Dust-clogged vents, a failing fan, or dried-out thermal paste on the processor all cause this. It often gets worse as the machine warms up over the course of a day — so a machine that feels fine at 9am may be cutting out at 2am after running for hours.
- A failing hard drive. Older spinning hard drives develop bad sectors and read errors. When Windows encounters one — often during an overnight task like indexing or an automatic backup — it can trigger a crash or corrupt the file it was writing.
- Faulty RAM. Memory errors are notoriously intermittent. They don't cause problems every time, which makes them maddening to diagnose. But they can cause the sort of random, unrepeatable crash that leaves no obvious trace.
- A Windows Update that installs and restarts overnight. This one is often benign — Windows is designed to restart after updates — but if it catches you mid-task, files can be lost and jobs can abort. Many people don't realise this is happening.
- Power supply issues. A failing PSU (the unit inside your PC that converts mains power) can deliver inconsistent voltage under load. It might hold on fine during light daytime use but fail when the processor is working hard at night.
How to Tell If Your PC Has Been Crashing
Windows actually keeps a record of every unexpected shutdown — most people just don't know where to look. Here's a quick way to check:
- Press the Windows key, type Event Viewer, and open it.
- In the left panel, go to Windows Logs → System.
- Look for entries with a red X marked Error or Critical. The ones labelled Kernel-Power with Event ID 41 are the telltale sign of an unexpected shutdown — the system lost power or crashed without a clean restart.
If you see several of those — especially clustered around the same time of night — you're not imagining things. Something is shutting your machine down.
What to Actually Do About It
Some of these are straightforward to fix yourself. Others need a bit more investigation.
Check your Windows Update schedule first. Go to Settings → Windows Update → Advanced Options → Active Hours. Set this to cover the hours you're actually using the machine, and Windows will stop restarting it during that window. It won't stop overnight restarts entirely, but it keeps them out of your working day.
Listen for fan noise. If your PC's fan is running loudly or constantly — or if the case feels warm to the touch even after the machine has been idle — dust and heat are the most likely culprits. A can of compressed air through the vents can help, but if it's been years since the machine was opened and cleaned properly, it's worth having done professionally. Thermal paste on the CPU dries out over three to five years and stops doing its job.
Run a free hard drive health check. If your PC is more than four or five years old and has a spinning hard drive (not an SSD), download CrystalDiskInfo — it's free and takes about thirty seconds to read the drive's built-in health data. If it shows anything other than "Good," take it seriously. A data recovery job after a failed drive is far more expensive and stressful than an SSD upgrade before it fails.
Don't leave critical files unsaved overnight. This is just good hygiene regardless of what's causing the problem. If your work matters, save it and ideally have it backing up to an external drive or cloud storage automatically. An overnight crash that loses a single afternoon's work is frustrating. One that loses an unfinished project you've been building for a week is genuinely awful.
The Bit Most People Skip
Here's the thing: because these shutdowns happen when you're not watching, most people put up with the symptoms — the missing file, the unfinished job, the mysteriously corrupted document — without ever connecting them to a hardware fault. They blame themselves. They assume they forgot to save. They redo the work and move on.
Meanwhile, the underlying problem gets worse. A drive that's developing bad sectors doesn't get better. An overheating machine runs hotter each time. The crashes that happen once a fortnight start happening twice a week.
If something feels off — files disappearing, overnight tasks never finishing, a PC that seems fine but keeps producing strange results — it's worth a proper look before the problem becomes a crisis. The Event Viewer trick above is a genuinely useful first step. But if you're seeing Kernel-Power errors and aren't sure what to do next, that's exactly the kind of thing we diagnose every week at Advantec's PC repair bench.
Silent problems are still problems. They're just quieter about it.