Hardware and Network Troubleshooting Flashcards
What are the steps to the troubleshooting method?
- Identify the problem.
- Establish a theory of probable cause (question the obvious).
- Test the theory to determine the cause. If not fixed, establish a new theory.
- Establish a plan of action to resolve the problem and implement the solution.
- Verify full system functionality and, if applicable, implement preventative measures.
- Document the finds, actions, and outcomes.
What should you always do before implementing changes?
- Plan for the change.
- Estimate the risk associated with the change.
- Have a recovery plan if the change doesn’t work.
- Test before making the change.
- Document all of this and get approval.
- Make the change.
What should you do when identifying the problem?
- Gather information, getting as many details as possible, and observe or duplicate the issue if possible.
- Identify all symptoms.
- Question the user about any recent changes to the software or hardware.
- Determine if any higher-level changes have been made.
- Approach each problem on its own.
- Make backups.
What should you do when establishing a theory of probable cause?
- Make a list of all possible causes, prioritizing the obvious causes before the less obvious.
- Utilize internal knowledgebase and the internet to research issues.
What should you do when testing the theory to determine the cause?
- If it works, then establish a plan.
- If it doesn’t, establish a new theory.
- If none of your theories are working, escalate.
What should you do when establishing a plan of action to resolve the problem and implement the solution?
- Build a plan with minimal impact to operations.
- Refer to any vendor documentation or support for the issue.
- Identify potential effects and make a plan B and C.
- Implement the fix during the change control window.
- Escalate to a 3rd party as necessary.
What should you do when verifying full system functionality and, if applicable, implementing protective measures?
- Have the user confirm the fix.
- Implement preventative measures through user education.
What should you do when documenting the findings, actions, and outcomes?
- Document actions and outcomes.
- Add to the formal knowledge base.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot POST beeps?
- Check the documentation for the meaning of the beeps.
- If there is a blank screen on boot, you have bad video, RAM, or CPU, or a BIOS config issue.
- If the time is incorrect or has been reset, you need to replace the CMOS battery.
- Might try to boot to an unintended drive, in which case change the boot order.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot proprietary crash screens?
Windows:
1. Check Event Viewer.
2. May be able to have manufacturer check error logs, or can research Windows stop code yourself.
3. Could be bad drivers, so try a system restore or driver rollback.
4. If it boots into Safe Mode, try and reseat any new hardware.
5. If still occuring, do a full hardware diagnostic using manufacturer utilities or using the BIOS to run the scan, if availble.
Mac:
1. Restart the computer and check the console logs, as it could be a bad app, or a memory or storage issue.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot black screen?
- Check the power and signal cables to the monitor.
- Change the input selection on the monitor.
- If the image is dim, check brightness controls.
- Try the monitor on a different computer.
- Try VGA mode from BIOS.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot no power?
If nothing happens at all:
1. Check outlet for power.
2. Check PSU for power.
3. Check PSU switch and cabling.
If fans spin:
1. Check if fans are connected to motherboard or PSU to check which is functioning.
2. Check if it POSTs, then troubleshoot POST issues.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot sluggish performance?
- Check task manager for processes with high CPU utilization.
- Windows may be updating.
- Check amount of disk space and defrag.
- If it’s a laptop, check for power-saving mode.
- Check for overheating.
- Antivirus/malware may be running.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot overheating?
- Check temps using BIOS or program like HW monitor.
- Clean and clear the path of airflow.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot a burning smell?
- Disconnect from power immediately.
- Open the case and see if a particular component failed or if you need a new motherboard.
- Replace components or motherboard.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot intermittant shutdown?
- Check Event Viewer to see if it recorded the shutdown.
- Check fans, heat sinks, and airflow, and monitor the temp.
- Check Device Manager or run a diagnostic to see if a particular component is failing.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot app crashes?
- Check the Event Log.
- Check Reliability Monitor.
- Reinstall app.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot a grinding noise?
- Rattling means loose components. Reinstall or replace.
- Scraping is a hard drive issue. Replace.
- Clicking or oscillating sound is a fan problem. Clear its path.
- Pops are blown capacitors. Replace.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot capacitor swelling?
- Locate the capacitor as the swelling may be subtle.
- Replace.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot lockups?
- Check for any activity such as hard drives spinning, status lights, toggling key locks, or Ctrl-Alt-Delete.
- Update drivers and software, or uninstall new software.
- Check for low resources
- Run hardware diagnostic.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot continuous reboots.
- Determine how far in the boot process it goes to determine if a BIOS or an OS issue.
- Use Safe Mode to disable the automatic restart setting to see error code.
- Replace bad hardware if indicated.
- Rollback drivers.
- If still not working, use F8 during boot to go to last known good configuration.
When it comes to the motherboard, RAM, CPU, and PSU, how do you troubleshoot inaccurate system date/time?
Replace CMOS battery.
What are signs storage has failed?
- Read/write failures, the inability to use the disc.
- Slow performance, constant LED activity, or constant reattempts to access.
- A loud clicking or grinding noise.
How do you trouble shoot disk failure?
- Get a backup.
- Check for any loose cabling.
- If the device runs for a while before symptoms occure, check for overheating.
- Check the PSU, especially if new devices were added.
- Run hard drive diagnostics.
What are the symptoms of boot failure?
- Drive not recognized, Boot Device not Found. Accompanied with beeps, or lights, or error message.
- OS not found. The drive is there, the OS isn’t.
When it comes to storage, how do you troubleshoot “bootable device not found?”
- Check the cables.
- Remove any removable boot devices, check the boot sequence in the BIOS, and ensure drive is enabled.
- If it’s new hardware, check to make sure the power and data cables are installed correctly. Try multiple SATA slots. Try the device in another computer.
When it comes to storage, how do you troubleshoot data loss/corruption?
- Always have a backup. Discs stop spinning, and SSDs may decide to read but not write.
- Third parties might be able to recover data from the disk.
When it comes to storage, how do you troubleshoot RAID failure?
- Check the controller utility during startup for RAID issues. Replace bad drives if you can.
- The RAID controller is missing or bad.
When it comes to storage, how do you troubleshoot SMART failure?
- Use SMART utilities to access data about the drive, including errors.
- RAID arrays will update you on performance.
- Replace when the errors start ticking up.
When it comes to storage, how do you troubleshoot extended read/write times?
- Know that 200 IOPS is the norm for HDDs, 1,000,000 IOPS for SSDs.
When it comes to storage, how do you troubleshoot with IOPS?
- Use it as a standard to compare.
When it comes to storage, how do you troubleshoot missing drives in OS?
- Check the BIOS for the drive.
- Check the cables/connections.
- If it’s a network share, rerun the log-in script.