Basic Troubleshooting Steps When Something Stops Working

When something stops working, start with power, cables, connections, and any error message. Those simple checks fix a lot of problems and are the safest place to begin. If that doesn’t help, restart once, then work out whether the problem follows the device, the app, the network, or the power source.

What to check first when it stops working

Start with the parts that fail most often and are easiest to verify: power, cables, switches, battery level, signal, and any message on the screen or indicator light.

Device will not turn on
App opens but freezes or crashes
No sound, no picture, no response, or a flashing warning light

Check whether the device is actually getting power. If it has a plug, make sure it is fully seated at both ends. If it uses a battery, confirm it is charged or try the charger. If it depends on a signal, look for weak Wi‑Fi, no cellular bars, or a disconnected network icon.

If there is an error message, read it exactly as written before you do anything else. That message often points to the failed part, and changing settings blindly can make the problem harder to trace.

Is this problem actually something you can fix yourself?

Before you spend time on fixes, decide whether the symptom looks temporary, user-caused, or likely hardware-related.

Use this simple test:

• If the problem started right after a setting change, update, move, or power outage, it may be temporary or caused by a simple setting.
• If only one app, one input, one cable, or one account is failing, the issue is probably narrow and testable.
• If the device is dead, smells hot, has visible damage, or fails in the same way no matter what you change, it may be hardware-related.

For most readers, the first round of troubleshooting is safe if you stick to reversible checks. You are trying to find the bad link in the chain, not repair internal parts or change hardware yet.

Applies to most phones, computers, apps, routers, TVs, printers, small appliances, and similar devices. Version details vary by device and app.
Privileges needed: none for the first checks; Administrator or sudo only if you later change system settings.
Backup involved: only if a later step might affect data or reset settings.
Safe first checks: power, cable fit, battery level, and the exact error message.

If the item is still under warranty or you suspect a physical fault, keep going only with the safest checks. Don’t open the case, pry anything apart, or force connectors that already feel stuck.

Try the simplest reset and retry steps

The next move is a clean restart or power cycle. This clears a lot of temporary glitches without changing your data or settings.

1. Turn the device or app off if you can.
2. Wait a few seconds.
3. Turn it back on or reopen the app.
4. If it’s a device with a power cord, unplug it briefly, then plug it back in.

For a computer, phone, tablet, router, or streaming device, a normal restart is usually the first safe reset. For an app, close it completely and open it again. If the app is stuck, sign out and sign back in only if that’s low risk and you know your account details.

Phone or tablet: Power off / Restart from the power menu
Computer: Restart from the operating system menu
App: Close the app completely, then reopen it
Router or modem: Unplug power, wait briefly, plug it back in

If the restart fixes it, the problem was probably temporary. If it comes back immediately, that usually means there is a deeper issue, a bad setting, a bad connection, or failing hardware.

Check the obvious settings and connections

A lot of “broken” devices are really in the wrong mode, on the wrong input, or connected the wrong way. Check the obvious things before you assume anything is damaged.

Look for these common misses:

• Mute or volume turned down
• Airplane mode on
• Wi‑Fi disconnected or joined to the wrong network
• Wrong input source on a TV, monitor, or sound system
• Loose USB, HDMI, charging, Ethernet, or power cable
• Printer set offline, paused, or on the wrong tray
• Brightness, sleep timer, or power-saving mode hiding the screen or slowing the device

Wi‑Fi or network settings: Settings > Network / Internet / Connections
Sound: Settings > Sound or Audio
Display or input source: TV/monitor input menu
App permissions or account: App settings > Permissions / Account

If adjusting one setting fixes the issue, stop there and test it again. If nothing changes, don’t keep toggling random options. That makes it harder to tell what was actually wrong.

See whether the problem is with one thing or everything

Now isolate the fault by changing one variable at a time. The goal is to learn whether the failure follows the device, the app, the cable, the outlet, the account, or the network.

Try one test at a time:

1. Swap the cable with another one you know works.
2. Try a different power outlet or charger.
3. Connect to a different Wi‑Fi network or use mobile data, if that applies.
4. Open the same app or service on another device.
5. Sign in with a different account, if the problem is account-based.
6. Try another device in the same spot to see if the location or power source is the real issue.

Network test: Settings > Wi‑Fi / Network and connect to another available network
Account test: Sign out, then sign in again on the same app or service
Input test: Select a different input source on the device

If one cable, one outlet, or one network makes the problem disappear, you’ve narrowed the cause. If every test fails the same way, the problem is probably inside the device or app itself, not the outside connection.

How to tell if the fix worked

A fix worked only if the device or app returns to normal behavior and keeps working after you repeat the action that failed before.

Look for these signs:

• The device powers on normally.
• The app opens and stays open.
• The error message is gone.
• Sound, display, network, or input works again.
• The failure does not come back when you restart or retry the same task.

If the symptom disappears for a minute and then returns right away, treat that as a partial failure, not a real fix. That usually means the underlying problem is still there, even if the device seemed better for a moment.

Device responds normally
No error message appears
The same task completes more than once

If the problem only happens under a specific condition, like when the device warms up, when a certain app opens, or when a particular cable is attached, that clue matters. Keep that note for support or repair.

When to stop basic troubleshooting

Stop at basic troubleshooting when the problem starts to look unsafe, physical, or clearly beyond simple settings.

Get support, repair, or replacement if you notice:

• Burning smell, smoke, heat that seems unusual, or a swollen battery
• Cracked housing, bent connectors, liquid damage, or missing parts
• Repeated error messages after a restart and cable or power check
• Data loss, files disappearing, or an account locked out in a way you can’t clear safely
• A device that fails with every cable, outlet, network, or app you try
• A power adapter, charger, or cord that is damaged or getting unusually hot

Don’t keep powering on a device that smells burnt, overheats, or shows signs of battery swelling. Unplug it if that can be done safely and move to support.

If the device is under warranty, has a required calibration, or stores important data, stop before any reset that might erase or change things you need. At that point, the safer next step is manufacturer support, service, or replacement.

Common mistakes that make troubleshooting harder

The biggest troubleshooting mistakes are usually small ones that waste time and hide the real cause.

Avoid these:

• Changing several settings at once, then not knowing which one mattered
• Skipping the power check and assuming the device itself is broken
• Ignoring the exact error message or warning light
• Testing with the same bad cable, charger, outlet, or network over and over
• Jumping straight to a reset, reinstall, or factory restore before trying simpler checks
• Forgetting to put the device back in its normal mode after a test

A slower, cleaner sequence usually works better: power, connection, simple restart, settings, isolation, then support if needed. That order keeps you from making the problem worse and makes your next step easier to explain if you do need help.

A quick checklist you can save for next time

Use this same order the next time something stops working:

1. Check power, battery, cables, and any visible error message.
2. Restart the device or close and reopen the app.
3. Confirm obvious settings like mute, airplane mode, Wi‑Fi, input source, or offline mode.
4. Swap one thing at a time: cable, outlet, network, account, or device.
5. Test whether the fix holds after you repeat the failed action.
6. Stop if there is physical damage, burning smell, repeated errors, or data loss.
7. Escalate to support, repair, or replacement if the same failure keeps coming back.

If you keep that sequence in mind, you’ll spend less time guessing and more time finding the real fault.

Conclusion

If the simple checks fixed it, keep using the device normally and watch for the same symptom coming back. If they didn’t, gather the exact error, what you already tested, and which part of the setup failed, then contact support or a repair service with that information.

Frequently Asked Questions

Should I restart first or check cables first?

Check power and cables first, then restart. A restart won’t help if the device isn’t actually getting power or signal.

How many things should I change at once?

Only one variable at a time. If you change several things together, you won’t know which one solved the problem.

What if the problem only happens sometimes?

That often points to a loose connection, weak signal, overheating, or a failing part. Try to reproduce it with the same action and note exactly when it happens.

When is a reset too much?

Skip any reset that might erase data, remove settings, or make recovery harder unless you’ve already ruled out the simpler checks and you understand the impact.