Troubleshooting (All) Flashcards
Hardware: Unexpected Shutdowns
Could be caused by overclocking, buggy applications, overheating, power outage/surge.
If overclocking, clear CMOS jumper.
Hardware: System Lockups
System lockups & page faults can indicate bad RAM.
Run Windows Memory Diagnostic.
Could be cause by overclocking (clear CMOS jumper).
Hardware: POST Code Beeps
Beep codes vary per manufacturer (check mobo manual).
Example (Don’t need to memorize):
Bad/missing video (long, short, short)
Bad/missing RAM (single beep repeated)
CPU alarm/heat limit (series of short beeps)
Hardware: Blank Screen on Bootup
Make sure everything is plugged in and turned on.
If within 30 days of purchase, could be burn-in failure.
One of components may be fried/damaged.
(Mobo, CPU, RAM)
Incorrect RAM module/seating
Hardware: BIOS Time/Settings Resets
Indication that CMOS battery is dying.
Replace! (CR2032)
Hardware: Attempts to boot to incorrect device
Open BIOS/UEFI system setup utility.
Go to boot order and switch primary boot device/boot order.
Hardware: Continuous Reboots
RAM problem: run Windows Memory Diagnostic.
Could also be a symptom of overheating.
Hardware: No Power
Make sure all power connectors are correctly plugged in.
PSU: Check power switch is on. Check proper voltage setting. Could be bad PSU/power button/inverter
Faulty outlet, bad power cable.
Disconnect third-party hardware.
Bad motherboard or bad components
(CPU, GPU, RAM, Sound card, Hard drive, optical drive)
Hardware: Overheating
Too much thermal paste on CPU.
Not enough thermal paste on CPU.
Failure to connect fan power/CPU fan.
Other: Too much dust or animal hair. (Use compressed air)
Lack of air conditioning in location.
Hardware: Loud Noise
Blown motherboard capacitor.
Blown PSU fuse.
Search for burnt smell in case.
Hardware: Intermittent Device Failure
Indication of dying PSU > Replace (likely)
Indication of bad RAM > Replace
Others: Buggy applications, buggy hardware, electrical interference
Hardware: Fans spin, no power to other devices
Disconnect external hardware.
Reseat RAM
Bad motherboard capacitors (check for yellow/amber light)
Change power outlet
Potentially bad PSU
Check/remove peripherals (they can cause this too)
Hardware: Indicator Lights
Yellow/amber light on motherboard: bad motherboard
No indicator light: bad PSU or motherboard
Hardware: Smoke
Turn off & unplug everything immediately.
Use Class C fire extinguisher if necessary.
Look for burning smell to identify source.
Hardware: Burning Smell
Could be fried CPU
Could be bad PSU (blown fuse)
Could be blown motherboard capacitor
Look for smell to identify the component.
Hardware: Proprietary Crash Screens
NMI (Non-maskable interrupt) - CPU can’t ignore
Search for burnt smell in case
Could be bad RAM (run windows memory diagnostic)
Could be fried CPU (short circuit)
Damaged motherboard
Faulty component.
Buggy driver, application, or OS corruption.
PSU problems
Hardware: Distended Capacitors
Poorly manufactured capacitors (bulging capacitors)
Usually occurs within first 30 days of use
AKA: Burn-in failure (motherboard)
ESD shock to system
Must replace motherboard
Hardware: Log Entries & Error Messages
POST error message (potentially bad RAM)
- Could be faulty SPD chip
Hexadecimal digit error: page fault
Write down the address
Not necessarily RAM problem, but memory error
POST text errors: should indicate specific issue
Storage: Read/Write Failure
Indication of dying hard drive.
Back up data immediately (if possible)
Must replace hard drive
Storage: Slow Performance
Failure of drive in RAID array
Storage: Loud Clicking Noise
Drive is about to die.
Other indications:
Continuous high-pitched squeal
Continuous grinding/rumbling
Storage: Failure to boot
Double check boot order in system setup
Could indicate dying/dead drive.
You may get read/write failures, drive noise, or drives disappear.
Storage: Drive not recognized
Make sure drives are powered & have proper connections.
Make sure drives are properly formatted/partitioned.
Storage: OS Not Found
Indication of failed drive in RAID array (especially RAID 0)
Could be corrupted hard drive data.
Run error checking utility.