Advanced Computer Maintenance Guide
Advanced Computer Maintenance Guide
Minimize downtime
Increase Mean Time Between Failures (MTBF)
Reduce operational costs
Ensure system security
Maintain data integrity
Extend equipment lifespan
No POST
Continuous beep codes
No display
Random freezes
Maintenance Steps:
Overheating Symptoms:
Sudden shutdowns
Thermal throttling
Loud fan noise
System lag under heavy tasks
Procedure:
Remove RAM
Clean contacts with eraser
Clean slot with compressed air
Reseat firmly
Test with Memory Diagnostic Tool
Fault Symptoms:
BSOD
Random restart
Memory errors
System freeze
Inspect fan
Check for burnt smell
Test output with multimeter
Replace if unstable
No power
Random restart
Burning smell
Shutdown under load
HDD Maintenance:
Run CHKDSK
Defragment (HDD only)
Monitor SMART status
Backup data regularly
SSD Maintenance:
Update firmware
Avoid defragmentation
Monitor health status
Symptoms of Failure:
Disk Cleanup
Disk Management
CHKDSK
Defragmentation (HDD only)
Installation Order:
1. Chipset
2. VGA
3. LAN
4. Audio
5. Other peripherals
Check:
Device Manager → No yellow warning signs
5️ Security Maintenance
5.1 Antivirus Protection
5.2 Firewall
Types:
Full backup
Incremental backup
Differential backup
Use:
External drives
Cloud storage
System image backup
6️ Troubleshooting Framework
Professional Method:
1. Identify problem
2. Gather information
3. Isolate cause
4. Repair or replace
5. Test system
6. Document solution
2️ Diagnostic Steps
3️ Solutions
1. Replace PSU
o If PSU fails voltage tests or does not spin, replace with a known good unit.
2. Reconnect or replace cables
o Ensure AC power cable is working.
o Replace if damaged.
3. Reseat front panel connectors
o Correctly attach power switch, reset switch, and LEDs according to motherboard
manual.
4. Reset CMOS / BIOS
o Replace CMOS battery if dead.
o Reset settings to defaults to eliminate misconfiguration.
5. Remove faulty peripherals
o Disconnect USB drives, printers, external hard drives, and test boot again.
6. Check motherboard
o Inspect for damage or short circuits.
o Replace motherboard if faulty.
7. Professional repair
o If all else fails, consult manufacturer or technician for PSU/motherboard repair.
Step Action
Check Power Source Confirm outlet & PSU cable
Inspect Hardware Look for damage, burnt smells, bulging capacitors
Minimal Boot Disconnect peripherals, keep essential components
Check Front Panel Reseat power/reset switch connectors
Test PSU Paperclip test, multimeter voltage check
Reset CMOS Remove battery 5–10 min, reinsert
Remove Faulty Devices Disconnect USB, external drives
Replace Components PSU/motherboard if defective
1. RAM not properly seated or faulty – prevents POST and display output.
2. GPU (Graphics Card) failure or not seated properly – video signal not sent to
monitor.
3. Monitor cable loose, damaged, or wrong input source – no signal reaches display.
4. Incorrect BIOS/UEFI settings – integrated vs discrete GPU selection, or disabled video
ports.
5. PSU unable to supply sufficient power to GPU – especially for high-end graphics
cards.
6. Faulty monitor – hardware failure in the display.
7. Motherboard failure – damaged video output circuitry.
2️ Diagnostic Steps
3️ Solutions
Step Action
Check Monitor & Cable Ensure power, reconnect cables, test another system
Input Source Correct HDMI/DP/VGA selection
Reseat/Test RAM Remove & reinstall, test individually
Reseat/Test GPU Ensure PCIe connection, test integrated graphics
Minimal Boot Disconnect peripherals, boot essentials only
Check PSU Ensure GPU powered, measure voltages
Reset CMOS Remove battery 5–10 min, reinsert
Observe POST Codes Listen to beeps, check motherboard LEDs
Replace Components GPU, RAM, monitor, PSU, or motherboard as needed
2️ Diagnostic Steps
3️ Solutions
1. Fix Overheating
o Clean CPU/GPU heatsinks and fans.
o Reapply thermal paste.
o Improve airflow in case/chassis.
o Consider upgrading cooling system for high-performance components.
2. Replace or Test PSU
o Replace faulty PSU.
o Ensure PSU can handle peak load of CPU + GPU.
3. Reseat or Replace RAM
o Reinstall RAM firmly in correct slots.
o Replace faulty RAM sticks.
4. Update / Rollback Drivers
o Install latest stable drivers from official manufacturer sites.
o Rollback any drivers causing instability.
5. Remove Malware
o Run antivirus scans, remove threats, and clean temporary files.
6. Reset Overclocking
o Set CPU, GPU, and RAM to default frequencies.
o Test system stability under default settings.
7. Repair OS / System Files
o Run SFC /scannow and DISM to repair corrupted Windows files.
o Reinstall OS if corruption persists.
8. Replace Faulty Components
o Motherboard, GPU, or PSU replacement if hardware is failing.
2️ Diagnostic Steps
3 Solutions
1. Remove Malware
o Quarantine or delete infected files.
o Clean temporary files using Disk Cleanup or third-party tools.
2. Optimize Startup Programs
o Disable unnecessary applications from launching at boot.
3. Upgrade or Replace Hardware
o Increase RAM if insufficient.
o Upgrade HDD to SSD for faster storage access.
4. Clean Cooling System
o Remove dust from CPU/GPU fans.
o Reapply thermal paste if overheating.
5. Repair OS & Drivers
o Run SFC /scannow and DISM to fix corrupted system files.
o Update or reinstall drivers.
6. Disk Maintenance
o Defragment HDD.
o Free up space on full drives.
7. Software Management
o Uninstall unused applications.
o Keep system lean for better performance.
8. Perform System Restore or Reinstall OS (if needed)
o For persistent slowdowns caused by corrupted OS files or malware.
Step Action
Task Manager / Resource Identify CPU, RAM, disk hogs
Monitor
Malware Scan Remove viruses/malware
Check Disk Health & Space CHKDSK, SMART status, free space
RAM Usage Monitor virtual memory, test RAM if needed
Check System Temperature HWMonitor/CoreTemp
Startup Programs Disable unnecessary startup apps
Drivers & Windows Update Update drivers and OS
Disk Fragmentation Defrag HDD only
Clean Boot Isolate software conflicts
Solutions Malware removal, hardware upgrade, cooling, disk cleanup,
OS repair
2 Diagnostic Steps
Step Action
Note BSOD Code Identify component/driver issue
Event Viewer Check Critical/Error logs
Memory Test Windows Memory Diagnostic / MemTest86
Storage Health CHKDSK, SMART tools
Update/Rollback Drivers GPU, chipset, network, storage
Scan for Malware Full antivirus/malware scan
Check Temperatures HWMonitor/CoreTemp
Test Recent Hardware Disconnect new components
Reset Overclocking BIOS default clock speeds
Repair OS SFC / DISM / System Restore / Reinstall
Pro Tip:
1. Hard Drive Clicking / Grinding – failing HDD with damaged read/write heads or bad
sectors.
2. POST Beep Codes – motherboard signals hardware faults via beeps (RAM, GPU, CPU,
motherboard).
3. Fan Whining or Rattling – CPU, GPU, PSU, or case fan bearings worn or obstructed.
4. Loose or Misaligned Components – screws, expansion cards, or cables vibrating.
5. Electrical Noise (Coil Whine) – GPU, PSU, or motherboard coils vibrating under load.
6. Optical Drive Spinning Noise – CD/DVD drive spinning or reading disc.
2️ Diagnostic Steps
3️ Solutions
Step Action
Identify Noise Clicking, Beeping, Whining, Rattling
Check POST Beeps Consult motherboard manual
Inspect HDD Backup, CHKDSK, SMART diagnostics
Inspect Fans Clean dust, spin test, replace if faulty
Check Coil Whine Monitor GPU/CPU load, V-Sync/frame limit
Inspect Loose Components Tighten screws, reseat cards/cables
Minimal Setup Test Disconnect peripherals to isolate noise
Implement Solutions Replace HDD, fans, reseat hardware, adjust GPU/PSU
Pro Tips:
2️ Diagnostic Steps
3️ Solutions
Step Action
Physical Connections Check Ethernet/Wi-Fi cables
Router / Modem Restart, check LEDs, update firmware
IP Configuration Verify IP, subnet, gateway; renew if needed
Ping Test Test local gateway & external site connectivity
Network Adapter Enable, update, or reinstall driver
Firewall / Antivirus Temporarily disable to test
Wi-Fi Signal Check interference, reposition, change channel
Test Other Devices Identify device-specific vs network-wide issues
Implement Solutions Replace cables, reset router, update drivers, malware scan, contact ISP
Pro Tips:
Always check both hardware and software layers – many connectivity issues are
caused by simple cable or adapter problems.
Use ping and traceroute to pinpoint where connectivity fails (local network vs ISP).
Keep router firmware updated to prevent security and performance issues.
Document recurring network issues to identify patterns for troubleshooting.
2️ Diagnostic Steps
1. Monitor Temperatures
o Use HWMonitor, CoreTemp, GPU-Z, or MSI Afterburner.
o Compare readings with manufacturer’s safe operating range (CPU: 30–85°C,
GPU: 30–90°C typically).
2. Inspect Cooling System
o Check CPU/GPU fans spinning properly.
o Verify heat sinks are securely attached.
o Ensure no cables blocking airflow.
3. Clean Dust & Debris
o Use compressed air to clean heatsinks, fans, and case vents.
4. Check Thermal Paste
o Remove old paste with isopropyl alcohol.
o Apply a fresh, appropriate amount (pea-size).
5. Verify Case Airflow
o Ensure proper intake and exhaust fan setup.
o Check airflow direction, avoid obstructing fans.
6. Check for Overclocking
o Reset BIOS/UEFI to default clock speeds if CPU/GPU is overclocked.
7. Stress Test
o Use Prime95 (CPU) or FurMark (GPU) to test thermal performance under load.
8. Check Ambient Temperature
o Ensure room is cool enough for proper cooling (20–25°C recommended).
3️ Solutions
Step Action
Monitor Temps HWMonitor, CoreTemp, GPU-Z
Inspect Cooling Fans spinning, heatsink properly seated
Clean Dust Compressed air for fans, heatsinks, vents
Check Thermal Paste Remove old paste, reapply new layer
Case Airflow Ensure intake/exhaust balance, tidy cables
Check Overclocking Reset BIOS to default if overclocked
Stress Test Prime95 for CPU, FurMark for GPU
Environmental Control Keep room temperature low
Solutions Clean, replace fans, reapply thermal paste, improve airflow, upgrade cooler
Pro Tips:
2️ Diagnostic Steps
1. Backup Important Data Immediately
o First priority is to secure data from failing storage.
2. Check Disk Health
o HDD: Use CHKDSK (chkdsk /f /r) to check and repair errors.
o SSD: Use manufacturer tools (Samsung Magician, Crucial Storage Executive) to
check SMART status.
3. Listen for HDD Sounds
o Clicking or grinding noises indicate imminent failure.
4. Check Connections
o Verify SATA/PCIe cables are firmly connected.
o Try different ports or cables to rule out faulty connections.
5. Check Power Supply
o Ensure stable voltage delivery; unstable PSU can damage storage.
6. Test with Another System
o Connect the drive to another PC to isolate whether the problem is drive-specific
or system-related.
7. Check for Driver / Firmware Updates
o Update storage controller drivers and SSD/HDD firmware.
8. Scan for Malware
o Run a full antivirus scan to eliminate malware-related corruption.
3️ Solutions
1. Backup Data
o Prioritize copying important files to external drives or cloud storage immediately.
2. Repair File System Errors
o Run CHKDSK or equivalent repair tools.
3. Replace Damaged Storage Device
o Replace HDD or SSD if mechanical failure or excessive wear is detected.
4. Update Firmware & Drivers
o SSD firmware updates often resolve performance or recognition issues.
o Update storage controller drivers to ensure proper OS communication.
5. Check Power & Connections
o Replace faulty SATA/PCIe cables.
o Ensure PSU provides stable power.
6. Preventive Measures
o Avoid physical shocks or drops.
o Use surge protectors or UPS to protect against power fluctuations.
o Enable TRIM for SSDs to maintain performance.
7. Use Disk Imaging / Recovery Tools
o If drive is partially failing, create a disk image before complete failure.
o Use recovery software to retrieve lost data.
Step Action
Backup Data Secure important files immediately
Disk Health Check CHKDSK for HDD, SMART/firmware tools for SSD
Listen for Sounds Clicking/grinding indicates HDD failure
Check Connections SATA/PCIe cables, different ports
Check PSU Ensure stable voltage delivery
Test in Another System Isolate drive vs system issue
Update SSD firmware, storage controller drivers
Firmware/Drivers
Scan for Malware Remove virus/malware affecting storage
Solutions Repair file system, replace drive, update firmware, use recovery tools,
preventive measures
Pro Tips:
HDD clicking or grinding is a red alert – do not continue using the drive; backup
immediately.
SSD failures are often sudden – monitor SMART attributes like wear leveling, bad
blocks, and total writes.
Regular backups are critical – storage failure is unpredictable and data loss can be
catastrophic.
Use high-quality cables and surge protection to prolong lifespan.
1. Faulty USB cable or port – damaged cables, bent pins, or malfunctioning USB port.
2. Driver issues – missing, outdated, or corrupted USB or peripheral drivers.
3. Power supply limitations – USB device not receiving enough power.
4. Operating system errors – OS failing to detect or mount the device.
5. Device malfunction – the peripheral itself is defective.
6. Conflicts with other USB devices – multiple devices causing resource conflicts.
7. USB controller issues – motherboard’s USB controller may be faulty.
8. Security / Antivirus restrictions – software blocking device access.
9. Incompatible USB version – e.g., USB 3.0 device on a malfunctioning USB 2.0 port.
2️ Diagnostic Steps
3️ Solutions
Step Action
Physical Connections Check cable, port, try another USB port
Test on Another System Isolate device vs PC issue
Device Manager Look for errors, unknown devices
Update / Reinstall Drivers Automatic or manual driver install
Check Power Use powered hub or AC connection
Disable USB Selective Prevent OS from suspending ports
Suspend
Remove Conflicting Devices Test one USB device at a time
OS Updates Install latest patches
BIOS / UEFI Ensure USB ports enabled, legacy support on
Solutions Replace cable, use powered hub, reinstall drivers, replace device or
controller
Pro Tips:
High-power devices often fail on unpowered USB ports; always use a powered hub if
needed.
Rear motherboard USB ports usually deliver more stable power than front panel ports.
Backup drivers before major OS updates to prevent peripheral failures.
Regular preventive maintenance like dust cleaning can prevent port damage.
2️ Diagnostic Steps
3️ Solutions
Step Action
Check Physical Connections USB/PS2 cable, wireless receiver, battery level
Test on Another System Isolate device vs PC issue
Device Manager Check for errors or disabled devices
Update / Reinstall Drivers Latest manufacturer drivers
Try Different Ports Switch USB/PS2 ports
BIOS / UEFI Enable legacy USB / PS2 support
Remove Conflicts Disconnect other peripherals temporarily
Wireless Check Replace batteries, pair receiver, reduce interference
Scan for Malware Full antivirus/anti-malware scan
Solutions Replace cable/device, update drivers, check BIOS, scan malware
Pro Tips:
Rear motherboard USB ports generally provide more stable power and better
compatibility than front ports.
Wireless devices can lose connection due to interference—keep receivers close to
devices.
Regular preventive maintenance like cleaning dust from ports and keyboards prolongs
device life.
Always test devices on another PC to confirm whether the issue is hardware or system-
related.
1. Dust and debris buildup – blocks airflow and causes fans to work harder.
2. Fan bearing wear – worn or damaged bearings cause rattling or loud spinning.
3. High CPU/GPU temperatures – thermal stress makes fans spin at maximum speed.
4. Poor airflow in case – obstructed cables, poor fan placement, or no intake/exhaust
balance.
5. Overclocking / high system load – fans increase speed to manage extra heat.
6. Fan misalignment or loose mounting – vibrations create additional noise.
7. Low-quality or cheap fans – some fans are inherently louder under load.
8. Coil whine mistaken for fan noise – electrical components may emit high-pitched
sounds.
2️ Diagnostic Steps
3️ Solutions
Step Action
Inspect Fans Check CPU, GPU, PSU, case fans
Clean Dust Compressed air on fans, heatsinks, vents
Check Temperatures HWMonitor, CoreTemp, GPU-Z
Inspect Bearings / Spin fans manually, tighten screws
Alignment
Test Under Load Stress tests to correlate noise with temperature
BIOS / Fan Control Adjust fan curves / RPM thresholds
Check Coil Whine Identify if noise is electrical or fan
Minimal Setup Test Disconnect non-essential fans or devices
Solutions Clean, replace/lubricate fans, improve airflow, adjust fan curves, upgrade
cooling, reduce load, check PSU/GPU
Pro Tips:
Dust is the #1 cause of loud fans — clean every 3–6 months.
Rear motherboard USB ports sometimes have built-in fans; check those as well.
High-pitched whining may not be fans; it could be GPU/PSU coil whine.
Software fan control (like MSI Afterburner or SpeedFan) can drastically reduce noise
without sacrificing cooling.
1. Insufficient system resources – low RAM, CPU overload, or disk space shortage.
2. Corrupted application files – installation errors or missing files.
3. Software conflicts – other running programs interfering with the application.
4. Outdated or incompatible software – older applications not compatible with OS or
drivers.
5. Driver issues – GPU, sound, or peripheral drivers causing instability.
6. Malware infection – malicious programs interfering with normal application behavior.
7. Operating system issues – corrupted OS files or pending updates.
8. Faulty hardware – bad RAM, failing storage devices, or overheating CPU/GPU.
9. Overclocking instability – system pushed beyond stable operating limits.
2️ Diagnostic Steps
3️ Solutions
Step Action
Check System CPU, RAM, Disk usage via Task Manager
Resources
Update / Repair Reinstall or patch software
Application
Software Conflicts Close unnecessary programs, Clean Boot
Update / Rollback GPU, audio, peripherals
Drivers
Scan Malware Full antivirus/malware scan
OS Integrity SFC /scannow, DISM, Windows updates
Test Hardware RAM, storage, CPU/GPU temperature
Event Viewer Application Errors or crash logs
Solutions Free resources, reinstall app, update drivers, repair OS, check hardware,
reset overclocking
Pro Tips:
Frequent crashes of multiple applications usually indicate OS or hardware issues.
Isolate the problem by testing one application at a time on a clean system.
Regular maintenance like disk cleanup, driver updates, and malware scans prevent most
software crashes.
Back up critical data regularly; unstable applications can corrupt files.
2️ Diagnostic Steps
3️ Solutions
Step Action
BIOS / UEFI Check boot order, SATA mode, reset defaults
Physical Reseat storage and power cables
Connections
Storage Health SMART diagnostics, listen for HDD noises
Windows Recovery Startup Repair, bootrec /fixmbr, bootrec /fixboot, bootrec
/rebuildbcd
RAM / Hardware Reseat RAM, disconnect peripherals
Check Disk chkdsk C: /f /r
Scan for Malware Bootable antivirus rescue media
Test PSU Ensure stable power delivery
Solutions Repair bootloader, replace storage, reinstall OS, correct BIOS, remove malware,
reset overclock
Pro Tips:
Always backup critical data before attempting repairs if the drive is still accessible.
Listen for hardware cues: clicking HDDs or PSU beeps indicate physical issues.
Use Windows Recovery environment as first troubleshooting step before reinstalling
OS.
Document BIOS changes to restore stable configuration if needed.
1. Sudden power loss or improper shutdown – interrupts write processes, corrupting files.
2. Faulty storage device (HDD/SSD/USB) – bad sectors or hardware failure.
3. Virus / malware infection – intentionally or unintentionally modifies or deletes files.
4. Software or application errors – improper program termination can corrupt files.
5. File system corruption – NTFS, FAT32, or exFAT structure damaged.
6. Interrupted file transfer – disconnecting storage during copy/move operations.
7. Overheating storage devices – excessive heat can damage storage cells.
8. Failed updates or improper installations – system or software updates fail mid-process.
2️ Diagnostic Steps
3️ Solutions
Step Action
Identify Affected Files Check for missing, inaccessible, or error files
Storage Health SMART diagnostics, HDD/SSD health tools
Event Logs Windows Event Viewer → Disk / File System errors
File System Check chkdsk C: /f /r or equivalent tools
Scan for Malware Full antivirus / anti-malware scan
Data Recovery Tools Recuva, EaseUS, R-Studio
Backup Restoration Full, incremental, differential, cloud
Replace Storage Faulty HDD/SSD/USB replacement
Preventive Measures UPS, backups, system restore, cooling, periodic checks
Pro Tips:
Act immediately – continued use of a corrupted drive can worsen data loss.
Do not write new data to affected drives until recovery is complete.
Regular backups are the most effective defense against file loss.
Monitoring storage health periodically can detect early signs of failure.
1. Too many startup programs – applications launching during boot delay startup.
2. Fragmented or nearly full hard drive (HDD) – reduces OS read speed.
3. Outdated or corrupted drivers – especially storage or chipset drivers.
4. Malware or virus infection – interferes with startup processes.
5. Corrupted system files – essential OS files damaged.
6. Slow or failing storage device – HDD performance degradation or SSD firmware issues.
7. BIOS / UEFI misconfiguration – slow POST due to misconfigured boot devices.
8. Excessive Windows updates or background services – pending updates can slow boot.
9. Low system resources – insufficient RAM or CPU bottleneck.
2️ Diagnostic Steps
3️ Solutions
Step Action
Check Startup Task Manager → Startup tab
Programs
Check Disk Health CHKDSK, SSD/HDD tools, fragmentation
Scan for Malware Full antivirus / anti-malware scan
System Logs Event Viewer → Boot Performance Monitoring
Update Drivers Storage, chipset, graphics drivers
Measure Boot Windows Boot Diagnostics / msconfig
Time
BIOS / UEFI Enable Fast Boot, optimize boot devices, disable unused
Solutions Disable startup programs, repair disk, update drivers, clean malware, repair OS,
hardware upgrade, fresh OS if needed
Pro Tips:
SSD upgrade is the single most effective hardware solution for slow boot times.
Minimal startup programs drastically reduce boot duration.
Regular disk health checks and malware scans prevent long-term performance
degradation.
Use Event Viewer Boot Performance logs to identify the exact culprit delaying boot.
2️ Diagnostic Steps
1. Check Power and Connection
o Ensure printer is powered on and cable is properly connected.
o For wireless printers, verify Wi-Fi connectivity and signal strength.
2. Verify Printer Status
o Control Panel → Devices and Printers → Check if printer is Online.
o Remove Pause Printing or Use Printer Offline settings.
3. Test Hardware
o Check paper tray, ink/toner levels, and for paper jams.
o Restart printer to clear internal errors.
4. Check Driver and Software
o Update or reinstall printer driver from manufacturer’s website.
o Ensure OS recognizes the correct printer.
5. Check Print Spooler Service
o Services → Print Spooler → Restart service.
o Clear stuck print jobs from C:\Windows\System32\spool\PRINTERS.
6. Test Network Configuration (for network printers)
o Ping printer IP address to check connectivity.
o Check firewall settings to allow printer communication.
7. Try Printing a Test Page
o Control Panel → Devices and Printers → Right-click printer → Print Test Page.
8. Test on Another Device
o Confirm whether the issue is printer-specific or PC-specific.
3 Solutions
Step Action
Check Power / Ensure printer powered on, connected via USB/Wi-Fi
Connection
Verify Printer Status Online, resume printing, remove pause
Hardware Check Paper jam, ink/toner, internal errors
Update / Reinstall Manufacturer’s latest drivers
Drivers
Print Spooler Restart service, clear print queue
Network Check Ping IP, firewall/antivirus rules
Test Printing Print test page
Test on Another Device Identify device vs printer issue
Solutions Fix connection, update drivers, clear queue, hardware maintenance, reset
printer if needed
Pro Tips:
Always check print spooler first when a printer is unresponsive – most Windows printer
issues are due to spooler errors.
Network printers require both PC and printer to be on the same subnet for proper
communication.
Keep drivers updated after OS upgrades to prevent incompatibility.
Regular maintenance like cleaning paper paths and checking ink/toner prevents
common printer errors.
2 Diagnostic Steps
1. Monitor System Resources
o Task Manager → Check CPU, RAM, Disk, and GPU usage during freeze.
2. Check Event Viewer Logs
o Windows → Event Viewer → System/Application logs → Look for critical errors
or warnings.
3. Check for Malware
o Run full antivirus/malware scan.
4. Inspect Storage Space
o Check free space on OS drive (C:) – ensure at least 15–20% free for paging and
temp files.
5. Update Drivers
o Graphics, storage, chipset, and peripheral drivers.
o Rollback recently updated drivers if problem started afterward.
6. Check System Files
o Run SFC /scannow and DISM /Online /Cleanup-Image /RestoreHealth.
7. Test Hardware
o RAM: Windows Memory Diagnostic or MemTest86.
o Storage: CHKDSK and SMART diagnostics.
o Monitor CPU/GPU temperatures to check for overheating.
8. Boot in Safe Mode
o Determine if freeze occurs in Safe Mode; isolates software/drivers.
9. Check for Pending Updates
o Install all Windows updates and restart system.
3️ Solutions
Step Action
Monitor CPU, RAM, Disk, GPU usage via Task Manager
Resources
Event Viewer Logs Identify critical system or application errors
Scan for Malware Full antivirus/anti-malware scan
Check Storage Ensure sufficient free space on OS drive
Update / Rollback Graphics, chipset, storage, peripherals
Drivers
Repair System SFC /scannow and DISM /RestoreHealth
Files
Hardware Test RAM, storage, CPU/GPU temperature checks
Safe Mode Boot Isolate software/driver issues
Solutions Free resources, update drivers, repair files, clean malware, maintain storage,
address overheating, replace hardware, clean boot, OS reinstall
Pro Tips:
Freezing often points to software conflicts, malware, or hardware stress; isolating the
cause is key.
Safe Mode booting is invaluable to identify whether the problem is driver/software-
related.
Keep OS and drivers updated and perform periodic preventive maintenance to avoid
freezes.
Monitor hardware temps regularly; thermal throttling can silently cause freezes.
⚠ Note: Clicking or grinding noises usually indicate imminent HDD failure. Data recovery
should be prioritized immediately.
2️ Diagnostic Steps
1. Listen Carefully
o Identify if noise is a repetitive “click” (HDD heads) or grinding (motor/platters).
2. Check Connections
o Ensure SATA and power cables are firmly connected.
o Test with different cables and ports.
3. Check Disk Health
o Use SMART diagnostics via BIOS or software (CrystalDiskInfo, HDDScan).
o Look for Reallocated Sectors Count, Pending Sector Count, and other warning
attributes.
4. Check PSU Stability
o Ensure stable power delivery; use a multimeter if necessary.
5. Minimize System Stress
o Boot system minimally to avoid overloading HDD with read/write operations.
6. Test on Another System (Optional)
o Connect the drive to a different PC or USB enclosure to verify noise source.
7. Avoid DIY Physical Repairs
o Opening HDD outside cleanroom voids warranty and can cause total data loss.
3️ Solutions
1. Immediate Backup
o Copy critical data as soon as possible; avoid prolonged use.
2. Replace Faulty HDD
o If SMART data or noise indicates failure, replace the drive.
3. Use Data Recovery Services
o For critical data, professional recovery labs can recover files from failing drives.
4. Check Cables and PSU
o Replace faulty SATA/power cables and ensure PSU provides stable voltage.
5. Avoid Physical Shock
o Handle HDD gently; keep it stationary during operation.
6. Preventive Measures for Future
o Use surge protectors or UPS to prevent power-related damage.
o Maintain regular backups.
o Monitor HDD health periodically with SMART monitoring tools.
Step Action
Listen Carefully Identify type of noise (clicking or grinding)
Check SATA/power cables, different ports
Connections
Disk Health SMART diagnostics, check for reallocated/pending sectors
PSU Stability Ensure stable voltage supply
Minimize System Boot minimally, avoid heavy read/write tasks
Stress
Test on Another Isolate noise source
System
Solutions Backup data, replace HDD, professional recovery, check cables/PSU, prevent
physical shock, use surge protection, monitor SMART
Pro Tips:
2 Diagnostic Steps
3️ Solutions
Step Action
Check System Verify OS, RAM, CPU, disk space
Requirements
Verify Installer Redownload, check file integrity
Run as Ensure installer has proper permissions
Administrator
Check Disk Free space and run CHKDSK
Check Conflicts Uninstall previous versions, close interfering apps
Disable Security Antivirus and firewall temporarily
Software
Update OS / Drivers Install pending updates and critical drivers
Installer Logs Review for specific error messages
Solutions Free resources, repair installer, run as admin, disable antivirus, uninstall
conflicts, repair disk, update OS/drivers, compatibility mode, registry repair
Pro Tips:
2️ Diagnostic Steps
3️ Solutions
Step Action
Check Reseat device, try different port/cable
Connections
Test Device on Isolate device vs system issue
Another PC
Power Supply Use powered hub for high-power devices
Update / Reinstall Device Manager → USB controllers
Drivers
USB Selective Disable via Power Options
Suspend
Event Viewer Look for USB disconnect/reconnect events
Minimal Setup Disconnect other USB devices
BIOS / UEFI Enable USB ports and legacy support
Scan for Malware Antivirus / anti-malware scan
Solutions Replace cable/device, use powered hub, update drivers, disable selective
suspend, check BIOS, remove conflicts, scan malware, replace failing hardware
Pro Tips:
Rear motherboard USB ports are more reliable than front panel ports for critical
devices.
High-power USB devices often fail without a powered hub, even if drivers are correct.
Event Viewer provides exact timestamps of disconnects, helpful for tracing root cause.
Regularly update drivers and BIOS to avoid intermittent USB issues.
2️ Diagnostic Steps
Step Action
Check Power Measure wall socket voltage with multimeter
Source
Inspect PSU Verify wattage, cables, and test with good PSU
BIOS / UEFI Check +12V, +5V, +3.3V rails
Monitoring
Event Logs Windows Event Viewer → voltage warnings
Minimal System Disconnect non-essential devices
Test
Surge Protector / Verify quality and proper rating
UPS
Inspect Check capacitors and VRMs visually
Motherboard
Environmental Ensure proper cooling and avoid high ambient temp
Factors
Solutions Use UPS/stabilizer, replace PSU, secure cables, repair motherboard, avoid
electrical interference, update BIOS, monitor load
Pro Tips:
2️ Diagnostic Steps
3️ Solutions
1. Adjust Volume and Output Device
o Ensure system, application, and device volume are correctly set.
o Select the correct playback device.
2. Update / Reinstall Drivers
o Use latest drivers from motherboard or sound card manufacturer.
o Rollback if a recent update caused the issue.
3. Check and Repair Hardware
o Replace faulty cables, speakers, or headphones.
o Test internal sound card; consider external USB audio if onboard fails.
4. Enable / Restart Audio Services
o Start Windows Audio service and set to Automatic.
5. Run Troubleshooter
o Follow Windows built-in tool recommendations to fix common audio issues.
6. Check Application Settings
o Set application-specific audio output correctly (e.g., Zoom, media players).
7. Inspect Ports and Connectors
o Reseat jacks or try different ports (HDMI, USB, 3.5mm).
8. Prevent Interference
o Keep speakers/headphones away from high-power electronics.
9. System Repair (Advanced)
o Run SFC /scannow or DISM to repair OS audio components.
Step Action
Check Volume / Ensure system, app, and device volume correct
Output Device
Test Hardware Speakers/headphones on another device, test PC audio with another device
Audio Drivers Update, reinstall, or rollback drivers
Windows Audio Ensure running and Automatic
Service
Troubleshooter Run Windows audio troubleshooter
Check Cables / Ports Inspect 3.5mm, USB, HDMI connectors
Application Settings Confirm correct audio device selected
Event Logs Check Event Viewer for audio errors
Solutions Adjust volume/device, update drivers, repair hardware, restart audio service,
run troubleshooter, fix app settings, repair OS, prevent interference
Pro Tips:
HDMI audio may default to monitor; always check playback device in Sound settings.
External USB audio adapters are useful if onboard audio fails.
Frequent driver updates after Windows updates prevent audio malfunctions.
Static or buzzing sounds are often caused by cable quality or EMI; use shielded cables.
2️ Diagnostic Steps
3️ Solutions
Keep router away from microwaves, cordless phones, or other electronic interference
sources.
Step Action
Wireless Adapter Enable, check Device Manager, reinstall driver
Network Verify SSID and password
Credentials
Signal Strength Move closer to router, use Wi-Fi analyzer
IP Configuration ipconfig /release & ipconfig /renew, set static IP if needed
Router Restart Power cycle router/modem
Update Router Ensure latest firmware installed
Firmware
Router Settings DHCP enabled, MAC filtering off, SSID broadcast on, adjust channel
Firewall / Security Allow network access, disable temporarily if needed
Test on Another Determine device-specific vs network-wide issue
Device
Solutions Enable adapter, correct credentials, improve signal, fix IP, update firmware,
adjust router, check firewall, replace hardware, check ISP, reduce interference
Pro Tips:
Use 5GHz Wi-Fi for less congestion if supported by router and device.
Regular firmware updates on routers fix many connectivity bugs.
Wi-Fi extenders or mesh networks help eliminate dead zones.
Document IP, gateway, and DNS settings before changing network settings for
troubleshooting rollback.
1. Dead or weak CMOS/BIOS battery – the small coin-cell battery on the motherboard
failing to keep time.
2. Incorrect BIOS/UEFI settings – wrong time zone, date, or synchronization settings.
3. Operating system issues – Windows time service malfunctioning or corrupted system
files.
4. Malware or virus infection – malicious software altering system clock.
5. Failed Windows Time Service (W32Time) – service responsible for time
synchronization not running.
6. Network time synchronization issues – NTP server unreachable or misconfigured.
7. Faulty motherboard or RTC (Real-Time Clock) circuitry – rare but possible hardware
failure.
8. Power outages / sudden shutdowns – resets time if CMOS battery is failing.
2️ Diagnostic Steps
3️ Solutions
1. Replace CMOS Battery
o Install a fresh coin-cell battery (usually CR2032).
o Reset BIOS settings afterward.
2. Configure BIOS / UEFI Correctly
o Set correct date, time, and time zone.
o Enable CMOS/RTC battery backup if available.
3. Start / Repair Windows Time Service
o Set W32Time service to Automatic → Start service.
o Use Command Prompt:
Step Action
CMOS Battery Inspect, test voltage (~3V), replace if old/weak
BIOS / UEFI Set correct date, time, time zone; enable battery backup
Windows Time Start / set to Automatic, resync using w32tm commands
Service
Internet Time Enable NTP sync, use reliable time server
Sync
Malware Scan Full antivirus / anti-malware scan
Event Logs Check Event Viewer for W32Time or system errors
OS Repair Run SFC and DISM to fix system file corruption
Solutions Replace CMOS battery, configure BIOS, repair W32Time, enable NTP sync, remove
malware, repair OS, replace motherboard if needed
Pro Tips:
CMOS battery is often the cause if the system resets clock after power off.
Keep NTP synchronization enabled to automatically correct minor clock drift.
Document BIOS changes after battery replacement to restore previous configurations.
Malware affecting system time can cause certificate or update failures; always scan.
26. Problem: Blue Light / POST Errors on Motherboard
1️ Possible Causes
1. Faulty or improperly seated RAM – memory modules not fully inserted or defective.
2. CPU not seated correctly or defective – improper installation or thermal damage.
3. Power supply issues – insufficient or unstable voltage to motherboard/components.
4. Faulty GPU / graphics card – incorrect installation, damaged card, or driver conflicts.
5. Short circuits on motherboard – caused by misplaced standoffs, screws, or conductive
debris.
6. Peripheral or external device conflicts – USB devices or expansion cards causing
POST failure.
7. BIOS / UEFI corruption or misconfiguration – settings incompatible with installed
hardware.
8. Overheating or thermal issues – CPU or VRM overheating during POST.
9. Defective motherboard components – damaged capacitors, traces, or circuits.
2️ Diagnostic Steps
3️ Solutions
1. Reseat or Replace RAM
o Ensure proper installation; replace defective modules.
2. Reinstall or Replace CPU
o Correct orientation, clean old thermal paste, apply new paste, and reseat cooler.
3. Check and Repair GPU
o Reseat graphics card; try different PCIe slot; replace if defective.
4. Verify and Replace PSU if Needed
o Use reliable PSU with adequate wattage and stable rails.
5. Disconnect Conflicting Devices
o Remove USB drives, expansion cards, or external peripherals during POST.
6. Reset BIOS / UEFI
o Clear CMOS to restore default settings; update BIOS if necessary.
7. Inspect Motherboard for Damage
o Replace motherboard if shorted or components are damaged.
8. Ensure Proper Cooling
o Reinstall CPU cooler, ensure fan connection, and verify airflow.
9. Follow POST Beep / LED Codes
o Troubleshoot specific components as indicated by motherboard signals.
Step Action
Observe POST Codes Use manual to identify component causing failure
Check RAM Reseat, test one module at a time, replace if faulty
Check CPU Reseat, inspect pins, apply thermal paste correctly
Check GPU Reseat, try different PCIe slot, test integrated graphics
Test PSU Verify voltage stability and sufficient wattage
Disconnect Boot minimally to isolate fault
Peripherals
Reset BIOS / CMOS Restore defaults, update BIOS if needed
Inspect Check for damaged capacitors, shorts, burn marks
Motherboard
Ensure Cooling Proper heatsink/fan installation and airflow
Solutions Replace defective RAM/CPU/GPU/PSU, reset BIOS, repair motherboard,
follow POST codes
Pro Tips:
Blue LEDs on modern motherboards usually indicate CPU, RAM, GPU, or boot
device errors – check the manual for exact meaning.
One-component-at-a-time testing is crucial to isolate the faulty part.
Always discharge residual power and use anti-static precautions when handling
motherboard components.
Regular BIOS updates can prevent POST errors caused by new hardware compatibility
issues.
2️ Diagnostic Steps
3️ Solutions
Step Action
Check Physical Reseat SATA/NVMe cables, check power connectors
Connections
Inspect Drive Power Listen for HDD spin, check SSD activity LEDs
BIOS / UEFI Settings Enable controller, set correct mode (AHCI/IDE/RAID), enable CSM if needed
Update BIOS / Install latest motherboard firmware
Firmware
Test Drive Connect drive to another system to verify functionality
Initialize / Format Initialize unformatted drives using Disk Management
Drive
Swap Ports / Slots Test different SATA / M.2 ports on motherboard
PSU Check Ensure stable and sufficient power delivery
Solutions Reseat cables, configure BIOS, update firmware, replace drive, initialize, swap
ports, check PSU, replace motherboard if needed
Pro Tips:
AHCI mode is recommended for SSDs to ensure full performance; IDE may limit
features.
NVMe SSDs may not be detected on older motherboards without firmware updates.
Always test new drives on a secondary PC to isolate hardware vs motherboard issues.
Document BIOS changes before updating firmware to avoid losing previous settings.
2️ Diagnostic Steps
3️ Solutions
Step Action
Test Device On another PC to isolate device vs system issue
Check Battery / Recharge or replace batteries for wireless devices
Power
Update / Reinstall Device Manager → latest drivers from manufacturer
Drivers
USB Port / Use motherboard ports, avoid overloaded hubs
Bandwidth
Monitor System Task Manager → CPU/RAM/Disk usage
Resources
Disable Close unnecessary processes
Background Apps
Wireless Move closer to receiver, avoid 2.4 GHz interference
Interference
Polling Rate / Adjust device polling rate and disable power-saving features
Settings
Test Wired Confirm if lag is wireless-related
Connection
Solutions Replace/recharge device, update drivers, switch ports, optimize system,
adjust wireless setup, optimize OS, replace faulty device
Pro Tips:
1. Loose or damaged video cable – HDMI, DisplayPort, DVI, or VGA connections faulty.
2. Incorrect refresh rate or resolution – OS or GPU settings incompatible with monitor.
3. Outdated or corrupted GPU drivers – causing display instability.
4. Faulty GPU / graphics card – hardware malfunction or overheating.
5. Electromagnetic interference – nearby devices causing screen flicker.
6. Monitor hardware issue – aging display, backlight inverter, or internal circuitry failure.
7. Power supply instability – monitor or GPU not receiving stable power.
8. Software conflicts – applications causing abnormal GPU behavior (games, video editing
apps).
9. Overclocked GPU or display – settings exceeding safe operational limits.
2️ Diagnostic Steps
3 Solutions
Step Action
Check Cable Reseat or replace HDMI/DP/DVI/VGA cable
Connections
Test Monitor Connect to another PC to isolate issue
GPU Settings Ensure correct resolution and refresh rate
Update / Reinstall Use official GPU drivers, rollback if needed
Drivers
Inspect GPU Check for dust, cooling, fan operation
Hardware
Power Supply Ensure stable PSU and monitor power
Minimal Setup Boot with essential peripherals only
Electromagnetic Remove nearby electronic devices
Interference
Reset Monitor Use factory settings via OSD menu
Solutions Replace cables, adjust settings, update drivers, repair/replace GPU or
monitor, ensure stable power, reduce interference, reset factory
defaults
Pro Tips:
High refresh rate monitors are sensitive to cable quality; always use certified cables.
Flickering only in certain apps may indicate software conflicts or GPU load issues.
Electromagnetic interference from speakers, Wi-Fi routers, or power adapters is
common; reposition devices.
Monitor aging can cause flickering even with correct cables and drivers; consider testing
on a newer monitor.
Causes:
Diagnostics:
Monitor temperatures
Test PSU output
Run MemTest
Scan system for malware
Solutions:
Replace PSU
Clean/replace fans, reapply thermal paste
Replace faulty RAM
Remove malware
2️ Diagnostic Steps
3️ Solutions
1. Improve Cooling
o Clean GPU fans, reseat heatsink, reapply thermal paste.
o Ensure adequate airflow in case/chassis.
2. Remove Overclocking
o Set GPU and VRAM to default manufacturer speeds.
3. Update / Reinstall Drivers
o Official drivers from NVIDIA, AMD, or Intel.
4. Replace Faulty Hardware
o Replace GPU if artifacting persists after cooling and driver fixes.
o Replace damaged video cables or monitor if necessary.
5. Ensure Stable Power
o Replace or upgrade PSU if insufficient or unstable.
6. Check PCIe Slot / Reseat GPU
o Reinstall GPU, try another PCIe slot to rule out motherboard issues.
7. Test Under Controlled Load
o Use stress tests to confirm stability after adjustments.
Step Action
Monitor GPU Use HWMonitor/MSI Afterburner; check under load
Temperature
Check Drivers Update or rollback GPU drivers
Minimal Disconnect extra peripherals/displays
Configuration
Check Cables / Test different video cables and monitor
Monitor
Reset Overclocking Return GPU/VRAM to default clocks
Inspect Physical GPU Clean dust, check PCB, reseat heatsink, reapply thermal paste
Test PSU Ensure stable power, swap if needed
Stress Test FurMark / 3DMark to reproduce artifacts
Try Another System Determine if GPU-specific issue
Solutions Improve cooling, remove overclocking, update drivers, replace
GPU/cables/monitor, ensure stable PSU, reseat GPU, stress test
Pro Tips:
1️ Possible Causes
1. Overheating (CPU / GPU / VRM) – thermal protection forces power-off.
2. Faulty or insufficient Power Supply Unit (PSU) – unstable voltage output.
3. Power surge or unstable electricity – sudden loss of input power.
4. Short circuit inside system – motherboard or loose screw causing shutdown.
5. Defective RAM – memory faults triggering hardware protection.
6. Motherboard failure – damaged VRMs, capacitors, or power circuits.
7. Loose power connectors – CPU (8-pin) or motherboard (24-pin) cables.
8. BIOS / UEFI misconfiguration – incorrect voltage, overclocking, or thermal limits.
9. Overclocking instability – CPU, GPU, or RAM clocks too aggressive.
10. Failing storage device – electrical fault causing system protection shutdown.
11. UPS or surge protector failure – unstable output.
12. Operating system power policy errors – aggressive power settings.
13. Malware / firmware-level attacks (rare) – forced shutdowns.
2️ Diagnostic Steps
1. Check Temperature Immediately
o Use HWMonitor / BIOS hardware monitor
o CPU > 90°C or GPU > 85°C = critical
2. Inspect PSU
o Verify wattage is sufficient
o Listen for PSU fan failure
o Smell for burnt odor
3. Check Power Connections
o Reseat 24-pin motherboard cable
o Reseat 8-pin CPU power cable
o Check GPU power connectors
4. Review Event Viewer
o Windows → Event Viewer → System
o Look for Kernel-Power Event ID 41
5. Test Minimal Hardware Setup
o Disconnect non-essential components
o Boot with CPU, one RAM stick, and system drive
6. Check BIOS Settings
o Reset BIOS to default
o Disable overclocking
o Check voltage and thermal limits
7. Test RAM
o Run Windows Memory Diagnostic or MemTest86
8. Check Electrical Stability
o Test wall outlet
o Bypass UPS/surge protector temporarily
3️ Solutions
1. Fix Overheating
o Clean dust from CPU/GPU coolers
o Reapply thermal paste
o Improve airflow
2. Replace Faulty PSU
o Use certified PSU (80+ Bronze or higher)
o Ensure sufficient wattage
3. Secure All Power Connections
o Firmly seat all internal power cables
4. Reset BIOS / Disable Overclocking
o Load optimized defaults
o Avoid manual voltage tuning
5. Replace Faulty RAM
o Remove defective module
o Use matched RAM pairs
6. Fix Electrical Issues
o Use UPS with AVR
o Avoid overloaded sockets
7. Replace Motherboard (if needed)
o Required if VRMs or power circuitry is damaged
8. Scan for Malware
o Perform full antivirus and firmware scan
5️ Preventive Measures
Clean system every 3–6 months
Monitor temperatures regularly
Use high-quality PSU
Avoid extreme overclocking
Use UPS with AVR
Keep BIOS updated
Exam Tip
1️ Possible Causes
1. Faulty AC adapter or charging cable – insufficient or unstable power delivery.
2. Damaged DC-in jack / charging port – loose or broken internal connection.
3. Worn-out or degraded battery – battery has reached end of life.
4. Incorrect or incompatible charger – wrong voltage, current, or wattage.
5. Battery driver or firmware issues – OS not communicating properly with battery.
6. BIOS / UEFI charging limitation settings – charging disabled or capped.
7. Overheating battery or system – charging paused to prevent damage.
8. Power management software conflicts – vendor utilities blocking charging.
9. Operating system corruption – power services malfunctioning.
10. Motherboard charging circuit failure – damaged power ICs.
11. Battery calibration error – inaccurate charge level reporting.
12. Use of counterfeit battery or charger – safety shutdown by firmware.
2️ Diagnostic Steps
1. Check Power Adapter
o Confirm LED on charger is ON
o Test with a known-good charger of same rating
2. Inspect Charging Port
o Check for looseness or intermittent charging
o Wiggle plug gently to detect connection issues
3. Check Battery Status
o BIOS/UEFI → Battery health info
o Windows → Battery report (powercfg /batteryreport)
4. Check Power Icon Message
o “Plugged in, not charging” → software or battery issue
o No charging indication → hardware or adapter issue
5. Remove and Reseat Battery (if removable)
o Power off, unplug, remove battery
o Hold power button 15–30 seconds
o Reinsert battery and test
6. Check Device Manager
o Batteries → Microsoft ACPI-Compliant Control Method Battery
o Disable and re-enable or uninstall and reboot
7. Enter BIOS / UEFI
o Check charging thresholds or battery conservation mode
o Reset BIOS to default settings
8. Test Without Battery
o Remove battery and run on AC power
o If system runs fine → battery is faulty
3️ Solutions
1. Replace Faulty Charger
o Use original or manufacturer-approved adapter
2. Replace Battery
o Necessary if battery health < 50% or not detected
3. Repair or Replace DC-in Jack
o Requires motherboard-level repair or replacement
4. Reinstall Battery Drivers
o Uninstall ACPI battery driver and reboot
5. Update BIOS / Firmware
o Fix charging logic or compatibility issues
6. Disable Charging Limits
o Turn off battery conservation or charging cap modes
7. Cool Down System
o Clean vents and fans
o Avoid charging in hot environments
8. Motherboard Repair
o Replace charging ICs if circuit failure exists
5️ Preventive Measures
Use original charger
Avoid deep discharge (0%)
Keep battery between 20%–80%
Avoid heat exposure
Update BIOS regularly
Do not leave laptop plugged in 24/7 (unless supported)
Exam Tip
If a laptop works on AC power but shuts down immediately when unplugged, the battery is
faulty even if detected by the OS.
1️ Possible Causes
1. Dust-clogged cooling system – blocked vents and heatsinks.
2. Failed or weak cooling fan – insufficient heat dissipation.
3. Dried or poorly applied thermal paste – poor heat transfer from CPU/GPU.
4. Blocked air vents – using laptop on bed, sofa, or lap.
5. High CPU/GPU usage – heavy applications or background processes.
6. Malware or runaway processes – causing constant high load.
7. Poor ambient ventilation – hot room environment.
8. Aging hardware – degraded cooling efficiency.
9. BIOS / firmware issues – incorrect thermal control logic.
10. Overclocking or undervolting misconfiguration – unstable thermal behavior.
11. Faulty temperature sensors – incorrect readings triggering shutdown.
12. Damaged heat pipe – internal cooling system failure.
2️ Diagnostic Steps
1. Monitor Temperature
o Use HWMonitor, Core Temp, or BIOS hardware monitor
o CPU > 90°C or GPU > 85°C = critical
2. Listen to Cooling Fan
o Check if fan spins continuously or intermittently
o No fan noise may indicate fan failure
3. Check Vent Airflow
o Weak or hot air = blocked cooling system
4. Inspect CPU Usage
o Task Manager → Performance
o Identify processes consuming excessive resources
5. Check BIOS / UEFI
o Verify thermal and fan control settings
o Reset BIOS to default if unsure
6. Visual Inspection
o Look for dust buildup in vents and exhaust
o Check fan and heatsink alignment (if accessible)
7. Stress Test Carefully
o Use light stress testing
o Shutdown during test confirms thermal issue
3️ Solutions
1. Clean Cooling System
o Use compressed air on vents and fan
o Professional internal cleaning recommended
2. Replace Thermal Paste
o Apply high-quality thermal compound
o Ensure proper heatsink seating
3. Replace Faulty Fan
o Required if fan is noisy or non-functional
4. Improve Usage Conditions
o Place laptop on flat, hard surface
o Use cooling pad if necessary
5. Reduce System Load
o Close unnecessary applications
o Disable startup programs
6. Scan for Malware
o Perform full antivirus scan
7. Update BIOS / Firmware
o Fix fan control and thermal management bugs
8. Adjust Power Settings
o Use balanced or power-saving mode
5️ Preventive Measures
Clean vents every 3–6 months
Replace thermal paste every 2–3 years
Avoid soft surfaces
Keep OS and BIOS updated
Monitor temperatures regularly
Use cooling pads for heavy workloads
Exam Tip
1️ Possible Causes
1. Old or low-quality CMOS battery – CR2032 battery has reached end of life.
2. Defective CMOS battery – new but faulty or counterfeit battery.
3. Power leakage on motherboard – damaged CMOS circuit drawing excess current.
4. Frequent power disconnection – system always unplugged or laptop battery removed.
5. Faulty motherboard components – bad capacitors or RTC circuit failure.
6. Incorrect battery installation – loose contact or wrong polarity.
7. Short circuit near CMOS battery holder – corrosion or dust.
8. BIOS firmware bug – excessive CMOS power usage.
9. Environmental factors – high temperature reducing battery lifespan.
10. Laptop main battery failure – CMOS relies partially on main battery.
11. Power surge damage – RTC circuit partially damaged.
12. Aftermarket motherboard battery holder defect – poor electrical contact.
2️ Diagnostic Steps
1. Observe Symptoms
o Date/time resets on every boot
o BIOS settings revert to default
o POST error: “CMOS Checksum Error”
2. Test Battery Voltage
o Use multimeter
o Normal CR2032 ≈ 3.0V
o Below 2.7V = replace
3. Replace CMOS Battery
o Use a known-good branded CR2032
o Ensure correct polarity (+ side up)
4. Check Battery Holder
o Inspect for looseness or corrosion
o Clean gently with isopropyl alcohol
5. Check BIOS Version
o Update BIOS if issue persists
6. Check Power Behavior
o Leave system unplugged overnight
o Recheck BIOS time next day
7. Inspect Motherboard
o Look for bulging capacitors or corrosion near RTC area
8. Laptop-Specific Test
o Check if main battery holds charge
o Remove main battery and test CMOS behavior
3️ Solutions
1. Replace CMOS Battery
o Use high-quality branded CR2032
o Avoid cheap or old stock batteries
2. Clean Battery Contacts
o Remove oxidation or dust
o Ensure firm contact
3. Update BIOS / UEFI
o Fix RTC power-management bugs
4. Ensure Proper Power Connection
o Avoid unplugging desktop frequently
o Keep laptop battery installed
5. Repair Motherboard RTC Circuit
o Required if battery drains in days
o Component-level repair or board replacement
6. Replace Motherboard (Last Resort)
o Necessary if RTC circuit is permanently damaged
5️ Preventive Measures
Replace CMOS battery every 3–5 years
Use quality branded batteries
Avoid moisture exposure
Keep system in moderate temperature
Update BIOS when recommended
Use surge protector / UPS
Exam Tip
If BIOS time resets even after installing a new CMOS battery, the motherboard’s RTC
(Real-Time Clock) circuit is likely faulty.
1️ Possible Causes
1. Faulty USB cable or port – damaged or low-quality cable.
2. Insufficient power supply – especially common with portable HDDs.
3. USB controller driver issues – missing or corrupted drivers.
4. Disk not initialized or partition missing – new or corrupted drive.
5. File system corruption – OS cannot mount the drive.
6. Drive letter conflict – drive exists but not assigned a letter.
7. Disabled USB port – BIOS or OS power management.
8. Physical HDD failure – damaged motor, head, or controller board.
9. Faulty external enclosure – SATA-to-USB bridge failure.
10. Outdated OS or firmware – incompatibility with external drive.
11. Virus or malware infection – hides or blocks drive access.
12. Wrong file system (Linux/macOS format) – not readable by Windows.
13. Over-current protection triggered – USB port shuts down power.
14. Loose internal SATA connection (desktop) – cable disconnected.
15. USB selective suspend feature – power-saving disables the drive.
2️ Diagnostic Steps
1. Check Physical Connection
o Try a different USB cable
o Try another USB port (prefer rear ports on desktop)
2. Check Power Supply
o Use Y-cable or powered USB hub
o Listen for drive spin-up sound
3. Check Disk Management
o Windows → Disk Management
o Look for Unallocated or Offline disk
4. Check Device Manager
o Disk Drives / USB Controllers
o Look for warning symbols
5. Assign Drive Letter
o Right-click drive → Change Drive Letter and Paths
6. Test on Another Computer
o Confirms whether issue is drive or system related
7. Check BIOS / UEFI
o For internal HDD: verify detection in BIOS
o For external: check USB configuration enabled
8. Inspect External Enclosure
o Remove HDD and test via SATA (if possible)
9. Check for Disk Errors
o Run CHKDSK (only if drive is detected)
10. Listen for Unusual Sounds
o Clicking or no spin indicates mechanical failure
3️ Solutions
1. Replace USB Cable
o Use high-quality, short cable
2. Use Powered USB Hub
o Ensures sufficient power for HDD
3. Initialize or Format Drive
o Disk Management → Initialize Disk
o (⚠ Data loss risk)
4. Assign Drive Letter
o Resolve drive letter conflicts
5. Update / Reinstall Drivers
o USB controller and chipset drivers
6. Disable USB Power Saving
o Device Manager → USB Root Hub → Power Management
7. Repair File System
o Use CHKDSK or recovery tools
8. Replace External Enclosure
o Common failure point
9. Recover Data
o Use professional recovery services if HDD is failing
10. Replace Drive (If Dead)
5️ Preventive Measures
Always use Safe Remove Hardware
Avoid sudden unplugging
Use surge protector
Avoid physical shocks
Keep backups
Periodically check SMART health
Exam Tip
If an external HDD appears in Disk Management but not in File Explorer, the issue is
usually a missing drive letter or unformatted partition—not hardware failure.
1️ Possible Causes
1. Loose or damaged display cable (LVDS/eDP) – common hinge-area issue.
2. Outdated or corrupted graphics driver – causes unstable display refresh.
3. Incorrect screen refresh rate – mismatch with panel specification.
4. Faulty LCD panel – failing backlight or panel controller.
5. Inverter/backlight failure (older laptops) – unstable brightness.
6. GPU or integrated graphics failure – especially during load.
7. Overheating GPU/CPU – thermal throttling affects display output.
8. Power management issues – aggressive brightness or refresh changes.
9. BIOS / firmware bugs – incorrect display initialization.
10. Damaged hinges – stresses display cable during open/close.
11. External electromagnetic interference – nearby devices affecting signal.
12. Operating system corruption – display services malfunction.
13. Adaptive brightness / dynamic contrast – causes visible flicker.
14. Low or unstable battery power – voltage fluctuation affects display.
15. Aftermarket or incompatible LCD replacement – panel mismatch.
2️ Diagnostic Steps
1. Check if Flicker Appears in BIOS
o Flicker in BIOS → hardware issue
o No flicker → driver or OS issue
2. Connect External Monitor
o External monitor stable → laptop screen/cable issue
o Both flicker → GPU or driver issue
3. Move Screen Slowly
o Flicker when opening/closing lid → loose display cable
4. Update / Reinstall Graphics Driver
o Use manufacturer-approved driver
5. Check Refresh Rate
o Display Settings → Advanced → Match native refresh rate
6. Disable Adaptive Brightness
o Power settings → Turn off adaptive brightness
7. Check Temperature
o Monitor CPU/GPU temps during flicker
8. Boot into Safe Mode
o No flicker → software or driver issue
3️ Solutions
1. Reseat or Replace Display Cable
o Requires partial disassembly
2. Update or Roll Back Graphics Drivers
o Avoid beta drivers
3. Set Correct Refresh Rate
o Match manufacturer specifications
4. Replace LCD Panel
o Required if panel backlight is failing
5. Update BIOS / Firmware
o Fix display initialization bugs
6. Disable Power-Saving Display Features
o Adaptive brightness, dynamic contrast
7. Fix Overheating
o Clean cooling system
8. Replace GPU / Motherboard (If Needed)
o Necessary for persistent GPU-level flicker
5️ Preventive Measures
Open/close laptop gently
Avoid pressure on lid
Keep drivers updated
Clean cooling system
Use proper power adapters
Avoid cheap replacement panels
Exam Tip
If a laptop display flickers only when the lid moves, the primary suspect is a loose or
damaged LVDS/eDP display cable.
1️ Possible Causes
1. Incompatible operating system version – software designed for older/newer OS.
2. Wrong driver architecture – 32-bit driver on 64-bit OS or vice versa.
3. Outdated drivers – incompatible with current OS updates.
4. Corrupted driver installation – incomplete or interrupted install.
5. Conflicting drivers – multiple drivers controlling same hardware.
6. Unsigned or unofficial drivers – blocked by OS security.
7. Hardware not supported – legacy devices without modern drivers.
8. Incorrect firmware / BIOS version – mismatch with drivers.
9. Third-party system utilities conflicts – tuning or optimization tools.
10. Missing system dependencies – .NET Framework, Visual C++ redistributables.
11. Automatic OS updates – overwrite working drivers.
12. Virtualization or hypervisor conflicts – affects drivers and low-level software.
13. Incorrect installation order – chipset not installed first.
14. Security software blocking drivers – antivirus or firewall interference.
15. Application hardcoded limitations – software coded for specific hardware/OS.
2️ Diagnostic Steps
1. Read the Error Message Carefully
o Check exact compatibility warning or code
2. Check OS Version & Architecture
o Verify Windows version, build number, 32/64-bit
3. Check Device Manager
o Look for yellow warning symbols
o Check driver status messages
4. Check Software System Requirements
o Compare with installed hardware/OS
5. Review Event Viewer
o Application and System logs for driver errors
6. Test in Safe Mode
o If works → conflict with third-party software
7. Check Driver Signature
o Confirm driver is digitally signed
8. Check Installation Order
o Chipset → GPU → LAN → Audio → Others
9. Disable Antivirus Temporarily
o Test driver installation (re-enable after)
3️ Solutions
1. Install Correct Driver Version
o Match OS version and architecture
2. Update Operating System
o Install required service packs and updates
3. Use Compatibility Mode
o Run software as older Windows version
4. Clean Driver Reinstallation
o Uninstall → reboot → reinstall
o Use DDU for graphics drivers
5. Install Required Dependencies
o .NET Framework, Visual C++ Redistributables
6. Update BIOS / Firmware
o Ensure hardware compatibility
7. Disable Conflicting Utilities
o Remove driver boosters or tuners
8. Manually Install Legacy Drivers
o Device Manager → Have Disk method
9. Block Automatic Driver Updates
o Prevent OS from overwriting stable drivers
10. Replace Unsupported Hardware
o Required if no compatible drivers exist
5️ Preventive Measures
Always verify system requirements
Download drivers from manufacturer only
Install chipset drivers first
Create restore point before updates
Avoid driver-booster software
Keep BIOS and firmware updated
Exam Tip
Most driver compatibility issues are caused by incorrect driver architecture or OS version
mismatch, not hardware failure.
1️ Possible Causes
1. Disabled keyboard or touchpad settings – accidentally turned off via function keys.
2. Corrupted or missing drivers – OS cannot communicate with input devices.
3. Operating system errors – system services not functioning properly.
4. Liquid spill damage – corrosion under keyboard or touchpad.
5. Dust or debris under keys – mechanical obstruction.
6. Loose internal ribbon cable – common after repair or drop.
7. Touchpad firmware issues – outdated or incompatible firmware.
8. Third-party software conflict – gesture utilities or driver tools.
9. BIOS / UEFI misconfiguration – internal keyboard/touchpad disabled.
10. Malware infection – input devices blocked or hijacked.
11. Electrostatic discharge (ESD) damage – internal controller affected.
12. Physical wear and tear – keys or touchpad surface worn out.
13. External device conflict – external keyboard disabling internal one.
14. Wrong regional keyboard layout – incorrect key mapping.
15. Motherboard controller failure – keyboard/touchpad controller damaged.
2️ Diagnostic Steps
1. Test in BIOS / UEFI
o If not working in BIOS → hardware issue
o Works in BIOS → software/driver issue
2. Check Function Keys
o Look for Fn + key icons (touchpad disable key)
3. Check Device Manager
o Keyboards / Human Interface Devices
o Look for errors or missing devices
4. Test External Keyboard/Mouse
o Confirms OS usability for troubleshooting
5. Boot into Safe Mode
o If works → software or driver conflict
6. Check Keyboard Layout
o Settings → Language → Keyboard layout
7. Inspect for Liquid Damage
o Sticky keys, corrosion, or smell
8. Check BIOS Settings
o Ensure internal keyboard/touchpad enabled
3️ Solutions
1. Enable Keyboard / Touchpad
o Use Fn keys or BIOS settings
2. Reinstall or Update Drivers
o Use manufacturer-specific drivers
3. Reset Touchpad Settings
o Restore default gestures
4. Clean Keyboard
o Use compressed air or professional cleaning
5. Reseat Ribbon Cable
o Requires careful disassembly
6. Remove Conflicting Software
o Uninstall third-party gesture utilities
7. Run Malware Scan
o Full system scan
8. Replace Keyboard or Touchpad
o Required for liquid damage or physical wear
9. Update BIOS / Firmware
o Fix compatibility issues
10. Motherboard Repair
o Needed if controller circuit fails
5️ Preventive Measures
Avoid liquid near laptop
Clean keyboard regularly
Use protective keyboard cover
Handle laptop gently
Update drivers carefully
Avoid forced shutdowns
Exam Tip
If a laptop keyboard and touchpad do not work even in BIOS, the problem is hardware-
related, not an operating system issue.
1️ Possible Causes
1. Network congestion – too many users or devices sharing bandwidth.
2. Weak Wi-Fi signal – distance, walls, or interference.
3. Faulty Ethernet cable – damaged or low-quality cable.
4. Router or modem overload – aging or misconfigured network devices.
5. ISP issues – upstream packet loss or routing problems.
6. Wireless interference – nearby networks, microwaves, Bluetooth devices.
7. Outdated network drivers – inefficient packet handling.
8. Incorrect MTU settings – packet fragmentation.
9. Malware or background downloads – consuming bandwidth.
10. QoS misconfiguration – wrong traffic prioritization.
11. Firewall or security software interference – packet inspection delays.
12. Duplex mismatch – speed/duplex settings conflict.
13. DNS resolution delays – slow name resolution.
14. Server-side issues – remote server overloaded.
15. Hardware failure – failing NIC or router ports.
2️ Diagnostic Steps
1. Measure Latency and Packet Loss
o Use ping, tracert, or pathping
o Packet loss > 1% is abnormal
2. Test Local Network First
o Ping router (e.g., [Link])
o High latency here → local issue
3. Switch Connection Type
o Test Ethernet vs Wi-Fi
4. Check Signal Strength (Wi-Fi)
o Move closer to router
o Check RSSI levels
5. Inspect Cables
o Replace Ethernet cable (Cat5e/Cat6)
6. Restart Network Devices
o Modem → Router → PC
7. Check Network Usage
o Task Manager → Network
o Identify heavy background traffic
8. Update Network Drivers
o Download from manufacturer website
9. Test Another Device
o Confirms whether issue is system-specific
10. Check Router Logs
o Look for dropped packets or errors
3️ Solutions
1. Reduce Network Congestion
o Limit active devices
oSchedule downloads during off-peak hours
2. Use Wired Connection
o Ethernet offers lower latency than Wi-Fi
3. Optimize Wi-Fi
o Change Wi-Fi channel
o Use 5 GHz band where available
4. Replace Faulty Cables
o Use certified Cat5e/Cat6 cables
5. Update Router Firmware
o Fix bugs and performance issues
6. Configure QoS Correctly
o Prioritize real-time traffic (VoIP, gaming)
7. Disable Unnecessary Background Apps
o Stop auto-updates and cloud sync temporarily
8. Scan for Malware
o Remove bandwidth-consuming malware
9. Change DNS Servers
o Use faster DNS (e.g., ISP, public DNS)
10. Contact ISP
o If packet loss occurs beyond local network
5️ Preventive Measures
Use quality networking equipment
Keep router firmware updated
Secure network to prevent unauthorized access
Place router centrally
Monitor network usage
Use wired connections for critical tasks
Exam Tip
If packet loss occurs when pinging the local router, the problem is within the local
network—not the ISP.
40. Problem: BIOS Update Failure / Bricked Motherboard
(After a failed BIOS update, the system fails to boot, shows no display, emits beep codes, or
becomes completely unresponsive — commonly referred to as a “bricked” motherboard.)
1️ Possible Causes
1. Power loss during BIOS update – sudden shutdown or unplugging interrupts flashing.
2. Incorrect BIOS version – using a BIOS file not designed for the motherboard model.
3. Corrupted BIOS file – incomplete or damaged download.
4. Failed flashing utility – software crashes or errors during update.
5. Virus or malware – rare, but can corrupt BIOS during update.
6. Bad CMOS battery – unstable voltage during flashing.
7. Overclocked CPU/GPU/RAM – unstable system can corrupt BIOS during flash.
8. Faulty motherboard components – damaged EEPROM or BIOS chip.
9. Improper update method – wrong flashing procedure (USB, DOS, Windows-based).
10. Interference from connected peripherals – sometimes USB devices interfere with
flashing.
11. Flash memory wear – repeated BIOS updates exceeding chip endurance.
2️ Diagnostic Steps
1. Observe POST / Beep Codes
o No POST, continuous beeps, or blinking LEDs indicate BIOS corruption.
2. Check Motherboard LEDs
o Many modern boards have Q-LED or Debug LED codes for CPU, DRAM, VGA,
BOOT.
3. Attempt BIOS Recovery
o Check if motherboard supports dual BIOS or BIOS recovery mode.
4. Try CMOS Reset
o Remove CMOS battery or use jumper to reset settings.
5. Use BIOS Flashback Feature (if available)
o Plug in USB with correct BIOS file, press dedicated flashback button.
6. Test Minimal Configuration
o Disconnect peripherals; keep only CPU, RAM, GPU (if required).
7. Inspect for Physical Damage
o Burnt traces or damaged BIOS chip.
3️ Solutions
1. BIOS Recovery / Dual BIOS
o Some motherboards automatically recover using secondary BIOS chip.
o Use recovery jumper or flashback USB method.
2. Re-flash BIOS with Correct File
o Download verified BIOS from manufacturer
o Use proper procedure (USB/FDD/DOS/Windows tool)
3. Reset CMOS
o Clears corrupt settings that may prevent booting.
4. Replace CMOS Battery
o Provides stable voltage during flashing process.
5. Professional BIOS Chip Replacement
o Reprogram or replace EEPROM chip on motherboard.
6. Replace Motherboard
o If BIOS is irrecoverably corrupted and no recovery option exists.
5️ Preventive Measures
Use stable power source or UPS during BIOS update
Verify motherboard model and correct BIOS version
Use manufacturer-provided flashing utilities
Avoid interrupts during flash (do not unplug/power off)
Update BIOS only if necessary (stability or feature improvement)
Keep CMOS battery in good condition
Exam Tip
A bricked motherboard after a BIOS update is almost always caused by a power loss or
incorrect BIOS file. Modern boards with dual BIOS or flashback features can often
recover without replacing the board.
1️ Possible Causes
1. Wear leveling / NAND cell degradation – SSD memory cells have limited write cycles
(P/E cycles).
2. Overfilled SSD – performance drops when drive exceeds ~75–80% capacity.
3. Fragmented file system (for older OS versions) – increases access latency.
4. TRIM command not enabled – prevents garbage collection, reducing speed over time.
5. Outdated SSD firmware – firmware bugs can slow performance.
6. Excessive write amplification – frequent small writes wear cells faster.
7. Thermal throttling – high temperatures reduce SSD speed to prevent damage.
8. Insufficient over-provisioning – less spare area to manage wear leveling.
9. Driver issues – outdated NVMe/SATA drivers reduce throughput.
10. Background operations / heavy usage – continuous read/write reduces performance.
11. Bad blocks / weak sectors – logical or physical damage to NAND cells.
12. Faulty SATA/NVMe controller or cable – connection issues can mimic SSD
slowdown.
13. Power management settings – aggressive sleep or low-power states may reduce
throughput.
14. OS indexing or antivirus scanning – frequent access slows perceived speed.
15. Using incompatible storage interface – e.g., SATA III SSD on SATA II port reduces
speed.
2️ Diagnostic Steps
1. Check SSD Health
o Use tools: CrystalDiskInfo, Samsung Magician, or manufacturer utilities.
o Look for Total Bytes Written (TBW), health %, and bad blocks.
2. Benchmark Performance
o Use CrystalDiskMark, ATTO, or AS SSD benchmark.
o Compare with manufacturer’s rated speed.
3. Check Available Space
o SSD nearing full capacity → performance drop.
4. Verify TRIM
o Windows: fsutil behavior query DisableDeleteNotify
o 0 = TRIM enabled, 1 = disabled
5. Monitor Temperature
o Excessive heat → thermal throttling
6. Check Firmware & Drivers
o Ensure latest SSD firmware and SATA/NVMe drivers installed
7. Run System Maintenance
o Check for background processes causing I/O bottlenecks
8. Inspect Connection
o Use quality SATA/NVMe slot and cables
3️ Solutions
1. Enable TRIM
o Helps OS manage garbage collection and maintain speed
2. Update Firmware
o Fix bugs and optimize performance
3. Leave Free Space (~20–25%)
o Avoid overfilling SSD
4. Over-provisioning
o Allocate spare space via manufacturer utility to improve wear leveling
5. Defragmentation / Optimize
o For older SSDs / Windows versions: use “Optimize Drives” (not traditional
defrag for modern SSDs)
6. Replace Failing SSD
o Health below ~70% or TBW exceeded → replacement recommended
7. Check Power Settings
o Disable aggressive low-power states
8. Reduce Background I/O
o Limit antivirus scanning or heavy write operations
9. Improve Cooling
o Install heatsink or ensure airflow for NVMe SSDs
10. Secure Connection
o Replace faulty SATA/NVMe cable or try another port
5️ Preventive Measures
Keep SSD ≤ 75–80% full
Enable TRIM and OS optimization
Update firmware and drivers
Avoid unnecessary heavy writes
Monitor temperature regularly
Backup data periodically
Use quality SATA/NVMe ports and cables
Exam Tip
SSD speed degradation is normal over time due to NAND wear, but enabling TRIM,
leaving free space, and updating firmware can significantly extend performance and
lifespan.
42. Problem: OS Freeze During Update
(The operating system becomes unresponsive while installing updates. Screen may freeze, cursor
may not move, and the system appears “stuck” for an extended time.)
1️ Possible Causes
1. Corrupted update files – incomplete or damaged download.
2. Insufficient disk space – OS cannot extract or install update.
3. Conflicting software – antivirus, firewalls, or system utilities block update process.
4. Outdated or incompatible drivers – graphics, storage, or chipset drivers interfering
with update.
5. Background processes consuming resources – heavy CPU/RAM usage slows update.
6. Faulty hardware – RAM, storage device, or motherboard issues.
7. Power loss during update – interrupts installation, leaving OS in inconsistent state.
8. Slow or unstable internet connection – network-dependent updates fail mid-process.
9. Pending previous updates – conflicts with unfinished update cycles.
10. Malware infection – blocks update or interferes with system files.
11. Operating system corruption – damaged system files prevent update.
12. Third-party system optimizers – registry cleaners or disk optimizers interfere.
13. Overheating – thermal throttling may freeze the update process.
14. Update service failure – Windows Update or similar services malfunction.
15. Insufficient privileges – updates require administrator permissions.
2️ Diagnostic Steps
1. Observe Symptoms
o Frozen spinning circle, unresponsive cursor, no progress for >30–60 minutes.
2. Check Disk Space
o Ensure enough free space (Windows: ≥20% recommended).
3. Reboot in Safe Mode
o Confirms if freeze is caused by drivers or third-party software.
4. Run System File Checker (SFC)
o sfc /scannow to detect and repair corrupted system files.
5. Check Update History
o Identify failed updates.
6. Monitor Resource Usage
o Task Manager → CPU, Memory, Disk I/O during update.
7. Check Hardware Health
o Run memory diagnostic, SMART check for storage, CPU/GPU temperature
monitoring.
8. Check Event Viewer
o Application and System logs for error codes related to update.
9. Disconnect Non-Essential Devices
o External drives, printers, or USB peripherals that may conflict.
10. Network Stability Test
o Ensure uninterrupted download for network-dependent updates.
3️ Solutions
1. Restart Update in Safe Mode
o Use minimal drivers to avoid conflicts.
2. Free Up Disk Space
o Delete temporary files and unused applications.
3. Repair System Files
o Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth
(Windows)
4. Disable Conflicting Software
o Temporarily turn off antivirus, firewalls, or system optimizers.
5. Update Drivers
o Install latest graphics, storage, and chipset drivers.
6. Check for Hardware Issues
o Replace defective RAM, storage, or overheating components.
7. Retry Update
o Use Windows Update Troubleshooter or manually download update package.
8. Perform System Restore
o Revert to previous stable state if update failed.
9. Install Updates Incrementally
o Apply smaller updates individually instead of cumulative bulk update.
10. Clean Install (Last Resort)
o If repeated freezes occur, backup data and reinstall OS.
5️ Preventive Measures
Keep OS and drivers regularly updated
Backup data before major updates
Ensure sufficient free disk space
Disable unnecessary background applications
Use a UPS to prevent power loss during updates
Monitor system temperature during updates
Exam Tip
If OS freezes during an update but works in Safe Mode, the issue is usually driver or
software conflict—not hardware. Always check logs and free disk space before attempting
a forced restart.
1️ Possible Causes
1. Phishing emails – malicious attachments or links.
2. Malicious downloads – pirated software, cracked applications, or unsafe websites.
3. Infected removable media – USB drives, external HDD, or memory cards.
4. Unpatched operating system or software – security vulnerabilities exploited by
malware.
5. Weak or reused passwords – allow remote access via malware.
6. Outdated antivirus or firewall – inadequate protection against new threats.
7. Drive-by attacks – visiting compromised websites that exploit browser vulnerabilities.
8. Trojan horse programs – hidden malware disguised as legitimate applications.
9. Social engineering – tricking users into executing malicious files.
10. Peer-to-peer networks – file-sharing applications spreading malware.
11. Ransomware exploit kits – encrypt files demanding ransom.
12. Macro-enabled documents – infected Office files with macros.
13. Compromised IoT devices – malware spreading to PC via network.
14. Browser extensions – malicious extensions injecting malware.
15. Removable media autorun – malware exploiting autorun features.
2️ Diagnostic Steps
1. Observe Symptoms
o Slow system performance, frequent crashes, unexpected pop-ups, unauthorized
file changes, encrypted files with ransom notes.
2. Run Antivirus / Anti-Malware Scan
o Use trusted software: Malwarebytes, Windows Defender, Kaspersky, Bitdefender.
3. Check Task Manager / Resource Monitor
o Identify unusual CPU, memory, or network usage by unknown processes.
4. Inspect Startup Programs
o Check msconfig or Task Manager for unknown auto-start entries.
5. Check Browser Behavior
o Look for redirects, new toolbars, or suspicious extensions.
6. Check System Logs
o Event Viewer → Security logs for unauthorized logins or actions.
7. Examine Network Activity
o Unexpected outbound connections may indicate malware communication.
8. Verify File Integrity
o Missing, encrypted, or renamed files can indicate ransomware.
9. Isolate the System
o Disconnect from network to prevent malware spread.
10. Use Bootable Rescue Disk
o Scan system without booting infected OS.
3️ Solutions
1. Disconnect from Network
o Prevent lateral movement or data exfiltration.
2. Quarantine / Remove Malware
o Use antivirus or specialized removal tools.
3. Restore from Backup
o Only if clean backup is available (critical for ransomware).
4. Use Decryption Tools
o Some ransomware variants have public decryptors.
5. Clean Install OS (Last Resort)
o When malware cannot be removed, backup data and reinstall OS.
6. Update OS and Software
o Patch vulnerabilities exploited by malware.
7. Change All Passwords
o After malware removal, especially online accounts.
8. Enable Real-Time Protection
o Keep antivirus and firewall active.
9. Educate Users
o Avoid phishing emails, unsafe downloads, and suspicious links.
10. Monitor System Post-Infection
o Watch for residual or re-infection signs.
5️ Preventive Measures
Keep OS, applications, and antivirus updated
Regularly backup important files (offline or cloud)
Avoid opening suspicious emails or attachments
Do not download software from untrusted sources
Use strong, unique passwords
Enable firewalls and real-time protection
Limit user privileges (avoid admin rights for daily tasks)
Educate users about phishing and social engineering
Exam Tip
Ransomware encrypts files and demands payment; immediate network isolation and
restoring from clean backup are the safest responses. Antivirus alone may not recover
encrypted files.
1️ Possible Causes
1. Disk Failure – one or more member drives have failed (common in RAID 0, 5, 6, 10).
2. Controller Failure – RAID controller card or onboard controller malfunctions.
3. Configuration Corruption – corrupted RAID metadata or settings.
4. Power Loss / Surge – sudden power events damage drives or controller.
5. Loose or Damaged Cables – SATA/SAS cables disconnected or damaged.
6. Firmware / Driver Issues – outdated RAID controller firmware or OS drivers.
7. Human Error – accidental deletion, reinitialization, or improper rebuild.
8. Mismatched Drives – different sizes, speeds, or firmware versions.
9. Overheating – drives or controller overheating leads to failure.
10. Bad Sectors on Drives – logical or physical damage causing array degradation.
11. OS / Software Failure – corruption in RAID management software.
12. Battery Backup Unit (BBU) Failure – for RAID controllers with cache.
13. Rebuild Interruptions – powering off or rebooting during rebuild.
14. Virus / Malware – ransomware or malware corrupting RAID data.
15. Exceeding RAID Redundancy Limit – too many drives fail beyond parity or mirroring.
2️ Diagnostic Steps
1. Check RAID Controller Status
o Enter BIOS / UEFI RAID utility
o Look for degraded, offline, or failed status
2. Inspect Drive LEDs
o Many RAID-enabled drives have failure indicators
3. Check System Logs
o OS event logs or RAID controller logs for drive/controller errors
4. Test Individual Drives
o Remove and test with disk diagnostic tools (manufacturer utilities)
5. Check Cables and Connections
o SATA/SAS cables, power connectors, and backplane integrity
6. Verify Firmware / Driver Versions
o Ensure RAID controller and drive firmware are up to date
7. Monitor Temperatures
o Check for overheating of drives or controller
8. Backup Data Immediately
o If array is degraded but functional
9. Assess RAID Level
o Understand tolerable drive failures (e.g., RAID 5 tolerates 1 drive)
10. Check Rebuild Progress
o If a rebuild was in progress, verify it completed successfully
3️ Solutions
1. Replace Failed Drives
o Swap failed drive(s) with compatible replacements
2. Rebuild RAID
o Use RAID controller to rebuild array after drive replacement
3. Repair RAID Configuration
o Restore configuration from controller metadata if corrupted
4. Update Firmware / Drivers
o Fix controller or drive compatibility issues
5. Check and Replace Cables
o Replace damaged SATA/SAS or power cables
6. Restore from Backup
o If array cannot be rebuilt, restore data from backup
7. Controller Replacement
o Required if RAID controller has failed
8. Use Professional Data Recovery
o For complex or multiple-drive failures
9. Preventive Measures
o Monitor RAID health regularly
o Enable alerts for drive failures
o Keep redundant backups
o Use UPS to prevent power loss
5️ Preventive Measures
Monitor RAID health with software alerts
Replace drives proactively based on SMART data
Keep RAID controller and drive firmware updated
Use UPS to prevent sudden power loss
Keep regular external backups
Avoid mixing different drive models or sizes in RAID
Schedule maintenance and rebuild during low-load periods
Exam Tip
RAID failure does not always mean data loss. Immediate diagnosis, replacing failed drives,
and proper rebuild procedures can often restore the array without losing data. Always
maintain external backups
1️ Possible Causes
1. RAM Failure or Improper Installation – loose, defective, or incompatible memory
modules.
2. CPU Fault or Improper Seating – CPU not installed correctly or damaged.
3. Video / GPU Error – graphics card missing, loose, or defective.
4. Motherboard Fault – capacitors, chipset, or circuitry failure.
5. Keyboard / Input Device Error – missing or stuck keys.
6. Power Supply Issue – insufficient or unstable voltage.
7. CMOS / BIOS Corruption – incorrect settings or failed firmware.
8. Peripheral Malfunction – drives, expansion cards, or external devices causing POST
errors.
9. Cooling / Thermal Fault – CPU overheating or fan not detected.
10. BIOS Misconfiguration – overclocked or unsupported settings.
11. RAM Slot Fault – defective motherboard slot.
12. GPU Memory Fault – VRAM errors.
13. Battery / CMOS Battery Low – affects POST diagnostics.
14. Short Circuit / Loose Screws – grounding issues on motherboard.
15. External Hardware Interference – USB devices causing POST failure.
2️ Diagnostic Steps
1. Observe Beep Pattern
o Short or long beeps, repeated sequences, or combinations (consult motherboard
manual).
2. Check Motherboard Manual
o Beep codes differ by BIOS manufacturer: AMI, Award, Phoenix, or UEFI.
3. Test Minimal Configuration
o CPU, one RAM stick, GPU (if no onboard video), keyboard.
4. Reseat Components
o Remove and reinstall RAM, GPU, and CPU if necessary.
5. Check Power Supply
o Test voltage outputs using multimeter.
6. Check CMOS Battery
o Replace if voltage low (<3V for CR2032).
7. Test RAM Modules Individually
o Insert one stick at a time in different slots.
8. Check GPU
o Test with a known working card.
9. Remove Peripherals
o Disconnect drives, USB devices, and expansion cards.
10. Observe POST LEDs (if available)
o Many modern motherboards have debug LEDs indicating CPU, DRAM, VGA,
and BOOT issues.
Note: Always check your motherboard manual, as beep codes vary by BIOS version.
4️ Solutions
1. RAM Fault
o Reseat, test individual modules, replace defective sticks.
2. CPU Fault
o Reseat, check compatibility, replace if damaged.
3. GPU Fault
o Reseat card, clean contacts, replace if defective.
4. Motherboard Fault
o Inspect for bulging capacitors, burnt components; replace motherboard if
necessary.
5. Keyboard / Input Error
o Reconnect keyboard, test with another keyboard.
6. Power Supply Issue
o Test PSU or replace with known good unit.
7. CMOS / BIOS Issue
o Reset CMOS, update BIOS, or replace battery.
8. Peripheral / Short Circuit
o Disconnect all external devices, test system individually.
5️ Preventive Measures
Handle RAM, CPU, and GPU with care; use ESD precautions.
Keep BIOS updated and use correct version for motherboard.
Ensure proper cooling and fan operation.
Avoid loose screws or metal objects near motherboard.
Test new hardware incrementally before adding all components.
Maintain documentation of beep codes for reference.
Exam Tip
Beep codes are the motherboard’s primary diagnostic tool before POST displays output.
Short and long beeps indicate specific hardware failures, allowing targeted troubleshooting
without powering on the OS.
Always check the basics first: Ensure the system is powered on and cables are properly
connected.
Check PSU functionality: Use a multimeter to verify output voltages (3.3V, 5V, 12V).
Inspect external power sources: Confirm wall outlets, surge protectors, and adapters are
working.
Check peripheral connections: Loose keyboard, mouse, monitor, or network cables
often cause issues.
Listen and watch: Beeps, clicking sounds, fan noises, blinking LEDs, and error codes
provide crucial clues.
Record symptoms: Note what happens, when it happens, and under what conditions
(e.g., during startup, heavy load).
Look for patterns: Problems that happen consistently are easier to diagnose than
intermittent ones.
Hardware Diagnostics:
Software Diagnostics:
Temperature & voltage monitoring: Prevents overheating and power instability issues.
Disk health checks: Detect early signs of HDD/SSD failure.
Event logs: Catch recurring errors before they escalate.
Regular antivirus scans: Prevent malware from causing instability.
Manuals and official troubleshooting guides provide error codes, beep codes, and
BIOS recovery steps.
Forums and support communities can offer solutions for rare or complex problems.
Training and certifications (e.g., CompTIA A+, Microsoft, Cisco) improve diagnostic
skills.
ESD protection: Anti-static wrist straps, mats, and safe handling prevent hardware
damage.
Power safety: Always unplug before opening a system; discharge capacitors.
Tool organization: Keep screwdrivers, compressed air, and thermal paste ready to
reduce mistakes.
Exam Tip
During Maintenance:
☐ Clean components
☐ Inspect hardware
☐ Replace faulty parts
After Maintenance:
☐ Boot test
☐ Temperature test
☐ Stability test
☐ Install updates
Hardware overheating can lead to thermal throttling, where CPU/GPU components automatically reduce performance to prevent damage from excessive heat, significantly impacting system performance . To prevent this, ensure proper cooling by cleaning CPU/GPU heatsinks and fans, reapplying thermal paste, and improving airflow within the case or upgrading the cooling system for high-performance components . Monitoring temperatures using tools like HWMonitor can help detect overheating early and maintain performance stability .
Resetting BIOS/UEFI settings influences diagnostics by reverting all settings to their default configurations, eliminating any misconfigurations that might prevent hardware components from functioning correctly . This step is necessary when diagnosing issues related to incorrect hardware settings, conflicting configurations such as wrong overclock settings, boot errors, or when new hardware is incompatible with existing settings . By clearing potentially faulty custom settings, the system can attempt to achieve a basic functional state, aiding further hardware diagnostics.
Inspecting the motherboard for damage or short circuits is crucial because physical damage, such as burnt marks, bulging/leaking capacitors, or visible short circuits, can cause systemic failures that affect the entire computer . These signs can indicate faulty voltage regulation or component failure, leading to unresponsive systems, display issues, or even hardware damage across connected components . Identifying these issues early allows for targeted repairs, such as replacing the motherboard or specific components, to prevent further damage.
VRM checks on the motherboard are crucial for resolving power-related issues because VRMs regulate the voltage to the CPU and other critical components, ensuring stable operation . If VRMs fail or provide unstable voltages, it can result in system instability, unexpected shutdowns, or damage to sensitive components. To perform a VRM check, visually inspect for bulging or leaking capacitors, burned spots, and use monitoring software to check VRM temperature for irregularities . Replacing faulty VRMs or capacitors can stabilize power delivery and resolve associated issues.
Excessive malware can severely degrade a computer's performance by consuming critical system resources such as CPU, memory, and disk space, leading to slow performance or instability . To address this, perform a full system scan using trusted antivirus tools, quarantine or delete infected files, and consistently clean temporary files using built-in tools like Disk Cleanup or third-party utilities . Regularly updating antivirus definitions and scanning the system helps prevent future infections and maintains optimal performance.
A clean boot is significant for resolving software-related stability issues because it allows the system to start with a minimal set of drivers and startup programs, isolating software conflicts that may cause instability . To perform a clean boot, disable all startup programs and non-essential services using System Configuration (msconfig), then restart the system and observe if the issue persists . This process helps identify if third-party applications or services are causing the problem, guiding further troubleshooting steps.
Performing a POST using beep codes aids diagnostics by providing audible signals that identify hardware issues preventing a complete boot. Each beep code pattern correlates with specific hardware problems such as RAM, CPU, or video card failures . For instance, a series of short beeps might indicate a RAM issue, prompting reseating or replacement, while different patterns can indicate GPU or CPU problems. These outcomes direct technicians toward the faulty component, allowing precise remediation without the need for additional testing equipment, streamlining the troubleshooting process .
Hard drive mechanical failure sounds, such as clicking or grinding, indicate potential issues like damaged read/write heads or internal platter problems, posing a risk of data loss . Upon hearing these sounds, immediate actions include backing up critical data to prevent data loss, testing the drive on another system to confirm the fault, and running diagnostic scans like CHKDSK to check for bad sectors . If the issues persist, replacing the drive is advisable to prevent complete failure and data loss.
To diagnose a monitor displaying no image, follow these steps: 1) Check the monitor and cable, ensuring the monitor is powered and testing it with another system can confirm if the monitor or cable is faulty . 2) Verify the input source on the monitor, ensuring it matches the connected port like HDMI or DisplayPort . 3) Reseat and test RAM and GPU, as improperly seated RAM or a GPU can prevent the system from sending a signal to the monitor. Testing with integrated graphics can isolate a GPU problem . These steps help determine if the issue lies with the monitor itself, the cable, or internal components like RAM or GPU.
It is advisable to replace the PSU when diagnosing hardware issues if it fails voltage tests, does not power on, or cannot supply sufficient power to the system components, especially high-power devices like GPUs . Confirmation of PSU failure can be obtained by performing voltage checks using a multimeter to ensure each rail outputs correct voltages, or by conducting a "paperclip test" to verify PSU power-on functionality . A PSU replacement resolves power instability problems that frequently cause random shutdowns or hardware underperformance.