Chip-Level Repair Guide
Interactive version: open the Chip-Level Repair Lab for photo diagnosis, animated blueprint boards, multimeter probing, power-up sequences and fault simulations.
HDD · SATA SSD · NVMe · laptop and desktop motherboards · CPU/GPU/BGA. Diagrams, multimeter checks, and component-by-component explanation.
1. Read this first
Every brand and model uses different part numbers and layouts, but they are all built from the same few circuits: input protection → power converters → controller → memory/data. If you learn how to test those circuits with a multimeter, you can repair any model. For a specific model you then add its schematic and boardview (see section 14) to find exact part locations and expected values.
What chip-level repair can and cannot fix
✔ Can fix: shorted capacitors, TVS diodes, fuses, MOSFETs, power ICs, charger ICs, PWM controllers, corrupted BIOS, broken connectors, bad solder joints, damaged ports, and some liquid damage.
✘ Cannot fix with a soldering station: a dead CPU die, a dead GPU die, worn-out NAND flash, or crashed HDD heads and scratched platters. Those need a replacement chip (BGA swap), a donor head stack in a clean room, or professional data recovery tools such as PC-3000.
Customer data rule: if the customer needs their data, do not experiment. A wrong board swap on an HDD, or a firmware reflash on an SSD, can destroy data permanently. Diagnose first, then decide.
The universal repair loop (use it on every device)
- Inspect visually under a microscope or magnifier: burnt parts, cracked caps, corrosion, missing parts, lifted pins, previous repair attempts.
- Check for shorts with the power off: measure resistance and diode value from each main rail to ground (section 3).
- Power on with current limiting (bench PSU or USB/DC meter) and watch the current draw.
- Measure voltages in order of the power sequence. The first missing rail or signal is where the fault is.
- Look at that circuit: its input, its enable, its output, and its feedback/power-good signal.
- Replace the faulty part, then re-measure before reconnecting expensive parts (CPU, SSD, screen).
2. Tools & bench setup
| Tool | Why you need it | Minimum spec |
|---|---|---|
| Digital multimeter | Voltage, resistance, diode mode, continuity | Auto/manual range, fast continuity beep, diode mode showing 0.000–2.000 V. Fluke, UNI-T UT61E, Aneng, Brymen all work. |
| DC bench power supply | Powering boards safely with a current limit, and voltage injection to find shorts | 0–30 V, 0–5 A (or 10 A), with a 3-digit current display |
| USB-C / DC current meter | Watching the current draw while the laptop powers on | USB-C PD trigger meter (for example 0–20 V, 5 A) |
| Hot air station | Removing and installing SMD parts and ICs | Adjustable 100–480 °C with airflow control |
| Soldering iron | Small parts, wires, pads | Temperature controlled (T12 / JBC-style tips), fine conical and knife tips |
| Preheater | Large boards, BGA work, stopping the board from warping | Bottom heater, 100–250 °C |
| Microscope | Seeing 0201/0402 parts, cracks, and corrosion | Stereo microscope 7–45× or a good HDMI digital scope |
| Thermal camera / freeze spray / rosin | Finding the part that heats up on a shorted rail | Any of the three works; a thermal camera is fastest |
| SPI programmer | Reading/writing BIOS chips | CH341A (with a 1.8 V adapter and 3.3 V mod), or RT809F/H, or T48 (TL866-3G) |
| Consumables | — | Flux (gel type, e.g. Amtech-style), leaded solder 63/37, low-melt solder, solder wick, IPA 99%, Kapton tape, ultrasonic cleaner |
| Data tools (HDD/SSD) | Reading ROMs and doing firmware work | SPI programmer (for 8-pin ROMs); PC-3000 / MRT / DFL for serious data recovery |
Safety: always disconnect the battery (laptop) before working. Use an ESD mat and strap. Lithium batteries can catch fire if punctured or shorted. Never heat near a battery. Desktop PSU and adapter primary sides hold dangerous voltages (300+ V DC) on the big capacitor even after unplugging.
3. Multimeter: the full method
3.1 The four modes you will use
| Mode | Board powered? | What it tells you |
|---|---|---|
| DC voltage (V⎓) | ON | Is the rail present, and is it the correct value? Is the enable signal high? |
| Diode mode (→|) | OFF | The “signature” of a rail or pin compared to ground. Best tool for finding shorts and damaged ICs, and for comparing with a good board. |
| Resistance (Ω) | OFF | Exact value of a short (0.5 Ω vs 30 Ω), checking resistors, fuses, coils, motor windings. |
| Continuity (beep) | OFF | Quick check of fuses, traces, and connector pins. Beeps below about 30–50 Ω, so a beep alone does not prove a dead short. |
3.2 Diode-to-ground measurement (the most important technique)
Board repair technicians measure every point with the probes reversed: red probe on ground, black probe on the test point. You are measuring through the protection diodes inside the ICs connected to that point, so every rail and signal gives a repeatable number.
| Diode reading (red on GND) | Meaning |
|---|---|
| 0.000 – 0.010 + beep | SHORT Dead short to ground. Measure resistance next. |
| 0.010 – 0.100 | Very low. Normal only for CPU/GPU core rails (VCCIN, VCORE, NVVDD) — typically 0.005–0.150 depending on the platform. On any other rail this means a short or a damaged IC. |
| 0.100 – 0.350 | Normal for low-voltage, high-current rails: RAM VDDQ (1.1–1.35 V), PCH core 1.0–1.05 V, SSD core rails. |
| 0.350 – 0.800 | Normal for 3.3 V / 5 V rails, data lines, and signals. Most I/O pins read 0.4–0.7. |
| 0.800 – 1.5+ | Normal for the input rails behind MOSFETs (adapter input, B+/VIN) and some isolated signals. |
| OL (open) | Open circuit. Normal on some points (pads behind an open MOSFET), but a missing connection on a rail that should read a value: blown fuse, broken trace, missing resistor. |
The golden rule: there is no single “correct” number. Compare with (a) the same point on a known-good board of the same model, (b) a boardview that includes diode values, or (c) the other side of a symmetrical circuit (e.g. USB port 1 vs port 2, RAM slot A vs slot B).
3.3 Resistance to ground
Use it after diode mode shows something low. Let the reading settle (big capacitors charge up slowly).
| Reading | On a normal rail | On a CPU/GPU core rail |
|---|---|---|
| 0.0 – 0.5 Ω | Hard short: shorted cap, MOSFET or IC | Likely shorted (but compare — some platforms read ~1 Ω) |
| 1 – 10 Ω | Suspicious — partial short or leaky IC | Often normal (Intel VCCIN, NVIDIA NVVDD typically 1–5 Ω) |
| 10 – 100 Ω | Normal for low-voltage rails | Normal |
| 100 Ω – several kΩ (rising) | Normal for 3.3 V / 5 V / 19 V rails — reading climbs as caps charge | — |
Tip: swap the probes. If a reading is low both ways, it is a real short (resistive). If it is very different, you are measuring through a diode junction (IC or MOSFET body diode).
3.4 Voltage measurement tips
- Black probe on ground, red on the test point. Use the output side of an inductor (the side with the big caps) to measure a buck converter output.
- Measure the input, the enable (EN), the output, and power-good (PG) of every regulator. That is enough to judge any power IC.
- A rail that reads slightly low and drops further = load short or weak regulator. A rail that reads the input voltage = shorted high-side MOSFET — disconnect immediately, it will kill everything downstream.
- Pulsing voltage (e.g. 19 V on a 3.3 V rail’s input jumping up and down) = regulator in hiccup mode because of a short on its output.
4. How to test every component
4.1 Passive components
| Part | Board marking | How to test | Typical failure |
|---|---|---|---|
| Resistor | R, RN (network) | Ω mode. In-circuit reading must be ≤ its marked value (parallel paths can lower it, never raise it). Higher than marked = open/damaged. 0 Ω resistors act as jumpers — must beep. | Open (burnt), corroded |
| Ceramic capacitor (MLCC) | C, PC (power cap) | Diode/Ω to ground. Should NOT read 0 Ω. Cannot measure the capacitance in-circuit; a short is the main failure. | Shorts internally — the #1 cause of dead rails |
| Tantalum / polymer cap | PC, CE (black/yellow blocks) | Same as MLCC. Polarized: the bar marks + on tantalum. | Shorts, sometimes burns |
| Electrolytic cap | C, EC | Look for bulging/leaking. ESR meter out of circuit. | Dries out (older desktop boards) |
| Inductor / coil | L, PL, PR | Continuity: almost 0 Ω end to end. Open = broken. | Rarely; cracked by drops |
| Fuse | F, PF | Continuity: must read ~0 Ω. OL = blown — find what blew it before replacing. | Blown by downstream short |
| Ferrite bead | FB, L | Like a fuse: ~0 Ω end to end. | Open from overcurrent |
| Crystal oscillator | X, Y (32.768 kHz, 24/25/27/40 MHz) | No good multimeter test. Measure voltage on its pins while powered (about half of the IC supply, e.g. 0.3–1.0 V) — 0 V on both pins means not oscillating. Best: oscilloscope, or replace. | Cracked by drops |
4.2 Diodes
| Type | Test (diode mode, normal polarity: red = anode) | Failure |
|---|---|---|
| Rectifier / Schottky | Forward (red on anode, black on cathode/bar): 0.15–0.7 V. Reverse: OL. | Short both ways, or open both ways |
| TVS / Zener (protection) | Same as above. A shorted TVS reads ~0 both ways and pulls the rail to ground. Common on HDD/SSD 5 V / 12 V input and on USB/charging inputs. | Short after overvoltage (wrong adapter, reversed PSU cable) |
| LED | Diode mode forward 1.6–2.8 V; many meters light it dimly. | Open |
4.3 MOSFETs (the most-replaced active part)
- In-circuit quick test: measure D–S and G–S in Ω mode. D–S near 0 Ω both ways (and the rail is not a core rail) = shorted MOSFET. G–S near 0 Ω = damaged gate.
- Powered test: N-channel switch: gate must be higher than source (by 5 V+ for load switches, or gate = source + ~5–10 V on input MOSFETs driven by the charger IC). P-channel switch (often on 3.3 V/5 V load switches): gate LOW = ON, gate = source = OFF.
- Common laptop MOSFETs: AON7xxx, AO4xxx, SiRA/SiS series, FDMC/FDMS, NTMFS, IRF, plus dual N-channel “power stages” in VRMs (e.g. DrMOS / smart power stages).
4.4 ICs (power ICs, controllers)
- You cannot “test” an IC with a meter directly. You test its pins: power in, enable, output, power-good, and the diode value of each pin vs a good board.
- A pin reading 0.000 when it should read 0.4–0.7 = that IC (or something on that line) is damaged.
- An IC that gets hot with nothing on its output = internally shorted.
- Read the marking, search “marking code + package” (e.g. small chips print a 2–4 letter code instead of the part number) to get the datasheet and pinout.
5. Circuits you will meet on every board
5.1 Buck converter (step-down regulator) — on every HDD, SSD and motherboard
| Symptom | Cause | Check |
|---|---|---|
| VOUT = 0 V, VIN present | No EN signal, shorted output, or dead controller | Measure EN (should be >1 V / high). Check output diode/Ω to ground. |
| VOUT = VIN | Shorted high-side MOSFET | D–S ~0 Ω. Replace it AND check every chip on the output rail — they were overvolted. |
| VIN shorted to ground | Shorted input cap or shorted high-side + low-side | Lift the inductor/MOSFETs to isolate; or inject voltage (section 6). |
| VOUT low, pulsing | Overcurrent protection (hiccup) — load short | Measure output resistance; find hot part. |
| VOUT wrong value | Wrong/drifted feedback resistor | Compare FB resistors with schematic. |
5.2 LDO (linear regulator)
Small 3–5 pin chips (e.g. 1.8 V, 2.5 V, 1.2 V from 3.3 V). Pins: IN, OUT, GND, EN, sometimes PG/ADJ. Output missing with IN and EN present → replace LDO (if the output is not shorted). Gets hot = output shorted or IC shorted.
5.3 Load switch
A MOSFET or small IC that connects an always-on rail to a device only when needed (e.g. +3VS → +LCDVDD, +5V → USB port). Check: input present? enable present? output missing → switch bad, or output short has triggered its protection.
5.4 Rail naming you will see on schematics
| Suffix / name | Means |
|---|---|
| G3H, RTC, VCCRTC | Always on, even with no adapter (coin cell / battery) |
| ALW, A, AON, _S5, DSW | Always-on when adapter or battery connected (standby rails) |
| _S3, SUS, M | On in sleep (RAM stays powered) |
| _S0, S, RUN, VS (e.g. +3VS, +5VS) | On only when the laptop is running |
| B+, VIN, PPBUS, PWR_SRC, DCIN | Main system input rail (adapter/battery voltage, 7–20 V) |
| VCCIN, VCORE, VCC_CORE, VDDCR_CPU | CPU core power |
| VDDQ, +1.2V_DDR, +1.1V_VDDQ, +1.35V | RAM power (DDR4 1.2 V, DDR5/LPDDR5 1.1 V / 1.05 V, DDR3L 1.35 V) |
| VTT, +0.6V_DDR_VTT | RAM termination = half of VDDQ |
6. Finding shorts and dead rails
A rail that measures ~0 Ω to ground has hundreds of parts on it. These methods find the one bad part.
6.1 Voltage injection (best method)
- Remove battery, adapter, CPU (if socketed), RAM, SSD. Nothing expensive should be connected.
- Set PSU voltage to no more than the rail’s normal voltage. For CPU/GPU core rails and anything ≤1.8 V, start at 1.0 V. Never inject 19 V into a 1 V rail.
- Set current limit to 1 A; raise slowly to 3–5 A if nothing heats up (core rails may need 5–10 A).
- Connect red to the rail (a cap or inductor on it), black to ground.
- Watch the thermal camera / freeze spray. Remove the hot part and re-measure the rail.
If the CPU/GPU itself gets hot on its core rail, the processor die is shorted (see section 12). If the voltage climbs to the set value with almost no current, the short was cleared or it was not a real short.
6.2 Other methods
- Isolation: lift inductors, 0 Ω resistors, or MOSFETs that split the rail into sections. The section that stays shorted contains the fault.
- Milliohm / voltage-drop method: with current injected, measure millivolts along the rail with the meter; the voltage drops toward the short.
- Remove caps one by one (last resort): replace with new ones after.
7. HDD repair (3.5″ and 2.5″, all brands)
7.1 HDD PCB block diagram
7.2 Identify the fault by symptom
| Symptom | Most likely | Bench repairable? |
|---|---|---|
| Completely dead, no spin, no sound; PSU may shut off | Shorted TVS diode (5 V or 12 V), blown fuse, burnt motor driver (wrong PSU cable / surge) | ✔ Yes — PCB repair |
| Burning smell, burnt chip visible | Motor driver IC burnt | ✔ Replace driver or donor PCB + ROM transfer |
| Spins up, then clicks repeatedly | Bad heads, or wrong/missing ROM on a swapped PCB | ✘ Heads = clean room. Check ROM first if PCB was swapped. |
| Tries to spin, buzzes/beeps, does not spin | Stuck heads on platter (stiction) or seized motor | ✘ Clean room |
| Spins normally, not detected / wrong name / 0 GB | Firmware (service area) corruption, or ROM mismatch | Firmware tools (PC-3000, MRT); sometimes ROM issue |
| Detected, very slow, freezes, bad sectors | Weak/degrading heads, media damage | ✘ Clone immediately with ddrescue/imaging tool |
| Spins up and down repeatedly | Head/preamp problem or firmware | Usually ✘ |
7.3 Multimeter checks on an HDD PCB (power OFF)
- 5 V input to ground: measure on the SATA power connector 5 V pins (or on the TVS). Normal: tens/hundreds of Ω rising, diode ~0.4–0.6. 0–2 Ω = short.
- 12 V input to ground (3.5″ drives). Same check.
- Find the TVS diodes near the power connector (SMA/SMB package, 2 pins, marked with a code). Desolder the TVS on the shorted rail. If the short disappears → the TVS was the fault (it sacrificed itself). Replace it with the same type (5 V: SMAJ5.0A-class, 12 V: SMAJ12A-class). Running without TVS works but leaves the drive unprotected.
- Short still present after TVS removed? Inject 1–3 V (≤ 5 V) with current limit and find the hot part — usually the motor driver IC.
- Fuse / 0 Ω resistors in the 5 V and 12 V paths: must beep.
- Spindle motor windings (PCB removed, measure on the motor contact pads on the HDA): 3 or 4 pads. Between each pair of the 3 phases you should read equal low values (typically about 1–3 Ω on 3.5″, a few Ω on 2.5″). Open or very different = bad motor (clean-room job). Equal values = motor fine.
- Motor driver outputs on the PCB (to the motor pads) in diode mode: all three phases should read the same. One different = damaged driver.
7.4 Powered checks
- Power from a bench supply (5 V and 12 V, current limit ~1.5 A each). 3.5″ drive spin-up draws ~1.5–2 A on 12 V for a few seconds, then ~0.3–0.6 A.
- Measure the regulator outputs: typically ~3.3 V, ~2.5 V/1.8 V and ~1.0–1.2 V core around the MCU (generated by the motor driver or separate buck/LDO). Missing core rail = regulator or its load is bad.
- Check crystal oscillation with a scope if the board has power but does nothing.
7.5 PCB swap and ROM transfer (very important)
Every HDD has unique adaptives (calibration data for its heads) stored in the ROM on its own PCB. A donor PCB from another drive — even the same model — will usually make the drive click or not be detected unless you move the ROM.
- Match the donor PCB exactly: same board number (printed on the PCB, e.g. WD
2060-771xxx-00x; Seagate100xxxxxx REV x), same MCU, and for Seagate the same firmware family. - If your original board has an 8-pin ROM chip (25-series SPI flash, common on many WD and Seagate boards): desolder it and solder it onto the donor in the same location, or read it with a programmer and write it to the donor’s ROM.
- If there is no 8-pin chip (ROM is inside the MCU): either move the MCU itself (BGA/QFP rework), or read the ROM via the drive’s terminal/vendor commands with PC-3000/MRT and write it to the donor. On some boards the empty 8-pin footprint can be populated so the MCU loads ROM from it.
- On Seagate, read ROM via the serial terminal (TX/RX/GND jumper pins) with a USB-TTL adapter at the correct level — only if you know the commands; mistakes can make data unrecoverable.
- Toshiba/HGST/Samsung: same principle — ROM is unique; match board revision and transfer ROM.
7.6 Brand quick notes
Western Digital
Board number on PCB. Older boards: 8-pin ROM (often near the MCU, labelled U12 on many). Newer: ROM inside MCU. Common: shorted TVS after wrong cable; motor driver burns. Clicking with original board = heads.
Seagate
Serial terminal on jumper pins. Common: TVS short, “BSY” firmware state, F3 firmware lockups (e.g. older 7200.11 families had a known firmware bug). ROM in MCU or 8-pin.
Toshiba / HGST / Hitachi
HGST 3.5″: ROM in 8-pin chip on many boards; reliable PCBs. Toshiba 2.5″: ROM in MCU on many; match exact revision.
USB external drives
Many WD/Seagate portables have the USB bridge on the main PCB (no SATA connector) and hardware encryption. A board swap + ROM transfer is the only path; data may be encrypted to that board’s chip.
8. SATA SSD repair (2.5″ and M.2 SATA)
8.1 SSD block diagram
8.2 Symptoms
| Symptom | Likely cause | What to do |
|---|---|---|
| Not detected at all, PSU current 0 or very high | Shorted input cap / TVS / PMIC, or dead controller | Check input short → rails → controller (8.3) |
| Detected with wrong name (e.g. “SATAFIRM S11”, “PS3111”, “SM2246XT”), 0 GB or 8 MB | Firmware/translator corruption — the controller works but cannot read its FTL | Not a hardware fault. Data recovery needs PC-3000 SSD or vendor tool. Reflashing firmware usually erases user data. |
| Detected, read-only or very slow | NAND worn out (high TBW), drive entered protection mode | Copy data immediately; drive is at end of life |
| Gets very hot instantly | Shorted rail, controller or NAND | Injection to find hot part |
| Disappears randomly | Overheating, bad solder on controller, or power issue on the host | Reflow is a temporary test only; check host port too |
8.3 Step-by-step multimeter checks
- Input to ground (5 V for SATA): normal = no short, diode ~0.4–0.7. Short → check TVS and input caps, then inject ≤5 V / 1 A.
- Fuse after the connector: must beep. Open fuse = something downstream shorted — check rails before replacing.
- Each output rail to ground (measure on the inductors near the PMIC). Typical diode values: 3.3 V NAND rail ~0.3–0.6, 1.8 V ~0.3–0.5, core ~0.1–0.3. 0.000 on one rail = shorted cap or the chip on that rail.
- Power on (bench 5 V, 1 A limit). Idle draw: SATA SSD ~0.05–0.3 A. Measure each rail: 3.3 V, 1.8 V (or 1.2 V), DRAM 1.35/1.2 V, core ~0.9–1.1 V.
- One rail missing → its regulator (check EN and input). All rails missing → PMIC input/enable or the PMIC itself.
- All rails present but not detected → crystal, controller (bad solder / dead), or firmware. Try ROM / safe mode: many controllers have two pads/pins marked
ROM,SAFE,JP1orFW. Shorting them at power-on makes the controller appear in vendor tools (data is generally not touched by entering this mode, but flashing firmware usually wipes the translator).
Data recovery reality: modern SSD controllers scramble and usually encrypt data with a key inside the controller. You cannot desolder NAND and read files on another board. If the controller is dead, data is normally only recoverable by repairing the original board (rails, PMIC, crystal) — the controller and NAND must stay together. Some older controllers (e.g. certain SandForce/Phison/SMI models) can be handled with PC-3000 chip-off; most modern ones cannot.
8.4 TRIM warning
Once the OS deletes files on a working SSD, TRIM erases the blocks. Deleted-file recovery from SSDs is usually impossible — power off the drive as soon as a customer reports accidental deletion.
9. NVMe M.2 SSD repair
Same blocks as the SATA SSD above, but input is 3.3 V from the M.2 slot, the interface is PCIe, and the controllers run hotter (common failure). The most frequent board-level faults: shorted 3.3 V input capacitor, shorted PMIC, and shorted core-rail capacitor.
9.1 M.2 M-key pinout (what to measure)
9.2 NVMe step-by-step
- 3.3 V input to ground: resistance and diode mode. A good NVMe typically shows no short (diode ~0.3–0.6). 0–1 Ω = short.
- Inject 3.3 V (current limit 1–2 A, start at 1 V for safety) into the 3.3 V input. Hot part = usually an input MLCC (remove, test again) or the PMIC.
- PMIC replaced or cap removed, short gone? Power the drive on a bench adapter or in a PC: measure each buck output (core 0.8–1.0 V, DRAM 1.2/1.1 V, VCCQ 1.2/1.8 V, NAND 2.5/3.3 V).
- Core rail shorted (very low diode, gets hot): first check the caps around the controller; if the controller itself heats up, it is dead — data unrecoverable for encrypted controllers.
- All rails good, not detected: check crystal, PERST#/CLKREQ# continuity from fingers to controller, and the controller’s BGA (cracked solder from heat cycling). Try ROM/safe-mode jumper with vendor tools if only the drive (not data) matters.
- Detected but 0 GB / wrong ID → firmware fault, not hardware (same as SATA).
| Controller family | Notes |
|---|---|
| Phison (E12, E16, E18, E21, E26…) | Common in many brands. Has ROM/safe-mode pads on many boards. Hardware-encrypted. |
| Silicon Motion (SM2262/2263/2269/2259…) | Common in budget drives. Safe-mode pads. Encrypted on newer series. |
| Samsung (Phoenix, Elpis, Pascal…) | Samsung drives — proprietary; data recovery only via original board. |
| Realtek, Maxio, InnoGrit, WD/SanDisk in-house | Mostly DRAM-less budget or OEM. Same power-rail method applies. |
10. Laptop motherboard (all brands)
HP, Dell, Lenovo, Asus, Acer, MSI, Toshiba and others are mostly designed by a few ODMs (Compal, Quanta, Wistron, Inventec, Pegatron, Foxconn, LCFC). The board number (e.g. LA-xxxxP, DAxxxxMB, NM-Axxxx, 448.xxxxx) is printed on the board and is what you search for the schematic and boardview. The logic below works on all of them.
10.1 Power sequence (Intel / AMD laptops)
10.2 Measurement table for each stage
| Stage | Where to measure | Expected | If wrong |
|---|---|---|---|
| Adapter input | DC jack center pin / input cap after jack | 19–20 V (some 12 V/15 V) | 0 V: adapter, jack, input fuse. Low: adapter ID problem or input short. |
| Adapter ID (Dell/HP) | ID pin of the jack | Dell: ~3.3–3.5 V idle (1-wire data). HP: ~0.5–0.7 V on many models | 0 V: broken ID line / jack / resistor near EC. Laptop runs but won't charge or slows CPU. |
| ACIN / ACOK | Charger IC ACIN pin | Above ~2.4 V (set by resistor divider from adapter voltage) | Divider resistor open, charger IC dead |
| B+ / VIN | Big caps after input MOSFETs, near charger IC | Adapter voltage (minus ~0.1 V) | 0 V: MOSFET gates not driven → charger IC; short on B+ → find it (6.1). |
| +3VALW / +5VALW | Output inductors of the 3V/5V PWM IC | 3.3 V and 5 V (some boards switch 5 V later) | EN pins, PWM IC, short on rail. Many 3V/5V ICs also make a small LDO (3.3 V/5 V, VREF 2 V) — check those first. |
| RTC | RTC battery / CMOS rail | ~3 V | Low = no start on many boards; replace coin cell / check diode. |
| EC power | EC VCC pins (+3VALW_EC) | 3.3 V | Missing → load switch / resistor |
| EC crystal | 32.768 kHz crystal at EC | Oscillating (scope) | Replace crystal |
| Power button | Button line (NBSWON#, PWR_SW#) | 3.3 V, drops to 0 V while pressed | 0 V always: shorted button/flex. Steady 3.3 V when pressed: broken flex/connector. |
| SLP_S3#/S4#/S5# | PCH test points / resistors / EN pins of RAM & S0 regulators | 0 V → 3.3 V after pressing power | Stay 0: PCH not receiving RSMRST#/PWRBTN#, PCH standby rails missing, BIOS/EC problem, PCH dead. |
| VDDQ (RAM) | RAM PWM output inductor | DDR4 1.2 V · DDR5/LPDDR5 1.1 V / 1.05 V · DDR3L 1.35 V | Short on RAM rail → RAM chip (onboard) or cap |
| VTT | Near RAM PWM | Half of VDDQ (e.g. 0.6 V) | — |
| S0 rails | +3VS, +5VS, +1.8VS, +1.05VS | Correct voltage after power on | Load switch / PWM / EN signal |
| VR_ON / VR_EN | CPU VRM controller EN pin | ~1.0–3.3 V | Missing → previous power-good missing |
| VCCIN / VCORE | CPU VRM output inductors | Intel VCCIN ~1.6–1.8 V; others/AMD ~0.6–1.4 V (changes with load). May be 0 V until boot on some platforms. | Short: MOSFET/cap/CPU. Missing: VRM controller, VR_ON, or no SVID from CPU. |
| PLTRST# / RESET | PCH reset output | Goes high (1–3.3 V) after power-good chain | Stays low → a power-good missing, or BIOS / CPU / RAM fault |
10.3 Current-meter (ammeter) diagnosis — the fastest first test
Power the laptop through a DC bench supply (19 V, 4 A limit) or a USB-C meter, battery disconnected, and read the current.
| Current reading @ 19–20 V | What it means | Look at |
|---|---|---|
| 0.000 A, nothing changes when power button pressed | No power entering the board, or no standby | DC jack, fuse, input MOSFETs, charger IC, 3V/5V ALW, EC |
| 0.000 A and the PSU voltage drops / hits current limit | Short on the input / B+ line | Input caps, input MOSFETs, high-side MOSFETs of every buck on B+ (CPU VRM, RAM, 3V/5V, GPU) |
| 0.01–0.05 A, nothing when pressing power | Standby works, no power-on | Power button, EC, RSMRST#, SLP_S signals, BIOS |
| Jumps to 0.05–0.15 A, then drops back to standby | Starts power-on, then a protection kicks in | A shorted S3/S0 rail (RAM, +3VS, +5VS), missing power-good, BIOS/EC |
| Stuck at 0.2–0.5 A, not moving | Rails on, CPU not running code | BIOS corrupted, RAM, CPU VRM, CPU, PLTRST# |
| 0.2–0.6 A, then repeats (power cycling / restart loop) | RAM training failure or BIOS corruption | Reseat/replace RAM, reflash BIOS, onboard RAM solder |
| 0.6–1.5 A, fluctuating, but no display | System is booting (often good sign) | Display path: screen, eDP cable, LCD VDD, backlight, GPU |
| Jumps to current limit (2–4 A) immediately on power-on | Short on a rail that turns on at power-on | Core rail (CPU/GPU), VRM MOSFETs, GPU |
10.4 Dead laptop — complete flow
Checking for shorts before powering a dead board
Before applying power to a liquid-damaged or dead board, measure resistance / diode to ground on: B+ (19 V), 3VALW, 5VALW, VDDQ, VCCIN/VCORE, GPU core (if dedicated GPU), +3VS, +5VS. Any short here explains the dead board — fix it first.
| Rail shorted | Usual culprits (in order) |
|---|---|
| B+ / VIN | Input/output MLCC caps on B+, high-side MOSFETs of CPU VRM / GPU VRM / RAM / 3V5V, charger IC, USB-C PD controller |
| 3VALW / 5VALW | Caps, EC, USB power switches, audio codec, LAN chip, TPM, PCH |
| VDDQ | Caps near RAM, onboard RAM chip, CPU |
| VCCIN / VCORE / GPU core | Low-side or high-side MOSFET/power stage, cap near CPU/GPU, the CPU/GPU itself |
10.5 Charging problems
| Symptom | Check |
|---|---|
| Works on adapter, battery not charging | Battery itself (cells/BMS), battery connector, SMBus lines (SDA/SCL ~3.3 V), charge MOSFETs, adapter ID (Dell/HP refuse to charge if ID fails), BIOS battery setting |
| Works on battery, not on adapter | DC jack, input fuse, ACIN divider, input MOSFETs, charger IC |
| Charging LED blinks a code | Look up the brand’s LED code (Dell/HP/Lenovo publish them) |
| “Plugged in, not charging” | Battery health / charge threshold set in software, battery temperature sensor, EC firmware |
10.6 USB-C powered laptops
- USB-C first provides only 5 V. The PD controller (e.g. TI TPS65987/65988/65994, Cypress CCG, Realtek RTS54xx, Apple CD3215/CD3217) negotiates 9–20 V over the CC lines.
- Laptop stuck at 5 V (0.0x A) on a USB-C meter → no negotiation: PD controller has no power, its firmware SPI chip is bad, CC line damaged, or shorted VBUS behind the PD controller’s MOSFETs.
- Measure: CC1/CC2 (one shows ~1.6–2.6 V with a charger attached), PD controller 3.3 V / LDO outputs, VBUS before and after the power path MOSFETs.
- Liquid in the USB-C port corrodes the CC and VBUS pins — the most common USB-C charging fault. Check the port pins in diode mode vs the other port.
10.7 Powers on (fan spins), no display
- Connect an external monitor (HDMI). Picture on external = internal screen/cable/backlight problem (go to 10.9). No picture anywhere = board doesn’t boot.
- Read the current (10.3). Stuck low current = not running code.
- Remove RAM, try one stick in each slot, clean contacts. Listen for beep/LED codes (Dell/HP/Lenovo have diagnostic codes).
- Reset CMOS: unplug RTC battery 5+ minutes (or short CMOS jumper).
- Check all S0 rails, VCCIN/VCORE, VDDQ and the power-good chain → PLTRST#.
- If everything is present: reflash BIOS (10.8). Corrupt BIOS is very common after failed updates or power loss.
- Still nothing: onboard RAM, CPU/PCH BGA, GPU (if dedicated GPU drives the internal display).
10.8 BIOS / SPI flash chip
| Item | Details |
|---|---|
| Chip | 8-pin SOIC/WSON: Winbond 25Q64/25Q128/25Q256, Macronix MX25L, GigaDevice GD25, etc. Pin 1 = CS, 2 = DO, 3 = WP, 4 = GND, 5 = DI, 6 = CLK, 7 = HOLD, 8 = VCC. |
| Voltage | Most are 3.3 V; some (e.g. 25Q…W series) are 1.8 V — use a 1.8 V adapter or you will kill them. |
| Read first | Always read and save the original dump twice and compare. It contains the serial number, MAC address, Windows key, and ME region specific to that board. |
| Writing a clean BIOS | Use a dump for the exact board number, then transfer the board-specific data (serial, UUID) or clean the ME region with the proper tool. A wrong ME region causes 30-minute shutdowns on some Intel boards. |
| EC firmware | Some boards store EC firmware in the same chip, others in a separate chip or inside the EC (ENE KB9012 needs its own programmer method). |
| Passwords | Only remove BIOS/supervisor passwords on machines you have proof of ownership for. |
10.9 Screen and backlight
| Symptom | Test | Cause |
|---|---|---|
| Image visible with a flashlight, but dark | Backlight: BL_EN high (3.3 V), PWM present, backlight power (B+ via fuse), boost output (LED anode 20–50 V) | Backlight fuse open, BL_EN missing, LED driver (on board or in panel), panel LED strip |
| Completely black, external works | LCD VDD (3.3 V) at eDP connector after power-on | LCD VDD load switch, fuse, eDP cable, panel |
| Lines/artifacts | Try another panel | Panel or cable (rarely GPU/VRAM — then also on external) |
| Artifacts on external too | — | GPU/VRAM (dedicated GPU) — BGA job |
10.10 USB, keyboard, touchpad, audio, Wi-Fi
- USB no power: 5 V on the port VBUS → USB power switch (load switch, e.g. SY6288/AP2xxx/RT9715/G547) EN pin and input 5 V. Port data: diode-mode D+ / D− vs a good port.
- Keyboard / touchpad dead: connector pins (diode mode vs known good), 3.3 V supply on connector, liquid corrosion on the EC (keyboard matrix goes straight to EC).
- No audio: codec power (3.3 V, 5 V, 1.8 V), codec crystal/clock from PCH (HDA/I2S), speaker amp power and SD/EN pin, headphone jack detect switch.
- No Wi-Fi: 3.3 V at the M.2 E-key slot, W_DISABLE# line, try another card.
- Liquid damage: remove all shields, ultrasonic clean with IPA, dry, then do the short checks for every rail. Look under the EC, PCH, and around connectors for green/white corrosion.
10.11 MacBook notes (Intel and Apple Silicon)
| Rail / signal | Expected | Notes |
|---|---|---|
| PPBUS_G3H (main rail) | ~12.3–12.6 V (Intel models; MagSafe/USB-C) | Like B+. Short = caps, high-side FETs, CD32xx |
| PP3V42_G3H / PP3V3_G3H | 3.42 V / 3.3 V | Always-on for SMC. Missing → LDO or short |
| PP5V_S5 / PP3V3_S5 | 5 V / 3.3 V | Standby rails |
| SMC_RESET_L, PM_SLP_S4_L, PM_SLP_S3_L | 3.3 V high | Same idea as PC sequence |
| USB-C stuck at 5 V | Should go to 20 V | CD3215/CD3217 port controllers, their 3.3 V LDO, port corrosion |
| T2 / Apple Silicon | — | Revive/restore via Apple Configurator (DFU) before replacing chips; SSD is soldered and paired — data lives only with that board. |
11. Desktop motherboard
Same methods, different input: the ATX power supply gives 5VSB (always on), 12 V, 5 V, 3.3 V (after PS_ON#).
| Check | Expected | If wrong |
|---|---|---|
| 5VSB (purple wire, 24-pin) | 5 V with PSU switched on | PSU fault or 5VSB short on board |
| PS_ON# (green wire) | ~3.3–5 V, drops to 0 V when power button pressed | Stays high: Super I/O, power button header, PCH sequence |
| Rails to ground (PSU unplugged) | 12 V, 5 V, 3.3 V no short | Short on 12 V → VRM MOSFETs (very common), GPU slot |
| VCORE (CPU VRM output chokes) | ~0.8–1.5 V when running | Shorted VRM MOSFETs, controller, CPU |
| DRAM VDDQ | DDR4 1.2 V, DDR5 ~1.1 V (DDR5 has PMIC on the RAM stick) | RAM VRM |
| Debug | POST code card / board Q-LEDs (CPU, DRAM, VGA, BOOT) | Follow the LED that stays on |
Super I/O (ITE IT86xx, Nuvoton NCT67xx) plays the role of the EC. Bulging capacitors around the VRM on old boards = replace with same-or-better polymer caps.
12. Processor, GPU and BGA chips
A CPU or GPU die cannot be repaired. What you can do: decide whether the chip or the board is bad, replace small parts on the chip package, repair sockets, and reball / replace BGA chips.
12.1 Is it the CPU or the board?
- Measure VCCIN/VCORE to ground. Note the Ω and diode value; compare to a good board.
- Socketed CPU (desktop / old laptops): remove the CPU and measure again. Short gone → CPU is shorted. Short still there → board (MOSFET/cap).
- BGA CPU (soldered): inject 1 V with current limit. If the CPU package heats evenly and no MOSFET/cap heats first → CPU short. Check the small caps on the CPU package itself (top or bottom): a shorted package cap is common on many Intel and AMD mobile chips — remove it and re-measure. If the short disappears, the CPU often works without that single cap.
- Run a known-good CPU in the socket if you have one — the definitive test.
12.2 Typical processor-related faults
| Fault | Sign | Fix |
|---|---|---|
| Bent socket pins (LGA) | One RAM channel missing, no POST, random reboots | Straighten with a needle under microscope; replace socket if broken |
| Cracked BGA solder | Works when pressed/warm, fails when cold; GPU artifacts | Reflow is temporary; reball is the real fix |
| Dead GPU/CPU die | Core rail shorted inside chip | Replace chip (new/refurbished, same stepping/part number) or replace board |
| VRM failure | High-side MOSFET short → CPU killed by input voltage | Replace MOSFETs, check CPU survived (core rail diode value) |
| Thermal shutdown | Turns off under load | Fan, dried paste, clogged heatsink, VRM thermistor |
12.3 BGA reballing process
- Preheat board from below to ~150–180 °C. Protect nearby plastic parts with Kapton/aluminium tape.
- Remove the chip with hot air or a BGA station (lead-free solder melts ~217–220 °C; peak ~235–245 °C).
- Clean the chip and board pads with flux and wick — flat, shiny, no bridges, no ripped pads.
- Apply flux on the chip, place the correct stencil and ball size (0.3/0.4/0.45/0.5/0.6 mm), fill balls, heat until they form round balls.
- Clean, flux the board, align chip by silkscreen corners, reflow (leaded balls ~200–215 °C peak). The chip self-aligns when solder melts.
- Let cool slowly; never move the board while hot. Check rails for shorts before powering.
13. Soldering & rework settings
| Job | Tool | Typical setting |
|---|---|---|
| 0402/0603 resistors & caps | Iron or hot air | Iron 330–360 °C; hot air 330–360 °C, low airflow |
| SOT-23 / SO-8 MOSFETs | Hot air | 350–380 °C, medium airflow, plenty of flux |
| QFN power ICs (charger, PWM) | Hot air + preheater | 370–400 °C top, 120–150 °C bottom. Tin the pads lightly, align, reflow. |
| Ground-heavy parts (big caps, connectors) | Hot air + preheater | Add low-melt solder to lower the melting point |
| BIOS chip (SOIC-8) | Hot air or drag solder | 350 °C; or read in-circuit with a clip (may fail if the board back-powers) |
| BGA chips | BGA station / hot air + preheater | See 12.3. Use a thermocouple near the chip. |
- Always mix leaded solder into lead-free joints — they melt lower and flow better.
- Too much heat lifts pads. If a pad lifts, scrape the trace and bridge with a thin wire (jumper) secured with UV mask.
- Clean flux residue with IPA — some fluxes are conductive or corrosive when left.
- Replace parts with the same value and voltage rating (caps), same RDS(on)/voltage/package (MOSFETs). Cap voltage rating must be equal or higher.
14. How to work on any specific model
- Find the board number: printed on the PCB (laptop:
LA-,DA0…MB,NM-,6050A…,820-xxxxxfor Apple; HDD: PCB number; SSD: controller part). - Get the schematic (PDF): shows every rail, IC, signal name and the power sequence page. Search the board number + “schematic”.
- Get the boardview (
.brd,.bdv,.fz,.cad): shows physical location of every part. Open with OpenBoardView (free) or FlexBV. Some boardviews include diode values and voltages. - Open the schematic power sequence / power block diagram page — it maps exactly onto the table in 10.2.
- Look up datasheets for every IC you suspect (charger, PWM, VRM, PD controller) to learn pin functions.
- Keep your own log: model, symptom, faulty part. The same models fail the same way again and again.
Join technician forums and communities for your region; many share schematics, boardviews, BIOS dumps and known faults per model. Respect copyright and only use dumps for repairing the matching machine.
15. Quick reference sheet
Standard voltages
Laptop input: 19–20 V (USB-C 5→20 V)
B+: = adapter / battery (≈11–17 V battery)
ALW: 3.3 V, 5 V · RTC: ~3 V
DDR3L 1.35 · DDR4 1.2 · DDR5/LPDDR5 1.1/1.05 · VTT = ½ VDDQ
PCH: 1.8 V, 1.0–1.05 V
Intel VCCIN ~1.6–1.8 V · core 0.6–1.4 V
HDD: 5 V (+12 V for 3.5″)
SATA SSD: 5 V in · NVMe: 3.3 V in
SSD rails: 3.3 / 2.5, 1.8 / 1.2, DRAM 1.35/1.2/1.1, core 0.8–1.2
Diode mode (red on GND)
0.000 = short
0.005–0.150 = CPU/GPU core (compare!)
0.100–0.350 = low-voltage rails
0.350–0.800 = 3.3/5 V rails, signals
0.8–1.5+ = input rails
OL = open / missing path
Laptop current @ 19 V
0.00 A = no standby / no input
0.01–0.05 = standby, no power-on
jumps then drops = protection / short on S0
0.2–0.5 stuck = BIOS/RAM/CPU
0.2–0.6 cycling = RAM/BIOS
0.6–1.5 fluctuating = booting → check display
hits limit = short
First suspects
HDD dead → TVS diode
HDD clicks → heads (or ROM if PCB swapped)
SSD dead → input cap / PMIC
SSD 0 GB / wrong name → firmware
Laptop dead → B+ short, 3V/5V, EC
No charge → adapter ID, charger IC, battery
USB-C 5 V only → PD controller / port
No display → RAM, BIOS, LCD VDD, backlight fuse
Core short → MOSFET, cap, then CPU/GPU
Remember: power off → check shorts. Power on → follow the sequence. The first thing missing is your fault. Compare everything with a good board, the boardview, or a symmetrical circuit.
Values in this guide are typical ranges. Always confirm exact voltages, pinouts and part numbers from the schematic and datasheet for the model on your bench.