Observation
A photo or note of the exact stop code or reboot behavior.
Blue Screens and Random Reboots
Use this flow when the system blue screens, freezes, or randomly reboots and you need to separate memory tuning, thermals, drivers, storage, and power issues in a safe order. Start with evidence before rollback or swap testing.
Safety first: capture the stop code before repeated restarts erase it, and stop heavy load testing if temperatures are already unsafe.
What this flow is for
This flow is for unstable systems that crash or reboot unpredictably, so you can narrow the fault domain before you start rolling back drivers, pulling hardware, or replacing parts.
First safe checks
- Capture the exact stop code or reboot pattern first.
- List recent hardware, BIOS, driver, or Windows changes.
- Disable memory tuning and other overclocks temporarily.
- Check temperatures at idle and under load.
- Separate idle, gaming, and boot-time crashes before deeper fixes.
Evidence requests
Ask for the smallest missing proof
Photo or screen
Idle and load temperatures if the system stays up long enough to measure them.
Change log
A short list of recent hardware, BIOS, driver, or Windows changes.
Likely causes
Most likely problem buckets
Memory instability
Memory tuning and other overclocks are one of the fastest ways to create random crashes.
Driver or update issue
Recent BIOS, chipset, GPU, or Windows changes can turn a stable system unstable.
Thermal issue
High idle or load temperatures can cause freezing, throttling, or abrupt shutdowns.
Power, GPU, or storage problem
Load-specific reboots often point toward a particular component path instead of Windows alone.
Next safe steps
Take one step at a time
ACT-PC-015
Capture the exact stop code or reboot pattern before changing more variables.
ACT-PC-011
Disable memory tuning and other overclocks while you test for a clean baseline.
ACT-PC-013
Record idle and load temperatures to separate thermal issues from other fault domains.
ACT-PC-018
Review recent BIOS, driver, storage, and power-path changes against the failure pattern.
Best follow-up ask
What exact stop code or reboot pattern are you seeing, and does it happen at idle or under load?
When to stop and hand off
You still cannot find a clear pattern after stop-code capture, baseline settings, and basic thermal review.
Support links
Keep the instability pattern readable
If the problem looks more like boot failure, clear thermal trouble, or no-display behavior, move into the closest symptom page instead of forcing every crash into one category.
Open PC problems Open troubleshooting library