Troubleshooting

Computer keeps crashing? Find out what actually stops.

Before trying a repair, protect your files and write down the failure you see. Then check cooling, recent changes and hardware results in a controlled order.

By Rajan Maharaj, Co-Founder  •  23 October 2026  •  7 min read

Troubleshooting a computer that keeps crashing or restarting unexpectedly

Follow the symptom on your Windows computer

A program closing, a frozen screen and a complete loss of power are different failures. Record which one happens and use the checks below to narrow the cause. The Settings paths shown are for Windows 11; ask for help if your Windows menus differ.

Step 1 of 9

In this guide
  1. 01Protect files and check whether it is safe to continue
  2. 02Record the failure and try one normal restart
  3. 03Check ventilation and temperature readings
  4. 04Update and check it with the manufacturer's app
  5. 05Review one change that fits the timing
  6. 06Read Device Manager’s status and driver details
  7. 07Run a scan with the active security product
  8. 08Match Windows events to the recorded time
  9. 09Record a stop code and arrange the next check

Protect files and check whether it is safe to continue

Put data and physical safety ahead of another test.

  1. If Windows runs reliably enough, save copies of essential documents to suitable external storage or your cloud account before changing anything. Check that the copies open.
  2. Pause nonessential work while the crashes continue. Avoid long disk repairs until the important files are secure.
  3. Stop for clicking from a drive, a burning smell, unusual heat or recurring power loss. Shut down and arrange assessment; repeated restarts can make preservation harder.
  4. If the computer is too unstable to copy files safely, ask for help with the data before continuing.

Continue only when the files are protected and there is no safety concern. Otherwise use the help section.

Next: Record the failure and try one normal restart

Record the failure and try one normal restart

Describe the interruption before changing the setup.

  1. Write down whether one program closes, Windows freezes, the computer restarts, all power goes off, or only the display goes dark.
  2. Note the error wording, time and task: starting Windows, waking from sleep, gaming or ordinary work. Include recent software, driver, update or hardware changes.
  3. Save open work and restart normally if the computer is safe to use. Observe a light everyday task after it starts; avoid deliberately provoking another failure.
  4. To compare a newly added accessory, shut down first and disconnect that nonessential USB device or dock. Finish transfers before disconnecting storage, and keep required power, input and display connections.
  5. Note whether the crash occurs before Windows starts and whether the fans appear to run. A dark screen by itself does not establish that the whole computer lost power.

If normal use stays stable, keep the notes and monitor. Repeated failures continue to the cooling check.

Next: Check ventilation and temperature readings

Check ventilation and temperature readings

Observe cooling without opening the computer.

  1. Shut the computer down before checking its exterior. Disconnect external power before clearing accessible dust from vents, following the manufacturer’s cleaning advice.
  2. Leave space around the vents and use a portable computer on a firm, flat surface. Keep bedding, cushions and enclosed spaces away from its airflow.
  3. When it is safe to run again, note unusual fan noise or heat. Do not open the case just to inspect internal fans, or put anything into a vent.
  4. If the computer is stable enough, get HWiNFO from its official site and use its sensor monitoring to record CPU/GPU temperatures during ordinary use.
  5. Keep the readings and the time of any interruption. A temperature spike needs interpretation for the specific hardware; it does not identify a failed part by itself.

This app is made and managed by its vendor, not Call IT Mate. We can't take responsibility for any changes it makes to your system.

Intact desktop tower with clear space around its front ventilation on a white desk

Stop if heat or power loss returns. If the setup is safe and the crash persists, update and check it with the manufacturer's app.

Next: Update and check it with the manufacturer's app

Update and check it with the manufacturer's app

Make sure all software is up to date, then run the hardware checks.

  • Open your computer manufacturer's support app, or get it from the manufacturer's official support site for your model. For example, Lenovo has Lenovo Vantage.
  • Run the app's update check and install the updates it offers for your computer, so drivers and system software are up to date. Restart if it asks you to.
  • Then run the hardware checks. In Lenovo Vantage, use Hardware scan; some versions place it under Device diagnostics or Support.
  • For supported Dell computers, Dell SupportAssist provides hardware diagnostics. On supported HP computers, HP Support Assistant provides tests under Fixes & Diagnostics.
  • Save any failure code and test name. If a test fails, or the computer shuts off during updates or tests, stop and arrange support.

This app is made and managed by its vendor, not Call IT Mate. We can't take responsibility for any changes it makes to your system.

A failure goes to hardware support. If no failure is reported but unexplained crashes continue, use the memory check.

Review one change that fits the timing

Compare evidence before removing software or an update.

  1. Match the start of the crashes with a particular application, Windows update, driver or accessory. Make one justified change at a time so you can judge the result.
  2. For a newly installed application you no longer need, use Settings → Apps → Installed apps. Find that app, select its More options (…) menu and choose Uninstall. Follow its prompts.
  3. For a Windows update, first review Settings → Windows Update → Update history. Removal is for a specific suspected update, not routine cleanup.
  4. If removal is justified, select Uninstall updates, find that update and use Uninstall if available. Understand the security implications before removing a security update; ask for advice if unsure.
  5. Restart and compare normal use after the change. Record any performance-profile or BIOS changes for support rather than changing unfamiliar firmware settings.

If it still crashes, inspect the relevant device and driver. A stable result should be monitored rather than followed by unrelated removals.

Next: Read Device Manager’s status and driver details

Run a scan with the active security product

Malware is one possibility, not a diagnosis from crashing alone.

  1. Use the trusted protection already responsible for the computer and bring its definitions up to date. On a managed computer, involve the responsible IT team before changing security software.
  2. Where Microsoft Defender Antivirus is active, open Windows Security → Virus & threat protection → Scan options. Choose Full scan → Scan now.
  3. Read the scan result and complete the advised threat response. If another antivirus manages protection, use its documented scan process rather than disabling it to expose Defender’s controls.
  4. For suspected persistent malware, Microsoft Defender’s Offline scan is another option under Scan options. Save and close work first: it restarts the computer and scans outside the normal Windows session.
  5. After an offline scan, read Protection history in Windows Security. If scanning fails or security products appear to conflict, ask for help rather than turning protection off.

Keep any detection and action details. A clean scan is not proof that the cause of a crash has been fixed.

Next: Match Windows events to the recorded time

Match Windows events to the recorded time

Keep useful evidence without diagnosing hardware from one warning.

  1. Right-click Start and choose Event Viewer. Expand Windows Logs and select System.
  2. Look around the time of the interruption you recorded. Note repeated critical, error or warning entries and the messages just before the failure.
  3. Kernel-Power 41 records an unclean shutdown. It can follow power loss, a crash or a forced shutdown and does not establish that the power supply is defective.
  4. Keep the exact text of display, disk, NTFS or WHEA-related entries for support. These are leads for investigation, not instructions to replace the named component.

Retain the events and timestamps. Do not clear the logs or assume the final event caused the crash.

Next: Record a stop code and arrange the next check

Record a stop code and arrange the next check

Bring the test results when the interruptions continue.

  1. If Windows shows a stop error, record its exact code and any driver filename. Use our blue-screen troubleshooting guide for that path rather than guessing from the code.
  2. If normal use is now stable, keep backups current and monitor the original symptom. One successful session cannot confirm an intermittent failure is gone.
  3. For another crash, a failed hardware test or an uncertain result, give Call IT Mate the symptom log, recent changes and the checks already completed.
  4. Stop sooner for recurring power loss, unsafe heat, a burning smell or drive clicking. Arrange hardware or data-preservation help before more repair attempts.

Keep your notes and saved files available for the next assessment.

Book IT support

Frequently asked questions

What should I do before troubleshooting repeated Windows crashes?

Protect important files while the computer can copy them safely. Stop testing for a burning smell, unsafe heat, recurring power loss or drive clicking, and arrange help before repairs.

Can my computer manufacturer’s app check the hardware?

Supported Lenovo, Dell and HP computers have vendor diagnostic options described in this guide. Use the app and instructions for your model, keep failure codes, and stop if the test fails or the computer loses power.

Does Kernel-Power 41 mean I need a new power supply?

That event records that Windows did not shut down cleanly. Compare the time with the symptom and nearby events before deciding what hardware or software needs investigation.

Should I remove every recent update if Windows keeps crashing?

Compare the first failure with a specific change and make one justified change at a time. Some updates cannot be removed, and security-update removal needs a clear reason and an understanding of the risks.

More practical IT guides

View all guides

Share this guide