Crash timing matters
A failure during gaming, idle, updates, or first boot points the next check in different directions.
Blue screens and random reboots
This page is for the system that seems mostly alive but fails unpredictably under load, at idle, or during startup. The goal is to keep the diagnosis grounded in stop codes, repeat conditions, and baseline stability checks instead of swapping parts in panic.
Stop codes are worth keeping
A photographed or noted stop code is often more useful than three rounds of random changes.
Baseline before tuning
Returning to a simpler, stock-like state often reveals whether the issue is configuration or deeper instability.
Keep the diagnosis small
These checks help you separate heat, tuning, boot-path, and random stability trouble before the pattern disappears.
- Capture the stop code or the exact restart pattern if you can.
- Notice whether the issue appears during load, heat, idle, or after a recent change.
- Return aggressive tuning or experimental settings to a calmer baseline first.
- Separate true shutdowns, instant restarts, and blue screens because they are not the same symptom.
Open the next page that matches the crash pattern
Start with thermals if heat or load triggers the failure. Start with boot recovery if the machine no longer reaches a usable desktop reliably.
If the symptom stays active