EivoTech Laptop & Mobile Repair Master Course

Part 22 — Power On Then Off, Restart Loop aur Power Cycling Complete Mastery

Chapter 22: Laptop 1–5 Second ON Hoke OFF Ho Jaye To Fault Kahan Trace Karna Hai

Common complaints:

Power button press karo, fan spin karke band
LED 1 second on hoti hai phir off
Laptop 2–3 second ke loop mein restart hota rehta hai
CPU VCORE aati hai phir gayab
RAM rail aati hai phir drop
Laptop thori der ON reh kar sudden off
Adapter lagate hi auto power cycle
Battery par cycle, adapter par stable
Adapter par cycle, battery par stable
BIOS flash ke baad restart loop
RAM change ke baad loop
Power button chhorne ke baad bhi repeat start
Cold boot par cycle, warm par boot

Is fault ka golden rule:

Power cycle ko sirf “BIOS problem” mat samjho.

Pehle ye dekho:

Sequence kitni door ja rahi hai aur sabse pehle kaunsi rail/signal drop ho rahi hai.

1. Power Cycling Kya Hai?

Power cycling ka matlab:

Laptop power-on sequence start karta hai

↓

Kisi stage par condition fail hoti hai

↓

System shutdown/reset hota hai

↓

Firmware/EC dubara start try karta hai

↓

Same process repeat.

2. Timing Bohat Important Hai

Cycle kitni der ka hai?

Example:

0.5–1 second

Very early power-sequence fault possible.

2–5 seconds

RAM/CPU/firmware initialization possible.

10–30 seconds

Memory training/BIOS/boot retry possible.

Several minutes

Thermal/power instability possible.

Timing exact diagnosis nahi, lekin strong clue hai.

3. Fan Spin and Stop ka Matlab

Fan spin means:

Kuch power rails ON hui hain.

Lekin fan movement alone ye prove nahi karta ke:

CPU execute hua.

BIOS read hui.

RAM train hui.

POST hua.

4. Sabse Pehla Step

Fault ko repeat karke blindly observe mat karo.

Measurements plan karo:

Main B+

3VALW

5VALW

RAM rail

CPU VCORE

PGOOD

RSMRST#

PWRBTN#

SLP_S5#

SLP_S3#

PLTRST#

BIOS activity

5. Stable Rails vs Switched Rails

Important:

3VALW/5VALW standby rails cycle ke dauran stable reh sakti hain.

Lekin:

RAM

CPU

GPU

S0 rails

ON/OFF ho sakti hain.

Isliye har rail ka power state samjho.

6. Master Power-Cycle Flow

Adapter/Main B+ stable?

↓

3V/5V ALW stable?

↓

EC stable?

↓

RSMRST# stable?

↓

PWRBTN# event normal?

↓

SLP_S5# release?

↓

S5/S3 rails appear?

↓

SLP_S3# release?

↓

RAM rail appears?

↓

CPU VR_ON?

↓

VCORE appears?

↓

PGOOD?

↓

PLTRST#?

↓

BIOS activity?

↓

RAM training?

Jahan sequence toot kar wapas jaye, wahi primary diagnostic zone hai.

7. Main B+ Stable Hona Chahiye

Suppose:

Laptop ON attempt par main 19V rail 19V se 5V tak drop ho jati hai.

This is not normal firmware loop.

Possible:

Adapter weak.

Input MOSFET.

Heavy load/short.

Charging/power path.

8. Main B+ Stable, Secondary Rail Drops

Then input path likely okay.

Focus affected secondary regulator/sequence.

9. 3VALW Cycle ke Sath Drop Ho

This is serious early-stage issue.

Possible:

3V rail overload.

EC fault.

3V regulator protection.

Shared standby short.

10. 3VALW Stable but 5VALW Drops

Focus 5V branch.

Check:

5V output resistance.

Controller channel.

Downstream load.

Enable state.

11. Both ALW Stable

Good.

Power cycle later stage mein hai.

Move to:

EC/power sequence.

12. EC Reset Cycle Kar Raha Hai?

If EC reset repeatedly toggles:

Could explain whole loop.

Check:

EC supply stable?

Reset source?

Watchdog/firmware?

Input rail?

13. EC VCC Stable but System Cycle

Then EC itself may be commanding shutdown due to missing prerequisite.

Need observe outputs.

14. Power Button Stuck Low

Very important.

If PWRBTN# permanently low:

Platform may interpret long press.

Result:

Power on

then forced shutdown.

15. PWRBTN# Test

Idle:

HIGH expected in typical active-low design.

Press:

LOW.

Release:

HIGH.

If remains LOW after release:

Check:

Button switch.

Cable.

Pull-up.

EC/input line.

16. Stuck Power Button Symptoms

Possible:

Laptop starts and instantly shuts down.

Auto starts.

Won't stay on.

Long-press behavior.

17. Power Button Fine, Loop Continues

Move to sleep signals.

18. SLP_S5# Role

If SLP_S5# releases:

System is leaving deep-off state.

If it immediately drops again:

Platform cancelled power-on.

Need see what condition failed after S5 stage.

19. SLP_S3# Role

If SLP_S3# releases:

More system/S0 rails start.

If SLP_S3# never releases:

Fault before full run state.

20. SLP Signals Appear Then Drop

Important clue:

Platform itself may be requesting shutdown.

Possible reasons:

PGOOD failure.

RAM/firmware failure.

Protection.

EC command.

21. One Regulator PGOOD Missing

This can reset entire sequence.

Example:

1.8V output = correct.

PGOOD = LOW.

System may shut down.

Check:

Output stability.

PGOOD pull-up.

Controller.

22. PGOOD Chain

Think:

Rail A stable

↓

PGOOD A

↓

Enable Rail B

↓

PGOOD B

↓

ALL_SYS_PWRGD

↓

CPU/reset stage

A single broken PGOOD can stop all later stages.

23. Rail Appears for 0.5 Second

Multimeter may miss it.

Use:

Min/Max mode

Oscilloscope

where needed.

24. Oscilloscope Advantage

You can see:

Rail rise.

Drop timing.

PGOOD edge.

Enable transition.

This is very useful in power-cycle faults.

25. CPU VCORE Never Appears

Then check:

VR_ON.

If VR_ON also absent:

Problem CPU VR se pehle hai.

26. VR_ON Appears, VCORE Nahi

Focus:

CPU VR controller.

Power stage.

VCORE rail condition.

SVID/CPU requirements.

27. VCORE Appears then Drops

Sequence reached CPU stage.

Now check:

PGOOD.

PLTRST#.

BIOS activity.

RAM training.

28. VCORE Stable for 2 Seconds, Then Off

Could be:

Firmware timeout.

RAM training failure.

Missing PGOOD.

CPU/platform initialization fail.

29. VCORE Appears for Only Milliseconds

Could be:

VR protection.

Rail overload.

Power-stage issue.

Input collapse.

Need electrical check first.

30. VCORE Low Resistance = Short?

Again no.

CPU core rail naturally low resistance ho sakti hai.

Known-good comparison required.

31. RAM Rail Missing

Laptop may power cycle because memory cannot initialize.

Check:

DDR rail.

VTT.

VREF.

VPP if applicable.

Enable.

PGOOD.

32. RAM Rail Appears then Drops

Question:

Does it drop because:

Regulator fault?

whole system shutdown command?

Compare EN signal.

33. EN Drops Before Rail

If enable goes low first:

Controller intentionally shutting down.

Trace sequence/controller.

34. EN Stays High but Rail Collapses

Then regulator/output fault stronger.

Possible:

Overcurrent.

Short.

Controller.

Power stage.

35. This Distinction Bohat Important Hai

Enable drops first = command problem.

Output drops while enable stays = power-stage/load problem.

36. BIOS Activity in Power Cycle

If every cycle mein SPI activity:

Platform firmware read try kar raha hai.

Could be:

BIOS loop.

Memory initialization.

Firmware issue.

37. No BIOS Activity at All

Then cycle firmware execution se pehle ho sakti hai.

Check:

Reset.

Clock.

Power-good.

SPI supply.

38. BIOS Activity Then Reset

Possible:

Firmware crashes.

Memory training fails.

Platform watchdog.

Wrong BIOS.

39. Power Cycle after BIOS Update

Strong firmware clue if:

Before update laptop normal tha.

Hardware untouched.

Correct rails still present.

But verify:

Correct BIOS image?

Correct board revision?

EC firmware match?

40. Wrong BIOS and Power Cycle

Possible:

No POST.

Fan high.

Restart loop.

Battery/keyboard issues.

Correct firmware restore important.

41. RAM Training Loop

Common pattern:

Power on

↓

VCORE/RAM rails present

↓

Few seconds

↓

Reset

↓

Repeat

Known-good RAM test.

42. Memory Training after CMOS Reset

Some systems multiple power cycles perform kar sakte hain.

Especially:

DDR4/DDR5.

Do not interrupt too quickly if behavior matches normal training.

43. How to Distinguish Normal Training vs Fault

Normal:

Cycles limited.

Eventually boots.

Fault:

Indefinite repeated same loop.

No progression.

Error code may appear.

44. RAM Module Fault

Use:

Known-good compatible RAM.

One module.

Correct slot.

Test each slot.

45. One Slot Causes Loop, Other Boots

Focus:

Slot.

Channel.

Signal.

CPU memory controller connection.

46. Soldered RAM Power Cycle

Check:

RAM rails.

BIOS.

Training behavior.

Board revision.

Do not random heat chips.

47. CPU/PCH Fault and Cycle

If:

Power rails good.

Clock/reset good.

BIOS correct.

RAM known-good.

Still same cycle.

Then CPU/PCH/SoC deeper fault possible.

This is later-stage conclusion.

48. Thermal Shutdown vs Immediate Power Cycle

Thermal shutdown usually temperature rise ke baad.

Immediate cold boot cycle less likely thermal.

49. 1 Second Cold Shutdown

Focus:

Electrical sequence/protection.

Not thermal paste first.

50. 5 Minute Shutdown

Now thermal/power load issue possible.

Part 16 concepts apply.

51. Fan Full Speed Before Shutdown

Could be:

Thermal.

Sensor fault.

EC failsafe.

No POST.

Need temperature context.

52. Adapter Related Cycling

Laptop adapter par cycle but battery par stable.

Possible:

Adapter.

Adapter ID.

Charging input MOSFET.

Main rail noise.

Charger IC.

53. Battery Related Cycling

Battery par cycle, adapter par stable.

Possible:

Weak battery.

Battery voltage collapse.

Battery connector.

Battery path.

BMS.

54. Adapter + Battery Together Cycle

But each individually stable?

Possible:

Charging transition/power-path control.

Battery/charger communication.

Charging controller.

55. USB-C PD Cycling

USB-C charger repeatedly:

5V → disconnect → reconnect

Possible:

CC issue.

PD controller reset.

VBUS short.

Power-path fault.

Part 12 flow.

56. Adapter Current Limit

Weak/wrong adapter:

Laptop start attempt.

Current demand rise.

Adapter voltage collapse.

System resets.

Known-good correct wattage adapter important.

57. Input MOSFET High Resistance

MOSFET fully short nahi.

But under load voltage drop.

Symptoms:

Idle okay.

Power-on attempt main rail collapses.

Compare drain/source voltage under load.

58. Current Sense Resistor Fault

Open/high resistance:

System power path unstable.

Charging controller may misread current.

Could cause shutdown/cycling.

59. Shorted Secondary Rail

Example:

1.8V rail short.

Power button press:

Enable comes.

Rail tries.

Protection trips.

Whole sequence shuts down.

60. Secondary Rail Short Diagnosis

Power off.

Measure resistance.

Search net.

Disconnect removable devices.

Known-good compare.

No blind injection into sensitive rails.

61. Rail Overload Without Hard Short

Component may draw excessive current only when powered.

Symptoms:

Resistance looks normal.

Rail collapses under power.

Thermal clue + current behavior useful.

62. EC Shutdown Request

EC can shut system down due to:

Thermal fault.

Battery/power safety.

Power-good issue.

Firmware state.

Need trace board-specific shutdown/control signals.

63. EC Watchdog

If EC firmware malfunctions:

Watchdog reset loop possible.

But only after power/reset/firmware evidence.

64. PCH/SoC Watchdog

Firmware boot failure can trigger platform reset/retry.

Cycle timing may be regular.

65. PLTRST# Behavior

If PLTRST# never releases:

Loop before platform initialization.

If releases and then drops:

System reached later stage then reset.

Useful timing clue.

66. PLTRST# + BIOS Activity Together

Observe:

PLTRST# high

↓

BIOS activity

↓

reset

This suggests later-stage initialization/firmware issue.

67. RSMRST# Drops During Cycle

If RSMRST# itself falls:

Very early standby/platform reset occurs.

Check:

Standby power.

RTC.

PCH standby rail.

EC.

68. RSMRST# Stable but SLP Signals Cycle

Then early standby okay.

Issue in main power-up sequence.

69. 3VALW Stable, VCORE Cycles

This narrows fault significantly.

Input/standby good.

Focus CPU/RAM/firmware stage.

70. 3VALW Also Cycles

Then issue much earlier.

Do not jump to BIOS.

71. Measuring Sequence Order

Write:

t0: PWRBTN#

t1: SLP_S5#

t2: 1.8V

t3: RAM rail

t4: CPU_VRON

t5: VCORE

t6: PGOOD

t7: PLTRST#

t8: BIOS activity

Then find break.

72. Timing Table Example

Signal	Appears?	Drops?	Notes
3VALW	Yes	No	Stable
SLP_S5#	Yes	Yes	2 sec
RAM 1.2V	Yes	Yes	1.8 sec
VR_ON	Yes	Yes	1.5 sec
VCORE	Yes	Yes	1.2 sec
PLTRST#	No	—	Missing

This tells system PLTRST stage tak nahi pohancha.

73. Power Button Line Cycling?

If PWRBTN# spontaneously pulses:

Could be:

Button board.

EC.

Noise/corrosion.

Need check.

74. Lid Sensor and Cycling

Usually lid sensor display/sleep affect karta hai.

But certain firmware states can create power behavior.

Still not first suspect in immediate electrical loop.

75. Fan Tach Missing

Some systems may shut down if fan error critical.

More common after few seconds or with error message.

Exact model.

76. Temperature Sensor Invalid

EC fail-safe may:

Fan max.

Throttle.

Shutdown.

If cycle from cold boot, sensor input check where relevant.

77. CPU Heatsink Missing Test?

Do not run CPU without proper heatsink for normal diagnosis.

Modern CPU can heat very quickly.

Thermal assembly should be installed for stable tests.

78. dGPU Fault and Cycling

Dedicated GPU rail short or PGOOD failure can stop power sequence.

If board supports UMA variant or dGPU disable architecture, schematic helps isolate.

79. dGPU Rail Appears then Drops

Check:

GPU VR enable.

Output resistance.

PGOOD.

Whether GPU rail is required at that stage.

80. GPU VCORE Low Resistance

Like CPU:

Could be naturally low.

Known-good comparison.

81. GPU/CPU Random Reflow

Do not use reflow as diagnostic test.

Temporary effect can mislead and damage board.

82. Storage Device Causing Loop

Rare but possible:

Shorted SATA/NVMe device.

Remove storage device.

If cycle stops:

Storage/power branch.

83. Wi-Fi Card Causing Loop

Shorted M.2 WLAN card can pull 3.3V rail.

Remove card and compare.

84. USB Device Causing Loop

Shorted external USB device/port:

USB power switch fault.

Remove all external devices.

Inspect damaged ports.

85. Display Cable Causing Loop

Shorted panel/eDP cable can pull rail and prevent stable power.

Especially after screen repair.

Power off, disconnect panel cable, retest board if appropriate.

86. Keyboard/Touchpad Short

Liquid-damaged input devices can pull EC/I2C rail.

Disconnect peripherals systematically.

87. Minimum Configuration Test

For board diagnosis use only necessary supported components:

Motherboard.

Correct power source.

CPU/heatsink.

Required RAM.

Display not always necessary for POST clues.

Disconnect suspect optional devices.

88. Minimum Configuration ka Goal

Find:

Kya external peripheral loop cause kar raha?

89. Remove One Thing at a Time

Do not disconnect 10 things and then forget original state.

Document changes.

90. Power Cycle after Screen Replacement

Check first:

LCD/eDP connector.

Bent pins.

Fuse.

Cable short.

Panel compatibility.

91. Power Cycle after Keyboard Replacement

Check:

Ribbon orientation.

Connector short.

Wrong keyboard.

Power button ribbon.

92. Power Cycle after Battery Replacement

Check:

Correct battery.

Connector.

Battery voltage/path.

SMBus.

No internal battery work.

93. Power Cycle after Fan/Heatsink Service

Check:

Fan connector.

Thermal sensor.

Heatsink pressure.

Missing thermal pad.

But immediate 1-second loop may still be electrical connector issue.

94. Power Cycle after Board Cleaning

Check:

Liquid under BGA/connector.

Missing tiny parts.

Improperly seated connectors.

Residue/corrosion.

95. BIOS Battery/RTC and Power Cycle

After RTC reset some systems retrain RAM.

Could cycle temporarily.

But indefinite loop requires diagnosis.

96. EC Firmware Mismatch

Symptoms:

Power cycle.

Fan weird.

Keyboard/charging abnormal.

Could happen after wrong firmware.

Need exact EC/main BIOS pair.

97. BIOS Region Mismatch

Wrong ME/PSP/AGESA/platform data:

Boot loops possible.

Use correct board firmware and original data.

98. RAM SPD Issue

Module physically okay but SPD communication fail.

System can't read parameters.

Can cause training fail.

Known-good RAM easiest test.

99. DDR5 PMIC Fault

DDR5 module has on-module power management.

A bad module may cause:

No POST.

Training loop.

Known-good module test.

100. CPU Memory Controller Fault

If one channel consistently fails with known-good RAM and slot path okay:

CPU integrated memory controller possible.

101. BGA Connection Fault

Intermittent CPU/PCH/SoC connection can cause:

Cold boot loops.

Pressure/temperature-dependent behavior.

But diagnose only after external circuitry ruled out.

102. Cold Boot Loop, Warm Boot Works

Possible:

Marginal BGA.

Weak capacitor.

Power rail startup.

Crystal/clock startup.

But do not jump to BGA.

103. Warm Boot Fails, Cold Works

Possible:

Thermal IC fault.

VRM.

Clock.

Memory.

Component leakage.

Use temperature correlation.

104. Loop Only on Charger

Check adapter identification too.

Some systems may alter performance/power limits based on adapter ID.

105. Loop Only With Battery Installed

Disconnect battery.

If stable:

Battery path/pack.

Known-good battery.

No pack opening.

106. Main Rail Ripple

DC voltage average okay ho sakta hai.

But excessive ripple can reset regulators.

Oscilloscope useful.

107. 3V/5V Ripple

Standby controller weak caps/MOSFET can create instability.

Symptoms:

Random resets.

EC resets.

Power cycles.

108. Oscillator Startup Problem

Clock starts then dies.

Platform resets.

Advanced scope diagnosis.

109. EC Crystal Fault

If EC resets repeatedly:

Check EC clock/startup.

110. PCH Clock Fault

Could prevent PLTRST release and cause cycle.

111. PGOOD False Due to Noise

Rail average correct but PGOOD glitches.

Scope can catch short low pulses.

These can reset system.

112. Missing Pull-Up

PGOOD or reset line floats.

System intermittent/cycles.

Check schematic.

113. Cracked Resistor

Tiny resistor in enable/reset/PGOOD line can be mechanically cracked.

Looks normal visually.

Continuity/value check.

114. Corroded Via

Signal may show continuity sometimes and open under board flex.

Liquid-damage boards.

115. Power Cycle Diagnosis mein Thermal Camera

Useful for:

A secondary IC heating during each attempt.

Shorted power stage.

But cycle may be too brief.

Still supporting clue.

116. Current Draw Pattern

Bench input current waveform can help:

Low → pulse → drop.

High immediate → short/overload.

But exact current numbers board-specific.

117. Don't Memorize Current Numbers

One gaming laptop and one ultrabook completely different.

Look for pattern, not universal amperage.

118. Current Pulse + VCORE Pulse

Sequence reaches CPU.

No need recheck DC jack repeatedly.

119. No Current Increase After Button

Power request not progressing.

Check:

PWRBTN#.

RSMRST#.

SLP signals.

120. Power Cycling Diagnostic Worksheet

Laptop Model: __________

Board Number: __________

Cycle Time: __________

Main B+: __________

3VALW: __________

5VALW: __________

EC VCC: __________

RSMRST#: __________

PWRBTN#: __________

SLP_S5#: __________

SLP_S3#: __________

RAM Rail: __________

CPU VR_ON: __________

VCORE: __________

VR PGOOD: __________

ALL_SYS_PWRGD: __________

PLTRST#: __________

BIOS VCC: __________

BIOS Activity: __________

Known-Good RAM: __________

Cycle Stops With SSD Removed: __________

Cycle Stops With WLAN Removed: __________

Final Missing Stage: __________

121. Case Study 1 — 1-Second Loop

3VALW stable.

PWRBTN# correct.

SLP_S5# releases.

RAM rail appears.

VR_ON absent.

Then SLP signals drop.

Focus:

Pre-CPU VR sequence/prerequisite.

122. Case Study 2 — VCORE Appears then Drops

VR_ON present.

VCORE stable for 1 second.

PLTRST# never releases.

Check:

PGOOD chain.

Clock/reset.

PCH/SoC.

123. Case Study 3 — BIOS Activity Then Reset

SPI access every cycle.

Known-good RAM still loop.

Correct power rails.

Fault started after BIOS update.

Strong firmware direction.

124. Case Study 4 — One RAM Module Fixes Loop

Two-module configuration loops.

Each module alone test.

One specific module fails.

RAM fault.

125. Case Study 5 — Any RAM in Slot B Causes Loop

Slot A always boots.

Slot B loops.

Focus:

Slot B power/signals/channel.

126. Case Study 6 — Main Rail Drops Under Load

Adapter 19.5V no-load.

Power-on attempt main rail falls dramatically.

Known-good adapter same.

Check:

Input MOSFET high resistance.

Main-rail overload.

127. Case Study 7 — EN Stays High, 1.8V Collapses

Strong regulator/output fault direction.

Check short/load/power stage.

128. Case Study 8 — EN Goes Low Before 1.8V Drops

System/controller intentionally shutting it down.

Trace reason upstream.

129. Case Study 9 — Laptop Cycles Only With SSD Installed

Remove NVMe:

Board stays on.

Known-good NVMe boots.

Original NVMe fault/short likely.

130. Case Study 10 — Loop after Screen Replacement

Disconnect internal display cable with all power removed.

Board now reaches POST/external output.

Inspect eDP connector/cable/panel branch.

131. Case Study 11 — Fan 100%, 5-Second Loop after Wrong BIOS

Hardware rails okay.

Correct firmware restores normal sequence.

132. Case Study 12 — Power Button Stuck

PWRBTN# remains low after button release.

Laptop powers then shuts down.

Button board replacement fixes.

133. Case Study 13 — 3VALW Cycles

Main B+ stable.

3V controller EN remains high.

3V output rises then collapses.

3V rail resistance abnormal.

Find overloaded/shorted 3V branch.

134. Case Study 14 — 3VALW Stable, 5VALW Missing

Laptop attempts boot and shuts down.

5V rail required for next stage.

Diagnose 5V regulator channel.

135. Case Study 15 — Cycle Only on Battery

Known-good battery stable.

Original battery voltage collapses under load.

Battery replacement, no internal pack work.

136. Case Study 16 — Cycle Only With Wi-Fi Card

Card removed:

Boot normal.

Known-good compatible card works.

Original WLAN card short/fault.

137. Case Study 17 — Cold Boot Cycles Twice Then Boots

Could be normal memory training after reset if limited and consistent.

Check model behavior before declaring fault.

138. Case Study 18 — Cycles Forever Every 3 Seconds

No progress.

Known-good RAM.

BIOS activity repeats.

Needs deeper firmware/RAM/CPU analysis.

139. Case Study 19 — Laptop Runs 10 Minutes then Cycles

Temperature reaches critical.

Fan not spinning.

Thermal shutdown, not early power-sequence loop.

140. Case Study 20 — Laptop Randomly Restarts Under Load

Possible:

Power rail instability.

Adapter.

VRM.

Thermal.

RAM.

Not same as cold-start 1-second loop.

141. Power Cycle Quick Decision Tree

Main B+ stable?

NO → input/power path.

3V/5V stable?

NO → standby regulator/load.

RSMRST# stable?

NO → RTC/standby/platform.

SLP signals release?

NO → EC/PCH/firmware.

RAM rail present?

NO → memory power.

VR_ON present?

NO → sequence prerequisite.

VCORE present?

NO → CPU VR.

PGOOD present?

NO → regulator/power stability.

PLTRST# released?

NO → reset/clock/PGOOD.

BIOS activity?

NO → SPI/platform.

BIOS activity + loop?

RAM/firmware/CPU deeper diagnosis.

142. 1-Second Loop Quick Flow

3VALW stable?

↓

SLP_S5#?

↓

RAM rail?

↓

VR_ON?

↓

VCORE?

↓

PGOOD?

Usually one of these first missing points gives direction.

143. 3–5 Second Loop Quick Flow

Power rails mostly appear.

Focus:

RAM training.

BIOS.

Reset.

CPU initialization.

144. Long Loop Quick Flow

10+ seconds:

Firmware retry.

Memory training.

Boot-device behavior.

Thermal if much longer.

145. Peripheral Isolation Checklist

Power removed.

Then where relevant test without:

SSD.

Wi-Fi card.

Touchpad.

Keyboard.

Webcam cable.

Internal display.

Optional daughterboards.

One at a time.

146. Don't Disconnect Required Hardware

Some laptops need:

Required RAM.

Specific daughterboard.

Power-button board.

Do not remove critical components and misinterpret behavior.

147. Repair ke Baad Verification

After cycle fixed:

Cold boot 5–10 times.

Restart.

Shutdown/start.

Battery boot.

Adapter boot.

Sleep/wake.

Load test.

148. Intermittent Cycle Repair

If board boots once:

Don't return immediately.

Intermittent faults need repeated testing.

149. Flex Test

Normal gentle motherboard/chassis handling only.

Do not physically bend powered board to “find BGA fault.”

150. Heat Test Caution

Do not randomly heat CPU/PCH/GPU to see if it boots.

This can damage board and hide the real fault.

151. Power Cycle Golden Rules

1. Cycle timing note karo.

2. Stable aur switched rails ko separate samjho.

3. Sabse pehli rail/signal jo drop hoti hai usko identify karo.

4. Enable pehle drop ho to upstream command issue.

5. Enable stable ho aur output collapse ho to regulator/load issue.

6. VCORE appears = sequence CPU stage tak pohanchi.

7. BIOS activity = firmware access attempt ka clue.

8. RAM training repeated cycles create kar sakti hai.

9. Optional peripherals bhi shared rails short kar sakte hain.

10. Random BIOS flash, BGA heat aur blind rail injection avoid karo.

152. Part 22 Quick Revision

Power Cycle

Repeated ON/OFF startup attempt.

Cycle Timing

Fault stage ka clue.

Stable Rail

Cycle ke bawajood present rehne wali rail.

Switched Rail

Power-state dependent rail.

PGOOD

Regulator stable-output confirmation.

VR_ON

CPU voltage regulator enable.

VCORE

CPU core voltage.

PLTRST#

Platform reset.

RAM Training

Memory initialization/calibration.

Watchdog

System reset mechanism if execution hangs.

Enable vs Output

Power fault aur command fault separate karne ka key method.

153. Part 22 ka Sabse Important Lesson

Laptop:

ON → OFF → ON → OFF

kar raha ho to ye mat socho:

“BIOS kar dete hain.”

Is route ko follow karo:

Main B+

↓

3V/5V ALW

↓

RSMRST#

↓

SLP Signals

↓

RAM Rail

↓

CPU VR_ON

↓

VCORE

↓

PGOOD

↓

PLTRST#

↓

BIOS Activity

↓

RAM Training

Aur har signal ke liye do sawal:

Kya ye signal/rail aayi?

Agar aayi to sabse pehle kab aur kyun gayi?

Ye method power cycling ko guesswork se nikal kar:

timing-based fault diagnosis

bana deta hai.

Part 22 Complete

Next — Part 23: Laptop Charging Fault Complete Master Workflow

Part 23 mein hum real charging complaints ko complete practical flow mein diagnose karenge:

Adapter connected but charging nahi.

Battery detected but not charging.

Plugged in not charging.

Adapter unknown.

Charging LED blink.

Battery percentage stuck.

Battery charges only when laptop off.

Laptop works on charger but battery doesn't charge.

Charging current low.

Charging MOSFETs.

ACDET.

ACOK.

ACDRV.

CMSRC.

SRP/SRN.

BATDRV.

Current-sense resistor.

Battery SMBus.

Dell/HP adapter ID.

USB-C PD charging.

Aur complete EivoTech Professional Charging Fault Checklist.