From d24cf54e3f14938f145d641e7cfbee1665deec4d Mon Sep 17 00:00:00 2001
From: Shihaam Abdul Rahman <shihaam@shihaam.me>
Date: Mon, 11 Sep 2023 17:17:41 +0500
Subject: [PATCH] troubleshooting

---
 syllabus/1.md            | 10 ++-------
 syllabus/troubleshoot.md | 44 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 46 insertions(+), 8 deletions(-)
 create mode 100644 syllabus/troubleshoot.md

diff --git a/syllabus/1.md b/syllabus/1.md
index 8f54fa5..4856686 100644
--- a/syllabus/1.md
+++ b/syllabus/1.md
@@ -72,11 +72,5 @@ Output devices display or output data from a computer. Examples include monitors
 - **Drivers**: Software to interface with hardware.
 - **Examples of Operating Systems**: Windows, macOS, Linux
 
-## Troubleshooting Hardware
-- **RAM**: Check for faulty memory modules.
-- **CPU**: Overheating or malfunction.
-- **MB**: Motherboard issues.
-- **PSU**: Power supply unit failures.
-
-## Troubleshooting Network
-- **OSI Model**: Use it as a framework for troubleshooting.
+## Troubleshooting 
+ Read more on (troubleshoot.md)[troubleshoot.md]
diff --git a/syllabus/troubleshoot.md b/syllabus/troubleshoot.md
new file mode 100644
index 0000000..5056259
--- /dev/null
+++ b/syllabus/troubleshoot.md
@@ -0,0 +1,44 @@
+## Troubleshooting Hardware
+
+### RAM
+1. **Symptoms**: Frequent crashes, Blue Screen of Death (Windows), or kernel panics (macOS/Linux).
+2. **Steps**:
+    - Turn off the computer and unplug it.
+    - Open the case and reseat the RAM modules.
+    - Try booting with one RAM stick at a time to isolate faulty modules.
+    - Use software like MemTest86 to test RAM.
+
+### CPU
+1. **Symptoms**: Overheating, system instability, or failure to boot.
+2. **Steps**:
+    - Check the CPU temperature using BIOS or software like HWMonitor.
+    - Ensure the CPU fan is working and reapply thermal paste if needed.
+    - Check for bent pins or damaged components.
+
+### Motherboard (MB)
+1. **Symptoms**: Failure to boot, no power, or irregular behavior.
+2. **Steps**:
+    - Inspect for physical damage like burnt areas or bent pins.
+    - Check all connections and reseat components.
+    - Test with minimal hardware to isolate issues.
+
+### Power Supply Unit (PSU)
+1. **Symptoms**: No power, random shutdowns, or system instability.
+2. **Steps**:
+    - Use a PSU tester or multimeter to check voltage levels.
+    - Inspect for physical damage or burnt smell.
+    - Replace if faulty.
+
+## Troubleshooting Network
+
+### OSI Model
+Use the OSI model as a framework for troubleshooting network issues. Start from the bottom layer and work your way up.
+
+1. **Physical Layer**: Check cables, switches, and other hardware.
+2. **Data Link Layer**: Verify MAC addresses and ensure devices can communicate within the same local network.
+3. **Network Layer**: Check IP addresses, subnet masks, and routers.
+4. **Transport Layer**: Verify that TCP or UDP ports are open and listening.
+5. **Session Layer**: Ensure that sessions can be established and maintained.
+6. **Presentation Layer**: Check for data format or encryption issues.
+7. **Application Layer**: Verify that the application is functioning as expected, check for updates or patches.
+