PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To find out why your Windows 11 PC crashed, first record the exact stop code and any “What failed” module shown on screen. Then check Event Viewer’s System log for events at the same time, and run Windows Memory Diagnostic if memory is a plausible cause. These clues can narrow the search, but a stop code or nearby log entry alone does not prove what caused the crash.
1. Capture the crash details before troubleshooting
When Windows shows a blue screen or unexpected restart, note the time and what the computer was doing. Record whether it froze, restarted on its own, or displayed a stop code. If the screen disappears too quickly, take a photo.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Tech-Shop-pro Compatible with install Key Included USB For Windows 11 Home OEM Version 64 bit.... | $48.00 | Buy on Amazon |
- Write down the exact stop code.
- Record any module named after “What failed,” if one appears.
- Note recent changes, such as a new device, driver, update, or app.
- Describe what happened immediately before the crash and whether Windows restarted afterward.
The screen’s appearance and messaging can vary between Windows 11 releases. Microsoft says an unexpected restart may be caused by a hardware device, its driver, or software; the code is a starting clue, not a diagnosis. Microsoft’s guidance on unexpected restarts and stop code errors explains what information may appear.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Check Event Viewer around the crash time
Look for critical events in the Windows System log that occurred at or near the time of the crash. The timestamps, event names, and any device or driver mentioned may provide a lead. A nearby event is not proof that it caused the crash, so compare it with the stop code and any recent changes.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
- Search Windows for Event Viewer and open it.
- In the navigation pane, expand Windows Logs, then select System.
- Review events around the time you recorded. Note their exact timestamps and descriptions, especially references to a device or driver.
Microsoft recommends checking the System log for messages that might help pinpoint a device or driver. Resolving blue-screen errors in Windows describes this check.
3. Check memory if the symptoms point that way
If memory is a plausible cause, run the built-in Windows Memory Diagnostic. After it completes, look in Event Viewer for a MemoryDiagnostics-Results entry to review the result. Treat this as one troubleshooting check, not a complete certification of the computer’s hardware.
- Search Windows for Windows Memory Diagnostic and open the tool.
- Follow its prompts to run the diagnostic. The computer may need to restart.
- After Windows starts again, open Event Viewer and inspect the System log for
MemoryDiagnostics-Results.
4. If the crashes keep happening
Undo a recent hardware change
If the problem began after you added hardware, shut down the PC and remove that new hardware before testing again. If the crashes stop, the change is a useful lead; it does not, by itself, identify whether the device, its driver, or another factor was responsible.
Use Safe Mode when normal startup is difficult
If Windows repeatedly restarts or is difficult to use, Safe Mode provides a troubleshooting environment. Microsoft includes it among the steps for dealing with recurring restart and stop-code problems. See Microsoft’s troubleshooting guidance for the applicable steps.
Consider dump analysis only if you have the necessary experience
A memory dump can be analyzed for more detailed clues, but Microsoft frames this path for IT professionals and developers. If you are not comfortable interpreting diagnostic data, use the stop code, Event Viewer details, and recent-change history when seeking technical help rather than treating a dump as a simple end-user diagnosis.
Rank #2
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
5. Choose recovery options based on whether Windows starts
If Windows still starts, begin with less disruptive troubleshooting where possible. Depending on what changed before the crashes, options may include uninstalling a recent update or using a restore option. Back up important files before recovery when you can: some actions can cause data loss, and available features vary by Windows version. Microsoft’s Windows recovery options guide explains the choices.
If Windows will not start normally, Windows Recovery Environment (WinRE) offers tools including Startup Repair, uninstalling updates, restore options, and Command Prompt. Which option is appropriate depends on the failure; not every tool fits every situation. On an encrypted device, Windows may ask for a BitLocker recovery key to access many recovery options. See Microsoft’s Windows Recovery Environment guide.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
One version-specific option is Point-in-time restore: Microsoft says it is available for Windows 11 version 24H2 or later and rolls the computer back, including personal files, apps, and settings. Check the feature’s availability and effects for your Windows version before using it. Microsoft’s recovery-options guide covers current recovery choices.
Local crash records and diagnostic-data privacy
Reviewing Event Viewer is a local troubleshooting step. Separately, Microsoft says optional diagnostic data may include the device’s memory state when a system or app crashes; that memory could unintentionally contain parts of a file that was open or in use. Consider this distinction when deciding whether to send optional diagnostic data. Microsoft’s diagnostics, feedback, and privacy information explains what Windows diagnostic data may include.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
