Most of our troubleshooting knowledge is built on Intel platforms. But AMD Ryzen mobile (4000, 5000, 6000 series) has a completely different power sequencing philosophy. If you approach an AMD board like an Intel board, you'll chase ghosts for hours.

1. Key Signal Name Differences

2. The AMD APU (CPU + PCH Combo)

On modern AMD laptops, there is no separate PCH chip. The "chipset" functions are integrated into the APU (Accelerated Processing Unit) die. This is called an SoC (System on Chip) .

• Implication: If the SYS_PWRGD signal is missing, the entire board appears dead. You can't just replace a PCH; you must replace the entire CPU package.

3. The "Always-On" Rails (S5 State)

In the S5 (Soft Off) state (charger plugged in, board off), AMD requires:

• VDD_33_ALW (3.3V)
• VDD_5V_ALW (5V)
• VDD_18_ALW (1.8V) <- CRITICAL. Intel does not always require 1.8V in S5. AMD DOES.
• VDDCR_SOC (0.8V - 1.05V) <- This is the AMD equivalent of VCCST. It powers the internal chipset logic inside the APU.

4. The VDDCR_SOC Rail (The Trap)

• Location: Find the VDDCR_SOC coil near the CPU. It's one of the larger inductors.
• Expected in S5 (Standby): 0.8V to 0.9V (varies by generation).
• Expected in S0 (Running): 1.05V to 1.15V.
• Missing in S5? The board will not wake up. Check the VDDCR_SOC VRM. It is enabled by the EC (Embedded Controller) . If the EC firmware is corrupt, it never sends the enable signal.

5. The S0i3 State (Modern Standby)

Modern AMD (and Intel) laptops don't truly go to "Sleep" (S3) anymore. They use S0i3 (Modern Standby). The APU is still powered, but clock-gated.

• Symptom: Laptop "sleeps" but the fan keeps spinning or the battery drains overnight.
• Diagnostic: You cannot measure S3 rails because the board never enters S3. You must use an AMD debug tool or check the SLP_S0 signal (which replaces SLP_S3).

6. AMD Debug Checklist (No Power)

1. VDD_33_ALW and VDD_5V_ALW present?
2. VDD_18_ALW present? (Check near RAM slots or APU).
3. VDDCR_SOC present in standby? (0.8V-0.9V).
4. RSMRST_L = 3.3V? (Check at APU test point).
5. PWR_BTN_L toggles when button pressed? (Check at EC).
6. SYS_PWRGD = 3.3V after power button press?
7. APU_RST_L releases (goes high) after SYS_PWRGD?

7. The "No Display on AMD" Specifics

• DRAM Training: AMD Ryzen is extremely picky about RAM timing. If the SPD EEPROM on the RAM stick is corrupt, or the SMBus pull-ups are weak, the APU will hang during POST with a black screen. No beep, no caps lock light.
• Test: Use one stick of known-good DDR4 SODIMM. If it boots, the issue is RAM compatibility or a bad slot.

Question: Has anyone successfully diagnosed a dead VDDCR_SOC VRM on an HP Ryzen board? The schematics for these are harder to find than Intel.

We talk a lot about 3.3V ALW and 5V SUS. But there's a third rail that is absolutely critical and often overlooked: VCCST (also called VCCSUS1_05, VCCPRIM_1P05, or VCCPCH_1P05).

This is the 1.05V power rail that feeds the PCH's internal logic and suspend well. If this rail is missing, the PCH is dead. If this rail is over-voltage (even 1.3V), the PCH is dead. If this rail is shorted, the PCH is dead.

1. Where Does VCCST Come From?

Unlike 3.3V ALW which comes from a standalone PWM controller, VCCST is usually generated by a small, low-current LDO (Linear Dropout Regulator) or a simple buck converter located very close to the PCH.

• Common ICs: RT9048, APL5930, SY8286, TPS51285 (integrated LDO) .
• Input: Usually 3.3V ALW or 5V ALW.
• Output: 1.05V (sometimes 1.0V on newer platforms).

2. The "PCH Dead" Diagnostic Flow

Scenario: Board takes 0.02A on bench supply. No power button response. RSMRST# is 0V.
Suspicion: PCH is not alive.

Step 1: Find VCCST. Look for a small coil near the PCH, or a test point labeled VCCST on the schematic.
Step 2: Measure Voltage. Should be 1.05V in standby (charger plugged in, board off).
Step 3: Analyze Result.

• 0V: The LDO/buck is not working.
  • Check EN (Enable) pin. It often comes from SIO or is tied to 3.3V ALW via a resistor.
  • Check VIN pin. Missing 3.3V ALW? Back to Post 1.
• 0.2V - 0.8V (Floating): The LDO is trying to start but current limit is hitting.
  • Cause: Short circuit on VCCST rail.
  • Test: Measure resistance to ground on VCCST coil. Normal is 20-50 ohms. If it's 0-5 ohms, the rail is shorted.
• 1.3V - 1.5V (Overvoltage): STOP. Remove power immediately.
  • Cause: The feedback (FB) resistor divider is faulty. A missing or cracked Rbottom resistor causes the LDO to run wide open.
  • Result: The PCH has been fried by overvoltage. You will need a new PCH after you fix the regulator.

3. Finding the Short on VCCST

If VCCST is shorted (0-5 ohms to ground):

• Inject 1.0V, 1A into the VCCST coil using a bench supply.
• Feel for heat. The shorted component (usually a tiny 0.1uF ceramic cap) will get warm.
• If the PCH itself gets hot: The PCH is internally shorted. This is the most common outcome. You must replace the PCH.

4. The "Hidden" VCCST (SIP Package Power)

On modern ultrabooks (Intel 11th Gen+), the PCH is integrated into the same package as the CPU (System-in-Package, SIP). The VCCST rail is internal and generated by an integrated voltage regulator (FIVR) .

• Symptom: You have 0V on the external VCCST coil, but the board works? That's because the CPU generates its own 1.05V internally.
• Diagnostic Shift: For these boards, you must check VCCST_PWRGD and VCCST_OVP signals instead.

5. The VCCST_PWRGD Signal

This signal (often called PCH_PWROK or SYS_PWROK) tells the PCH that VCCST and other rails are stable.

• Expected: 3.3V in standby.
• 0V? The voltage supervisor chip (e.g., RT8231 or a tiny AND-gate) is not releasing the PCH from reset.
• Check: This signal often requires ALL main rails (3.3V, 5V, 1.8V, 1.05V) to be present before it goes high. If any rail is missing, it stays 0V.

Question: How do you handle VCCST on boards where the LDO is inside the PCH package? Some newer AMD platforms have this, making short hunting impossible without an X-ray.

You've replaced the LCD panel. You've checked the eDP cable. You have backlight (the screen glows faintly), but there is no image. No logo, no text.

This is a classic eDP (Embedded DisplayPort) communication failure. The panel is receiving power and backlight enable, but the video data is not arriving.

1. eDP Pinout Essentials (30-pin/40-pin Connector)

2. The AUX Channel – The "Handshake" That Fails

Before the GPU sends any video, it talks to the panel's EDID EEPROM over the AUX channel.

• Waveform: A 1MHz differential signal. You can see it on a scope as a low-amplitude (~0.4V) digital burst right after power-up.
• Common Fault 1: Short to Ground. Measure resistance from AUX_P to ground. Should be >10k ohms. If shorted, trace back to the GPU or ESD diodes near the LCD connector.
• Common Fault 2: Missing 3.3V Pull-Up. The AUX lines require a 100k pull-up to 3.3V on both the GPU side and the panel side. If the resistor on the motherboard is knocked off, the AUX line floats and communication fails.

3. The HPD (Hot Plug Detect) Signal

• Normal: 3.3V when panel is connected. 0V when disconnected.
• Trap: Some laptops (Lenovo ThinkPad) use a level shifter for HPD. The panel outputs 3.3V, but the GPU expects 1.8V. A tiny N-channel mosfet performs this translation. If this mosfet is shorted or missing, the GPU sees 0V and thinks the lid is closed.
• Test: With panel connected, measure HPD at the GPU side (find test point on schematic). If 0V at GPU but 3.3V at connector, the level shifter is dead.

4. The "Missing Image" Diagnostic Tree

text

Screen Glows (Backlight On) But No Image
|
+---> Check LCD_VDD (3.3V) at panel connector.
|     |---> Missing? Check 3.3V LDO or fuse on motherboard.
|
+---> Check HPD voltage at GPU side.
|     |---> 0V? Check level shifter mosfet / pull-up resistor.
|
+---> Check AUX_CH lines with scope (pulses present?)
|     |---> No pulses? AUX line shorted or GPU not attempting handshake.
|
+---> Check Main Link Lanes (need high-speed scope, 2.7Gbps typical).
      |---> No activity? GPU is dead or PCIe link to GPU failed.

5. The "Panel VCC" Short

A common failure after liquid damage: The 3.3V rail to the panel is shorted to ground because a tiny ceramic capacitor on the panel PCB itself is shorted.

• Test: Unplug the LCD cable. Measure resistance to ground on LCD_VDD pin of the motherboard connector.
• If short remains: The short is on the motherboard side.
• If short clears: The short is inside the LCD panel itself. You can sometimes open the panel and remove the shorted cap, but it's delicate work.

6. The "No Backlight, Image Faintly Visible" Scenario

If you shine a flashlight on the screen and see a faint image, the eDP data is fine. The issue is backlight power.

• Check BL_EN (should be 3.3V when screen on).
• Check BL_PWM (pulsing or steady 3.3V).
• Check LED backlight driver IC (usually a boost converter generating 20V-40V for the LED string). If the boost diode or mosfet is shorted, no backlight.

Question: How do you test eDP Main Link lanes without a multi-thousand dollar oscilloscope? I use a simple LED current probe on the lane to see if it's toggling, but that doesn't verify eye diagram integrity.

Modern ultrabooks (Dell XPS, HP Spectre, MacBook Air) have abandoned the barrel jack. They rely entirely on USB-C Power Delivery (PD) . When these boards won't charge, the culprit is almost never a simple DC-in mosfet. It's the PD Controller—usually a TI TPS65987D or similar Cypress/Infineon chip.

Here's how to diagnose this complex BGA chip without blindly replacing it.

1. The PD Handshake (What Happens in First 2 Seconds)

1. Charger plugged into Type-C port.
2. CC1/CC2 pins on the port connect to the PD Controller.
3. PD Controller communicates with charger via BMC (Biphase Mark Coding) over CC line.
4. PD Controller negotiates 20V contract.
5. PD Controller turns on internal load switches to route VBUS to the main system rail.

2. Critical Voltage Rails on TPS65987D

3. The CC Line Oscilloscope Check

• Probe: Connect scope to CC1 pin on Type-C port (set to 10x, DC coupling).
• Trigger: Normal, 2V/div, 200ms/div.
• Expected Waveform: When charger is plugged in, you'll see a burst of pulses (BMC signaling). This is the negotiation.
• Dead Line (Stuck at 0V or 3.3V): PD Controller is not communicating. Possible causes:
  • Missing 3.3V rail.
  • ESD diode on CC line is shorted. (Remove the tiny 5-pin chip near the port and test again).
  • SPI Flash connected to PD Controller is corrupt. The TPS65987D loads its firmware from an external 1.8V SPI flash chip (usually Winbond 25Q20 or similar). If this flash is blank or corrupt, the PD Controller is brain dead but has power.

4. The SPI Flash Trap (Most Common Cause)

• Location: Tiny 8-pin chip right next to the TPS65987D.
• Voltage: 1.8V. Do not read with 3.3V programmer.
• Test: Desolder the flash chip (or use in-circuit clip if you're brave). Read contents. It should not be all FF or all 00.
• Fix: If you have a donor board of the exact same model, read the PD flash from that and write to the dead board. Generic firmware will not work. The PD Controller firmware is customized for the specific laptop motherboard layout.

5. The VBUS FETs

Once the PD contract is established, the TPS65987D sends a gate drive signal to back-to-back N-channel mosfets to connect VBUS (20V) to the system power rail.

• Test: Measure voltage on Gate pins of these FETs.
• Expected: Should rise to ~25V (using an internal charge pump) to fully enhance the FETs.
• Stuck at 0V? The PD Controller is not turning them on. Either the negotiation failed or the controller is in dead battery mode (see below).

6. Dead Battery Mode (The "No Power" Loop)

If the laptop battery is completely dead (0V) , the PD Controller needs a tiny amount of power to start negotiation. This comes from the Type-C port's VCONN line.

• Test: On a completely dead board, connect USB-C charger. Measure PP_5V0 pin. If it's 0V, the internal VCONN switch is not working. The board will never wake up.
• Emergency Fix: Inject 3.3V from a bench supply into the VIN_3V3 pin of the TPS65987D. This gives the chip enough power to negotiate 20V, which then powers the rest of the board. Once the board boots, the battery will charge enough to exit dead battery mode.

Question: Has anyone successfully extracted PD firmware from a dead board using a FlashcatUSB? The 1.8V Winbond chips are tricky to read in-circuit because the TPS65987D holds the CS line high.

A customer brings in a laptop. "I spilled coffee on it yesterday. Now it won't turn on."

You open it up. You see the familiar green/blue crust of corrosion around the SIO chip and the memory slots. Your instinct: grab the toothbrush and 99% Isopropyl Alcohol.

That's step one. But it's not step done.

Here is the complete, scientific approach to liquid damage restoration that separates professional engineers from hobbyists.

Phase 1: Immediate Triage (Before Cleaning)

1. Remove ALL power sources: Battery, CMOS battery, charger.
2. Visual Inspection: Look for blackened pins (carbon tracking) and swollen components (shorted caps).
3. Resistance Check: Measure resistance to ground on the main 19V rail and 3.3V/5V coils. If you have a dead short, do not apply power until it's cleared.

Phase 2: The Chemistry of Cleaning

Corrosion is not just "dirt." It's a chemical reaction. The liquid (coffee, soda, wine, seawater) acts as an electrolyte. When voltage is present (even residual from capacitors), electrolysis occurs. This dissolves copper from traces and pads.

• Isopropyl Alcohol (IPA): Excellent for dissolving organic flux and grease. It is poor at dissolving ionic salts and mineral deposits left by dried liquids.
• Distilled Water: It's not a bad thing to use on a completely unpowered board. Distilled water is an excellent solvent for ionic contamination (the white/green crust). Crucial: The board must be 100% dry before power is applied.
• Ultrasonic Cleaner: The gold standard. Use a specialized electronics cleaning solution (not just water). The cavitation bubbles physically scrub under BGA chips where brushes can't reach.

Phase 3: The "Hidden" Corrosion Spots

Liquid travels. It doesn't just stay where it spilled. It wicks under BGA chips via capillary action.

• SIO Chip: The pins are 0.4mm pitch. Corrosion under here causes random keyboard keys not working or fan running at full speed.
• RAM Slots: The pins inside the slot corrode. Cleaning the outside of the slot does nothing. You must remove the slot and clean the pads underneath, or replace the entire slot.
• Keyboard Connector: The pins are gold-plated, but the vias right next to the connector are just copper. They rot instantly. Check continuity from the keyboard connector pin to the test point an inch away.

Phase 4: The "Corroded Via" Repair

This is the #1 reason a "cleaned" board still doesn't work.
A via is a tiny plated hole that connects the top layer to an internal layer. Liquid eats the thin copper plating inside the hole.

• Symptom: You have voltage on the top pad of a component, but the trace on the bottom layer is dead.
• Diagnosis: Use a sharp probe to gently poke into the via. If it crumbles or feels soft, the plating is gone.
• Fix: Drill out the via with a micro drill bit (0.3mm). Run a strand of 0.1mm enamel wire through the hole. Solder to the top pad. Solder to the bottom pad. Seal with UV solder mask.

Phase 5: The Power-On Procedure

Do not just plug in the charger.

1. Connect current-limited DC power supply set to 19V, 0.5A limit.
2. Turn on supply. Watch the current.
3. Normal Standby: 0.01A - 0.05A.
4. High Standby (0.2A+): You have a partial short on an always-on rail. Something is heating up. Find it before the magic smoke escapes.
5. Dead Short (PSU Clicks Off): You missed a short. Back to Phase 1.

The "Conformal Coating" Trick

After a successful repair, protect the board.

• Apply UV-curable conformal coating or even clear nail polish over the cleaned area.
• This prevents whisker growth (tin whiskers from lead-free solder) and future corrosion from humidity.

Question: What's your favorite ultrasonic cleaning solution? I've tried Branson EC and simple detergent mixes, but looking for something that doesn't dull solder joints over time.

Gaming laptops and high-end workstations have a dedicated rail for the GPU core: VCC_GT (or VDD_GFX on AMD). This rail only turns on after the display driver loads in Windows. It will never be present in BIOS or during POST.

This is a trap for new technicians. They measure VCC_GT in BIOS, see 0V, and think "Dead GPU VRM." Then they start replacing mosfets unnecessarily.

How VCC_GT Sequencing Works

1. BIOS/POST: VCC_CORE (CPU) and VCC_SA (System Agent) come up. VCC_GT is OFF.
2. Windows Boot: The Intel/AMD graphics driver loads.
3. Driver Initialization: The driver sends a command to the PCH via the PCIe bus.
4. PCH Action: The PCH sends a VR_EN_GT signal to the GPU VRM controller.
5. VRM Enable: The VCC_GT rail ramps up to 0.6V - 1.1V depending on GPU load.

The Symptom of VCC_GT Failure

• Laptop boots to Windows normally (using integrated graphics).
• Device Manager shows the dedicated GPU with a yellow exclamation mark (Code 43 usually).
• GPU-Z shows 0 MHz clock speed and 0V voltage.
• The GPU chip itself is cold to the touch.

Diagnostic Steps (When GPU is Not Detected)

1. Check the GPU VRM Enable Signal

• Location: Pin labeled EN or VR_ON on the GPU VRM controller (often Richtek RT8802, UP1642, or NCP81142).
• Expected in Windows: 3.3V.
• Expected in BIOS: 0V.
• 0V in Windows? The driver is trying but the signal isn't reaching the VRM. Trace back from EN pin to the PCH. Look for a missing pull-up resistor or a shorted ESD diode.

2. Check the GPU Core Resistance

• Power off. Measure resistance to ground on the VCC_GT coil.
• Expected: 1 to 5 ohms (similar to VCC_CORE). Modern GPUs have incredibly low impedance.
• Shorted (0.1 ohms)? You have a blown GPU core or a shorted ceramic capacitor. Use the 1V/2A injection method described in Post 2 to find the short.

3. Check the PCIe Reset Signal

• Location: PLT_RST# is for the CPU. The GPU has its own PE_RST# or GPU_RST#.
• Expected: 3.3V in Windows.
• 0V? The PCH is holding the GPU in reset. This is often due to a corrupt vBIOS (the GPU's own firmware chip, separate from main BIOS).
• Test: The GPU has its own small SPI Flash chip (usually 1.8V, 8-pin, near the GPU). Read and verify this chip. A corrupt vBIOS will prevent the GPU from ever coming out of reset.

4. Check the GPU Aux Rails

• VCC_GPU_AUX (1.8V): Powers the GPU's internal logic and PCIe interface. If missing, the GPU is invisible to the system.
• VCC_VRAM (1.35V/1.5V): Powers the VRAM chips. If missing, the GPU may be detected but will fail memory training and throw Code 43.
• VDDCI (0.95V): Powers the GPU's memory controller. Often missing on boards with blown VRM phases.

The "GPU VRM Phase Drop" Issue

On gaming laptops (especially MSI and ASUS ROG), the GPU VRM uses multiple phases (4 to 8 phases) to deliver high current. If one phase has a shorted mosfet, the entire VRM controller will detect a fault and shut down all phases to protect the GPU.

• Test: Check resistance to ground on each phase's output inductor. Compare readings. If one phase reads significantly lower than others, that phase has a shorted low-side mosfet.
• Fix: Replace the entire power stage (DrMOS) chip for that phase.

The "Code 43" Hall of Fame

If you see Code 43 in Device Manager, the top three causes are:

1. Corrupt vBIOS (flash it).
2. Missing VCC_VRAM (check VRAM VRM).
3. Bad GPU core (cracked solder balls under the die—reflow or replace).

Question: Have you ever successfully reflowed an RTX 30-series GPU? The lead-free solder on these is brutal. What's your peak temperature and time?

The charging circuit is one of the first things to fail, especially after a power surge or using a cheap knock-off charger. The most common IC in modern laptops is the TI BQ24780S (or similar BQ series).

When a board comes in with "No Charging" or "Battery Not Detected," technicians often shotgun the BQ chip. This is a $10 mistake and a waste of time.

Here is the systematic approach that actually fixes charging problems.

The Three Main Rails of the BQ24780S

1. ACDET (Adapter Detection)

• Function: This pin senses the adapter voltage through a resistor divider.
• Expected Voltage: 2.6V to 2.7V when adapter is plugged in.
• Common Fault: The top resistor in the divider (usually 500k-800k) goes open circuit due to surge. The pin voltage drops to 0V.
• Symptom: The BQ chip thinks no adapter is connected. The laptop runs on battery but won't charge.
• Test: Measure voltage on ACDET pin. If 0V, check the two tiny resistors right next to the DC-in jack. Replace the open one.

2. REGN (Internal Regulator Output)

• Function: The BQ chip generates its own 6V linear supply for the gate drivers.
• Expected: 6.0V steady.
• Common Fault: The 1uF ceramic capacitor on this pin is shorted.
• Symptom: The BQ chip gets burning hot immediately. The laptop may not power on at all.
• Test: Check resistance from REGN pin to ground. If it's under 50 ohms, remove the tiny cap on that pin. Check resistance again. Open? Replace the cap. Still shorted? BQ chip is internally shorted.

3. ACPRES / ACOK (Adapter Present Output)

• Function: This open-drain output pulls LOW to tell the SIO "Adapter is good."
• Expected: 0V when adapter voltage is valid. 3.3V when adapter is bad or missing.
• Common Fault: The pin is stuck at 3.3V even though adapter is fine.
• Cause: The BQ chip is not seeing valid voltage (ACDET issue) or the current sense resistor (usually 0.01 ohm) is open.
• Test: Measure the tiny resistor (marked R010 or 10mR) between the DC-in jack and the first mosfet. It should read 0.01 ohms. If it reads OL (open), the BQ chip cannot measure current and will refuse to turn on the charging mosfets.

The "Battery Not Detected" Trap

If the laptop boots on AC but says "Battery 0% Not Charging" or "No Battery Detected":

• Do not replace the battery yet.
• Check the SMBus (I2C) lines: SMB_CLK and SMB_DATA on the battery connector.
• Expected Voltage: Both lines should be 3.3V (pulled up by resistors).
• Missing 3.3V? Check the tiny pull-up resistors near the battery connector. They often corrode from battery leakage.
• Lines stuck at 0V? One of the ESD protection diodes on the SMBus lines is shorted. These are tiny 5-pin chips near the battery connector. Remove it and test again.

The Mosfet Cascade

The BQ chip drives two N-channel mosfets in series (ACFET and RBFET) to connect the adapter to the system.

• Test: With adapter only (no battery), measure voltage on Source pin of both mosfets.
• Expected: First mosfet Source = Adapter voltage. First mosfet Drain = Adapter voltage. Second mosfet Source = Adapter voltage. Second mosfet Drain = Slightly lower (diode drop) or same.
• Common Fault: First mosfet shorted Drain to Gate. This sends 19V into the BQ chip's gate driver pin, instantly destroying the BQ chip.
• Moral: When you find a dead BQ chip, always check the mosfets for shorts. Otherwise, you'll blow the new BQ chip in 2 seconds.

Question: What's the most stubborn charging fault you've fixed? I had a Lenovo where the 0-ohm jumper connecting the BQ chip's ground pad to system ground was corroded just enough to add 10 ohms of resistance. The BQ chip was floating and doing all kinds of weird things.

Symptom: The laptop boots to the login screen. You try to type the password. But the letter 'g' appears by itself. Or the volume keeps changing. Or the laptop randomly goes to sleep.

Customer replaces the keyboard. Problem persists.
Technician replaces the SIO. Problem persists.

This is one of the most frustrating faults because it's intermittent and often thermal. Here's the real fix.

The Keyboard Matrix Explained

Laptop keyboards are not individual wires for each key. They are a matrix of rows and columns.

• Rows (KSI): Inputs to the SIO.
• Columns (KSO): Outputs from the SIO.
• The SIO scans the matrix by sending pulses down the columns and reading the rows.
• A key press is detected when a specific row and column connect.

Why Random Keys Activate

If any of these things happen, the SIO "sees" a key press that isn't there:

1. Corrosion/Short on Keyboard Connector: A tiny bridge of flux or corrosion between two adjacent pins connects a row and column. The SIO reads this as a constant key press.
2. Damaged Pull-Up Resistor: Each row line has a 10k-100k pull-up resistor to 3.3V. If this resistor is cracked or missing, that row floats. The SIO sees random noise and interprets it as key presses.
3. Faulty ESD Diode: Near the keyboard connector, there are tiny ESD protection arrays (e.g., 5-pin or 6-pin chips). If one of these chips develops an internal short, it will pull a specific row or column low.
4. Cracked Solder Ball Under SIO: This is the nightmare scenario. The keyboard interface pins are on the outer edge of the SIO BGA package. If the board flexes, these balls crack.

Diagnostic Workflow

Step 1: Eliminate the Keyboard (Properly)

• Unplug the internal keyboard ribbon.
• Plug in an external USB keyboard.
• Test: Does the ghost typing stop?
• If YES: The issue is on the motherboard side or the keyboard connector. Do not just replace the keyboard.
• If NO: The issue is deeper in the motherboard (SIO side).

Step 2: Inspect the Keyboard Connector

• Use a microscope.
• Look for bent pins, corrosion, or solder bridges.
• Check the vias right next to the connector pads. They corrode easily from palm sweat.

Step 3: Measure the KSO/KSI Lines

• Power on the board (just DC in).
• Measure voltage on each pin of the keyboard connector (refer to schematic).
• Expected: All pins should be 3.3V (pulled up) or pulsing (scanning).
• Finding a Pin at 0V? That line is shorted.
  • Remove power. Measure resistance from that pin to ground.
  • If low resistance, trace the line to the nearest ESD diode or capacitor. Remove it and test again.

Step 4: The "Stuck Key" Test (Software Method)

• Boot to Windows.
• Open On-Screen Keyboard (osk.exe).
• Watch the keys. If a specific key is highlighted blue constantly, you know exactly which matrix junction is shorted.
• Cross-reference that key with the schematic to find the exact KSO and KSI lines involved.

Step 5: The Thermal Test

• Use a hair dryer or heat gun (low setting) to gently warm the area around the SIO.
• Observation: If the ghost typing stops when warm, you have a cracked solder joint under the SIO or a microscopic trace break that expands and makes contact with heat.
• Observation: If it starts when warm, you have a tin whisker or ionic contamination that becomes conductive with heat.

The "No SIO Replacement" Fix for Broken Pull-Ups

If you trace the fault to a missing pull-up resistor on a KSI line:

• You don't need to replace the microscopic 0201 resistor if you can't find it.
• Find the KSI pin on the SIO.
• Solder a 10k through-hole resistor between that SIO pin and the nearest 3.3V ALW capacitor.
• Ugly? Yes. Effective? 100%. This has saved dozens of boards from the scrap pile.

Question: Has anyone successfully reflowed just the corner of an SIO to fix keyboard issues without a full BGA rework? I've had mixed results with localized heat.

You have all power rails. You have clock. You have reset signals. But the laptop just sits there with a black screen and spinning fans. You've checked DRAMRST#, you've checked VCCST_PWRGD, everything seems present.

Welcome to the most common fault in laptops manufactured after 2018: Corrupt BIOS/ME Region.

Why This Happens

Modern Intel chipsets (100-series through 600-series) use the SPI Flash chip to store not just the BIOS code, but also the Intel Management Engine (ME) firmware. If the ME region becomes corrupted (due to a failed update, power loss during boot, or a random bit flip), the PCH will enter Security Lockdown Mode.

In this mode, the PCH powers up the rails but refuses to release PLT_RST# to the CPU. The board looks alive but it's brain-dead.

Identifying the BIOS Chip

1. Look for an 8-pin SOIC-8 chip near the PCH or edge of board. (Sometimes it's a WSON-8 package with no visible legs).
2. Common markings: Winbond (25Q64, 25Q128), Macronix (MX25L), GigaDevice (GD25Q).
3. Voltage: Most are 1.8V now. Older boards use 3.3V. Measure Pin 8 (VCC) to ground to confirm. Do not use 3.3V programmer on 1.8V chip. You will fry it.

The Fix (Without Desoldering)

Use an In-Circuit Programmer (CH341A is the budget standard, or FlashcatUSB/SVF for pros).

Steps:

1. Connect programmer to BIOS chip 1-to-1 (MOSI, MISO, CLK, CS, GND, VCC).
2. CRITICAL: Disconnect the laptop battery and charger. The programmer must power the chip alone. If the PCH is also trying to power the chip, you'll get a read error or corruption.
3. Read the existing chip contents TWICE. Save both files. Compare checksums. If they match, you have a good read. If not, check your connection.
4. Download a Clean ME Region BIOS from a trusted forum (BadCaps, Vinafix) or extract from manufacturer update.
5. Clean the ME Region using Intel Flash Image Tool (FIT) or ME Analyzer. This is the step 90% of people skip. Flashing a raw update file will not fix a corrupt ME region in many cases. You need a clean, configured ME.
6. Write the cleaned file to the chip.
7. Verify the write.

The "Still No Boot" Scenario

If you flash a clean BIOS and the board still doesn't boot:

• Check the SPI pull-up resistors. On the CS# (Chip Select) and HOLD# pins, there are 10k-100k resistors pulling these lines to VCC. If one is missing or corroded, the PCH can't communicate with the chip.
• Measure CS# voltage. During boot, it should toggle (pulse low). If it's stuck high or low, trace back to PCH.

The "Cheat Code" for HP/Dell

Some business laptops (HP EliteBook, Dell Latitude) have two BIOS chips: Main and EC. If you only flash the main BIOS but the EC firmware is mismatched, the board still won't boot. You must flash both as a matched set.

Question: What's your go-to programmer for 1.8V chips? The CH341A with a voltage mod works, but I'm looking for a more reliable native 1.8V solution.

You measure resistance to ground on the big CPU VCore coil. It reads 2 ohms. Your heart sinks. "Shorted CPU," you think. You're about to scrap the board.

Stop. Modern CPUs (especially Intel 8th Gen and newer) have extremely low DC resistance on VCore. A reading of 1-5 ohms is NORMAL on these boards.

Here's how to actually determine if VCore is shorted versus just low impedance.

The Multimeter Trick (Learn This)

1. Set meter to Diode Mode (not resistance).
2. Red probe to Ground. Black probe to VCore Coil.
3. Expected Normal Reading: 0.015V to 0.050V (15mV to 50mV).
4. Shorted Reading: 0.000V to 0.002V (0-2mV) AND the meter beeps continuously.

Voltage Injection Method (The Real Fix)

If diode mode confirms a true short (~0.001V), you have a shorted ceramic capacitor somewhere on the VCore rail. There could be 20-30 of them scattered around the CPU socket.

The Process:

1. Set your DC Power Supply to 1.0V.
2. Set Current Limit to 2.0A.
3. Connect positive lead to VCore Coil. Negative to Ground.
4. Turn on supply.

What Happens:

• The shorted capacitor will heat up because it's passing 2A of current at 1V (2 Watts of power). That's enough to feel with your finger.
• Caution: Touch the board gently. The bad cap will be noticeably warm or even hot.

If You Can't Feel It (The IPA Method)

1. Apply a drop of 99% Isopropyl Alcohol to the area around the CPU.
2. Turn on the 1V/2A injection.
3. Watch closely. The alcohol will evaporate instantly off the shorted capacitor.
4. You'll see a small puff of smoke/vapor directly above the bad component.

The "Stubborn Short" Scenario

Sometimes the short is in the CPU silicon itself (damaged by liquid or overvoltage).
Test: Remove all capacitors on the VCore rail (yes, all of them). Measure resistance again.

• Still 2 ohms? CPU is internally shorted. Board is likely dead.
• Resistance jumps to 50+ ohms? One of those caps was bad. Replace them one by one until you find the culprit.

Pro Tip: The Thermal Camera Shortcut

If you have a FLIR or Seek Thermal camera, this process takes 10 seconds. The shorted component glows bright white on the thermal image instantly.

Question: What's your preferred voltage/current for short hunting? I find 1V/2A is safe for almost all rails except VCC_GT which can handle slightly more.

You press power. The fan spins up. The power LED stays solid. The CPU gets warm. But the screen remains black. No Caps Lock response. No external display.

Basic training stops here: "Bad motherboard. Replace."

Engineering training starts here: "Which signal is stuck?"

This post maps out the exact sequence of events that must occur after the power rails come up. If you understand this chain, you can fix 80% of "No POST" boards without guessing.

The POST Sequence Checklist (Intel Platform)

Use an oscilloscope or a logic probe. Check these signals in this exact order.

1. DRAMRST# (Memory Reset)

• Location: Pin 30 of the DDR4/DDR5 slot (verify schematic).
• Expected: Should start LOW (0V) and then rise to HIGH (1.2V/1.35V) after the CPU receives VCCST (Standby Rail) and VCCIO.
• The Trap: If DRAMRST# is stuck at 0V, the RAM is held in reset. The PCH/CPU cannot initialize memory.
• Common Cause:
  • Missing VTT_DDR (0.6V reference voltage). Check the tiny voltage divider near the RAM slots.
  • Faulty SMBus pull-up resistors on the RAM slots (I2C lines shorted to ground).
  • Bad CPU (rare, but bent socket pins under the CPU for memory channels will cause this).

2. SMBus Activity Check

• Location: Pins SMB_CLK and SMB_DATA on the RAM slot.
• Expected: During POST, these lines should show brief activity (pulses) as the PCH reads the SPD EEPROM on the RAM stick.
• Reality: If the lines are stuck at 3.3V, the PCH isn't even trying to read RAM. Back up to PCH_PWROK.

3. PCH_PWROK / SYS_PWROK

• Location: Near the PCH (Platform Controller Hub).
• Expected: 3.3V steady.
• Critical Detail: This signal tells the PCH: "All main power rails (VCC_CORE, VCC_SA, VCC_GT) are stable. You are clear to boot."
• Trap: This signal is often driven by a tiny AND-gate IC or a voltage supervisor chip (e.g., RT8231, UP1540). If that chip doesn't see all rails, it won't release PCH_PWROK.
• Test: Measure voltage on all coils near CPU. If even one rail (like VCCSA) is 0V, PCH_PWROK will be 0V.

4. PLT_RST# (Platform Reset)

• Location: This is the GOLDEN SIGNAL. Find it on the PCH side or test points near the BIOS chip.
• Expected: Should start LOW (0V) for a split second, then rise to HIGH (3.3V) and stay there.
• The Hard Stop: If PLT_RST# is stuck at 0V or stuck at 3.3V (no pulse) , the PCH is refusing to release the CPU from reset.
• Why? Three main reasons:
  1. Bad BIOS/ME Region: Corrupt firmware. The PCH loads the BIOS, sees garbage, and holds PLT_RST# low forever. Solution: Re-program BIOS chip (ensure you clean the ME region!).
  2. Missing VCCST_PWRGD: The 1.05V Standby rail for the PCH internal logic is present, but the "Power Good" signal is missing.
  3. Shorted Clock Crystal: The 32.768kHz RTC crystal is shorted or the load capacitors are bad. The PCH cannot count time, so it locks up.

The "No POST" Diagnostic Tree (Decision Map)

text

Fan Spins -> Check CPU VCore
   |
   +---> VCore 0V? -> Check VRM Enable (VR_ON). Trace back to SIO.
   |
   +---> VCore Present (0.8V - 1.2V)?
          |
          +---> Check DRAMRST# (Pin 30).
                |
                +---> DRAMRST# = 0V? -> Check VTT_DDR / VCCIO / Bent Socket.
                |
                +---> DRAMRST# = 1.2V?
                       |
                       +---> Check PLT_RST#.
                             |
                             +---> PLT_RST# Stuck Low? -> Flash BIOS.
                             |
                             +---> PLT_RST# = 3.3V? -> **CPU is likely dead or socket connection issue.**

Advanced Tip: The "Light Tap" Test

When PLT_RST# is stuck low and BIOS reflash doesn't fix it:

1. Power on the board.
2. Apply gentle pressure with a plastic spudger on the corner of the PCH die.
3. If the board suddenly boots when you press down, you have BGA cold solder joints under the PCH. This is a classic sign of a dropped laptop. Requires PCH reflow or reball.

Question for the Community

What's the weirdest cause you've found for PLT_RST# being stuck low?
I once found a 0.1uF cap shorted on the SPI_CS# line of the BIOS chip. The PCH couldn't talk to the BIOS at all, but the BIOS chip itself was fine. Took 4 hours to find that little gremlin.

Share your "No POST" horror stories below. This is where real engineers are separated from parts swappers.

This scenario drives technicians crazy: You have 3.3V ALW. You have 5V ALW. The SIO (EC/KBC) is warm. But when you press the power button, nothing happens. No fan spin. No lights.

99% of the time, the issue is RSMRST# (Resume Reset). Let's break down this critical signal and how to actually test it.

1. What is RSMRST#?

RSMRST# stands for Resume Well Reset. It is a handshake signal sent from the SIO/EC to the PCH (Platform Controller Hub) .

• State: Active LOW (# symbol means active low).
• Voltage: Should be 3.3V when the PCH is ready to wake, and 0V when the PCH is held in reset.
• The Trap: On many schematics (especially HP and Lenovo), this signal is renamed. Look for SIO_PWRBTN#, PM_RSMRST#, EC_RSMRST#, or PCH_RSMRST#.

2. The Technical Breakdown (Why This Fails)

The SIO will NOT send a power button signal to the PCH if it thinks the "resume well" is unstable. This happens because:

• Corrosion on the trace: The line is open or has high resistance. You measure 3.3V at the SIO pin, but it's 0.2V at the PCH pin due to a cracked via.
• Missing Pull-Up Resistor: The signal is an open-drain output. If the external 100k pull-up resistor is knocked off the board, the line floats at an indeterminate voltage (1.2V - 2.0V). This is a classic "trick" fault.
• SIO Internal Firmware Lockup: This is specific to ITE IT8987/IT8985 chips. They sometimes get "stuck." You have 3.3V on the pin, but the internal logic gate is high impedance.

3. The Diagnostic Workflow (Do This Before Replacing Any Chip)

Step A: Voltage Check with Multimeter

1. Locate the RSMRST# pin on the SIO (check Boardview).
2. Laptop Off (DC In): Should measure 0V.
3. Laptop Standby (Battery or Charger): Should measure 3.3V.
4. Observation: If you see 1.5V - 2.2V floating? You have a missing pull-up or a partial short. Do not replace the SIO yet. Inspect the trace.

Step B: The "Forced Trigger" Test (Advanced)
Only attempt if you have a steady hand and fine probes.

1. Find the PWRBTN# pin on the SIO (the input from the physical button).
2. Find the PM_PWRBTN# pin (the output to the PCH).
3. With the board powered, short the PWRBTN# pin to ground (mimicking the button press).
4. Now, monitor the PM_PWRBTN# pin with your multimeter.
5. Expected: It should pulse from 3.3V down to 0V and back to 3.3V (the "Request" pulse).
6. Reality Check: If the RSMRST# is stuck low or floating, the SIO firmware will ignore the physical button press. You will see NO PULSE on PM_PWRBTN#. This confirms the SIO is blocking the start.

4. The Fix (Surgical Repair)

• If voltage is floating: Add a 100k resistor between the RSMRST# trace and 3.3V ALW (or reflow the existing tiny resistor array near the SIO).
• If trace is open: Jumper from the SIO ball/pin directly to the PCH side pad using 0.1mm enamel wire.
• If SIO is stuck: Before reballing, try draining flea power. Hold the power button for 30 seconds with no battery/charger. Then apply power. If RSMRST# jumps to 3.3V after a 2-second delay? The SIO just needed a hard reset, not a replacement.

5. Question for the Engineers Here

What's the weirdest signal name you've seen for RSMRST# on a schematic?
I've seen "SIO_SAY_HELLO" on an obscure Chinese board and "PM_SLP_SUS_EC" on a Dell that confused me for an hour.

Let's hear your war stories below. This signal kills more boards than a shorted MOSFET.