Thermal Provocation — Forcing Heat- and Cold-Dependent Faults

Section Overview

The thermal intermittent is the class that answers to temperature, and this section turns its failure window into a summons — recreating the heat or cold on demand instead of waiting for it (why-intermittents-are-the-hardest-faults). The history names the direction. A warm-up fault appears after the device has run and heated — the die-after-an-hour amplifier — while a cold fault appears from a cold start and clears as things warm, and each points its own way: summon one with heat, the other with cold. The summons starts global. A thermal soak — running the device warm in its own case, the way its owner does, to a known temperature — or a controlled chill recreating the cold morning, brings the whole device into its window with an instrumented observable armed throughout (capturing-transients-and-single-shot-events). Then the provocation narrows. Once the fault answers reliably, directed heat and freeze spray shrink the area — whole device, then zone, then component — until the smallest area that still summons the fault contains it (freeze-spray-and-localized-heat-for-isolation). Discipline keeps it honest and safe. Heating stays gentle and inside component ratings; condensation — the moisture film a chilled board pulls from the air — is respected, because a wet board invents leakage faults and corrodes, so bulk chilling happens power-off where possible and boards dry before conclusions. And the recipe proves the repair. A warm-up fault is verified hot and a cold fault cold — the repair is proven at the temperatures that once summoned it, run enough times to beat the fault's own rate. Read the window's direction, soak or chill globally, narrow to the component, respect the ratings and the dew, and verify at temperature — and the thermal intermittent performs on your schedule.

Why This Matters

Thermal intermittents are among the most common of all — cracked joints that open with expansion, semiconductors that drift with heat, capacitors that fade when cold — and they are also the most summonable, which makes this the campaign's highest-yield provocation (why-intermittents-are-the-hardest-faults). This matters because waiting for temperature wastes days: a fault that needs an hour of warm-up appears in minutes under a deliberate soak, and a cold-morning fault stops needing a morning. This matters because direction decides the technique: warming a cold fault or chilling a warm-up fault pushes the device away from its window and proves nothing, so misreading the history costs the whole session. It matters because the narrowing is the localisation: each round of directed heat or cold that still summons the fault shrinks the suspect area, so the provocation itself walks from "the device" to "this joint" (freeze-spray-and-localized-heat-for-isolation). It matters because careless thermal work creates faults: overheating stresses good parts toward failure, and a condensation-wet board leaks, corrodes, and fails in ways the original complaint never did — evidence contaminated by the test. And it matters because repairs verified cold come back: a warm-up fault fixed and tested only on a cool bench was never tested at all, and the device returns with the same complaint (capturing-transients-and-single-shot-events). Master the thermal summons, and the largest class of intermittents becomes routine work.

Required Prerequisites

Why Intermittents Are the Hardest Faults — Section 9.1 built the failure window and the reproduction recipe; this section executes them for the thermal class.
Freeze Spray and Localized Heat for Isolation — Section 6.5 taught cold and heat as part-level active probes with their handling precautions; this section scales the same tools up to summoning a hidden fault and back down to naming its component.

Recommended Consumables

Freeze spray with a straw nozzle — to chill zones and single components during the narrowing (freeze-spray-and-localized-heat-for-isolation)
A notebook or worksheet — to record temperatures, soak times, and what each round did or did not summon
Card or masking to shield neighbours — to keep directed cold and heat on the intended zone
Lint-free wipes and patience — to dry a condensation-wet board fully before re-powering
A thermocouple or stick-on temperature indicator — to know the actual temperature instead of guessing

Recommended Practice Hardware

A device with a known thermal intermittent — to practise the full summons-narrow-verify cycle (why-intermittents-are-the-hardest-faults)
A gentle heat source — hair dryer or hot-air tool on low — to soak and zone-warm without exceeding ratings
A thermal camera or IR thermometer — to watch soak temperature and find the zones you actually heated (thermal-imaging-and-camera-technique)
A scope with single mode and persistence, or a logging meter — to arm as the observable through every thermal run (capturing-transients-and-single-shot-events)
A sacrificial board — to practise spray and heat handling before touching a customer's device
A notebook of thermal recipes — to build soak times and temperatures that worked, per device family

Real-World Applications

The thermal summons is a daily tool on a working bench. A technician with a die-after-an-hour amplifier soaks it in its own case at its working temperature and has the fault on the bench in twenty minutes — with a tripwire trigger already armed on the rail when it dies (capturing-transients-and-single-shot-events). A repairer facing a won't-start-cold monitor chills it power-off, powers it cold, watches it fail, and then warms zones one at a time until the failure clears — the zone that clears it contains the fault. Someone narrowing a summoned warm-up fault lets the device reach its window, then walks freeze spray component by component until one joint snaps the fault away — the classic isolation from thermal diagnostics, now aimed by a recipe (freeze-spray-and-localized-heat-for-isolation). A technician who bulk-chilled a board sees a new leakage-flavoured misbehaviour, recognises the condensation film, and dries the board fully instead of chasing a fault the test invented (why-intermittents-are-the-hardest-faults). And a bench proving a repair re-runs the soak recipe hot, three times the fault's old interval, and files the silent runs as the verification. The failures this prevents: days lost waiting for a warm-up that a soak delivers in minutes, a session wasted pushing the device away from its window, evidence contaminated by a wet board, and a "repaired" warm-up fault shipped after testing only cold.

Common Challenges

Knowing the real temperature. A soak without a measurement is a guess, and "warm" spans fifty degrees — the difficulty is anchoring the window to numbers with a thermocouple, indicator, or camera so the recipe is repeatable (thermal-imaging-and-camera-technique).
Gradients that overshoot. Freeze spray hits tens of degrees below zero instantly and a heat gun's core is far hotter than any rating — the difficulty is delivering direction without violence: distance, motion, low settings, and short bursts.
Faults that need heat and something else. Some windows are thermal plus load, or thermal plus flex — the difficulty is recognising when temperature alone will not summon, and combining provocations instead of abandoning the class (why-intermittents-are-the-hardest-faults).

Safety Notes

Risk Level: Medium. Deliberate heating and chilling of powered equipment adds burn, damage, and moisture hazards to the standing live-work discipline.

Deliberate temperature work is live work plus burns, cold, and moisture — keep it gentle, measured, and dry

Thermal provocation runs powered boards while hands and tools move around them, so all live-work discipline holds — and the heat source adds its own rules: low settings, constant motion, distance, and never dwelling on one spot, because a heat gun's core exceeds every component rating and melts plastics in seconds (freeze-spray-and-localized-heat-for-isolation). Freeze spray causes cold burns on skin and cracks cold-sensitive parts — keep it off displays, wet electrolytics sparingly, and never spray toward your face or a fan that will throw it back. Chilling a board below the room's dew point grows a condensation film: bulk-chill with power off wherever the window allows, treat a wet board as unpowerable until fully dry, and remember that moisture plus voltage means electrochemical migration — dendrites growing between powered conductors — and corrosion, not just wrong readings (why-intermittents-are-the-hardest-faults). Many freeze sprays are also flammable — keep them away from the heat sources this section employs in the same session. Soaks are standing watches: current-limit or fuse the supply, keep flammables away from warm enclosures, and never leave a deliberately heated faulty device unattended (capturing-transients-and-single-shot-events). The takeaway: temperature is a probe, not a weapon — gentle, measured, moving, and dry.

Professional Tips Before Starting

Measure the window before recreating it. Ask the history what temperature the fault lives at, then anchor it with a thermometer — a recipe with numbers is repeatable; "pretty warm" is not (thermal-imaging-and-camera-technique).
Arm the observable before the soak. The fault may appear early — the tripwire or logger goes live before the temperature starts moving (capturing-transients-and-single-shot-events).
Let temperature settle before judging. Boards lag the air around them — give each round a settling pause, or the response you read belongs to the previous round.

The Thermal Summons — Soak, Chill, Narrow, and Prove

Recap and Frame

Section 9.1 turned the intermittent problem into windows and recipes; this section executes the recipe for the largest class — the fault that answers to temperature (why-intermittents-are-the-hardest-faults). The mechanisms are familiar. Expansion opens hairline cracks in joints and traces, semiconductor parameters drift with heat, and aged capacitors lose capacity when cold — ordinary unfinished failures pushed over the line by temperature. The tools are familiar too. Freeze spray and localized heating were thermal diagnostics' active probes for a fault already showing; here they scale up to summon a hidden fault and back down to name its component (freeze-spray-and-localized-heat-for-isolation). The strategy is global-then-narrow. A hidden fault is summoned with the whole device in its window — soak or chill — because the fault's location is unknown; only after it answers reliably does the provocation shrink toward zones and parts. The observable is armed throughout. Every thermal run happens under an instrumented witness — a tripwire, persistence, or a logger — because the summons is worthless if the appearance passes unseen (capturing-transients-and-single-shot-events). And temperature is measured, not guessed. Soak temperatures, spray targets, and the window's numbers are read with a thermometer or camera so the recipe repeats tomorrow what it did today (thermal-imaging-and-camera-technique). Hold the frame — familiar mechanisms, scaled tools, global-then-narrow, witnessed and measured — and the thermal class becomes the easiest intermittent to drag into the open.

Reading the Thermal Window — Warm-Up and Cold Faults

The history tells you which direction to push, and getting the direction right is the whole first move (why-intermittents-are-the-hardest-faults). The warm-up fault appears with heat. A device that fails after minutes or hours of running, fails sooner in summer or in a cabinet, and recovers after a rest is describing a fault that its own operating heat summons — the classic die-after-an-hour pattern. The cold fault appears without it. A device that fails from a cold start — the won't-start-cold monitor, the radio that distorts until the room warms — and clears as it runs is describing a fault that heat heals and cold summons. Some windows are bands. A fault may live only between temperatures — fine cold, fine hot, faulty in between — which the history shows as failures in mild conditions and health at the extremes, and which the soak must target rather than overshoot. The direction picks the provocation. Warm-up faults are summoned by soaking toward operating-hot; cold faults by chilling toward the cold morning; pushing the wrong way moves the device out of its window and reads as a false acquittal. Numbers anchor the window. "Fails when warm" becomes usable when the history's conditions — enclosed case, summer room, an hour of load — are translated to a target temperature and confirmed with a measurement during the first successful summons (thermal-imaging-and-camera-technique). Warm-up or cold or a band between, direction picking the push, and the window anchored to measured numbers — and the thermal window is read. Get the direction and the number from the history, and the summons is half done.

The Global Summons — Thermal Soak and Controlled Chill

A hidden fault is summoned with the whole device in its window, because before the first appearance nobody knows where to point a spray can (why-intermittents-are-the-hardest-faults). The soak recreates the owner's heat. The gentlest soak is the device's own: run it in its case, under its working load, the way its owner does — the bench habit of running boards open and idle is exactly what was hiding the fault. Assistance stays gentle and measured. When the device's own heat is not enough or too slow, a warm environment or a hair dryer at distance on low raises the soak — with the temperature watched, kept inside every rating, and never delivered as a blast (thermal-imaging-and-camera-technique). The chill recreates the cold morning. A cold fault is summoned by cooling the whole device power-off — a cold room, an unheated space, or careful refrigeration in a sealed bag with a desiccant pack — then powering it cold and watching the failure that the owner sees at breakfast, remembering that the condensation film forms the moment the cold board meets room air, bag or not. The observable is armed before temperature moves. A tripwire on the suspect rail, persistence on the accused line, or a logger on the symptom goes live before the soak or chill begins, so the first appearance is captured, not just noticed (capturing-transients-and-single-shot-events). The summons is repeated before it is trusted. One appearance under soak is an anecdote; the same appearance on the next two runs makes a recipe — temperature, time, and load recorded — that the narrowing can lean on. The owner's own heat first, gentle assistance measured, the cold morning recreated power-off, the witness armed early, and the summons repeated into a recipe — and the fault now performs on schedule. Bring the whole device into its window with the instruments watching, and the hidden fault stops hiding.

The Narrowing — From Device to Zone to Component

Once the fault answers the global summons reliably, the provocation becomes the localiser (freeze-spray-and-localized-heat-for-isolation). The logic is opposition or restriction. With the device summoned into its faulty state, cold applied to the right spot clears a warm-up fault — and where clearing it worked, the fault lives; alternatively, from the healthy state, directed warming of one zone at a time finds the zone whose heating alone summons it. Zones come before components. A palm-sized area — this regulator corner, that amplifier block — is chilled or warmed as a unit first, because zone-level rounds are fast and each one halves the search the way divide-and-conquer always has. Components finish the walk. Inside the guilty zone, the straw nozzle and shielding card bring the spray or heat to one part at a time — the part-level isolation taught in thermal diagnostics, now aimed by everything the narrowing learned (freeze-spray-and-localized-heat-for-isolation). Settling time keeps rounds honest. Boards lag the air and neighbours share heat, so each round gets a pause before judging, and a response is confirmed by reversing it — clear it with cold, let it return with warmth, clear it again. The shrinking recipe is the evidence. Each smaller area that still summons or clears the fault updates the recipe, and the final version — this joint, this temperature, this response — is the diagnosis in recipe form (why-intermittents-are-the-hardest-faults). Oppose or restrict, zones then components, settled and confirmed by reversal, with the recipe shrinking to a name — and the narrowing is done. Let the provocation walk from the device to the part, and the localisation comes free with the summons.

The Discipline — Ratings, Gradients, and the Dew Point

Thermal provocation earns its keep only if it leaves the evidence and the board no worse than it found them (freeze-spray-and-localized-heat-for-isolation). Heat stays inside the ratings. Consumer parts live within rated limits that a heat gun's core exceeds several times over, so assistance heating means low settings, distance, constant motion, and target temperatures watched with a camera or thermocouple — a soak raises a device by tens of degrees, never hundreds (thermal-imaging-and-camera-technique). Cold respects the fragile. Freeze spray lands far below freezing on contact — enough to cold-burn skin, crack displays and glass parts, and stress ceramics with thermal shock — so bursts stay short, displays stay off-limits, and the straw and shield keep the cold on the suspect. The dew point is the hidden hazard. Any surface chilled below the air's dew point grows a moisture film, and on a powered board that film is a new circuit — leakage paths that invent faults, readings that mislead, and with voltage present, corrosion and electrochemical migration that do lasting damage. Condensation has a protocol. Bulk chilling happens power-off wherever the window allows, a chilled board is powered only for the observation the recipe needs, and a visibly wet board is unpowerable until fully dry — patience or gentle airflow, and drying confirmed before any conclusion is drawn from its behaviour (why-intermittents-are-the-hardest-faults). Contaminated evidence is discarded. Behaviour first seen on a wet board is attributed to the water until reproduced dry, because a test that invents faults has stopped being a test. Ratings respected, gradients gentle, the dew point watched, wet boards unpowered and dried, and wet evidence quarantined — and the discipline holds. Provoke without damage and conclude without contamination, and temperature stays a probe.

The Proof — Verifying Across the Thermal Window

The thermal recipe's second job is the one that keeps devices from coming back: proving the repair at the temperatures that used to break it (why-intermittents-are-the-hardest-faults). A cool-bench test of a warm fault is no test. The repaired die-after-an-hour amplifier that runs for ten cool minutes has demonstrated nothing — the fault never lived at bench temperature, so the verification must go where the fault lived. The proof re-runs the summons. The same soak or chill, the same load, the same measured temperature, with the same armed observable — run against the repaired device, and the fault's silence under the conditions that reliably summoned it is the evidence (capturing-transients-and-single-shot-events). Repetition beats the fault's own rate. A summons that worked every time needs a few silent runs; one that worked two times in three needs more — the count is chosen to beat the old rate and recorded, not guessed. The whole window gets covered. A repair that moved parts can shift a window rather than close it, so verification sweeps the band — cold start, warm soak, and the transitions between — before the recipe is declared dead. The recipe files with the repair. Temperatures, soak times, loads, and the verification count go into the record, because the next device of this family with this complaint starts from a proven recipe instead of a fresh window hunt. Verified where the fault lived, by the summons that proved it, repeated past the old rate, across the whole band, and filed — and the repair is proven, not presumed. Prove it hot if it broke hot and cold if it broke cold, and the thermal intermittent stays fixed.

Common Mistakes

Pushing the wrong direction. Warming a cold fault or chilling a warm-up fault moves the device out of its window and reads as health — take the direction from the history before the first run (why-intermittents-are-the-hardest-faults).
Soaking without a measurement. "Pretty warm" is not a recipe — anchor soaks and windows to numbers with a thermometer, indicator, or camera (thermal-imaging-and-camera-technique).
Running thermal rounds unwitnessed. An appearance nobody captured teaches nothing — arm the tripwire, persistence, or logger before temperature moves (capturing-transients-and-single-shot-events).
Blasting instead of soaking. A heat gun dwell or a long spray delivers damage, not diagnosis — low, distant, moving, and short, inside the ratings.
Trusting a wet board. A condensation film invents leakage faults and corrodes under power — bulk-chill power-off, dry fully, and reproduce any wet finding on a dry board before believing it.

Troubleshooting Guidance

The thermal campaign runs direction, summons, narrowing, discipline, proof. If the history says it fails warm: soak it — its own case, its own load, gentle assistance if needed — with the observable armed (capturing-transients-and-single-shot-events). If the history says it fails cold: chill it whole and power-off where possible, then power it cold and watch the owner's morning failure. If the soak or chill stays quiet: check the numbers — measure what temperature you actually reached against the window, and extend or adjust before abandoning the class (thermal-imaging-and-camera-technique). If temperature alone will not summon: combine provocations — the window may be thermal plus load or thermal plus flex, so add the second condition from the history (why-intermittents-are-the-hardest-faults). If the fault answers reliably: narrow — zones first with directed warmth or cold, then components with the straw and shield, confirming each response by reversing it (freeze-spray-and-localized-heat-for-isolation). If a chilled board misbehaves in a new way: suspect condensation — dry fully and reproduce the finding dry before chasing it. If the response shifts with each round: give settling time — boards lag the air, and unsettled rounds read the previous round's temperature. If the repair is in: verify at temperature — the same summons, repeated past the fault's old rate, across the window's whole band, and filed with the repair. The throughline: push the direction the history names, witness every run, narrow by opposition, keep it gentle and dry, and prove the fix where the fault lived.

Verification & Testing Methods

Confirm the thermal campaign was method, not weather:

[ ] I read the thermal window's direction from the history — warm-up fault, cold fault, or a band — and anchored it to a measured temperature rather than a guess.
[ ] I summoned globally first: a thermal soak in the device's own case and load, or a power-off chill for a cold fault, with the observable armed before temperature moved, and I repeated the summons until it was a recipe.
[ ] I narrowed by provocation — zones, then components, with settling time and each response confirmed by reversal — until the smallest area that still summoned or cleared the fault named the suspect.
[ ] I kept the discipline: heat low, distant, and moving inside component ratings; spray short, shielded, and off displays; bulk chilling power-off; and any condensation-wet board unpowered, dried fully, and its wet-board behaviour quarantined until reproduced dry.
[ ] I proved the repair across the thermal window — the same measured summons, repeated enough to beat the fault's old rate, cold start through warm soak — and filed the recipe, temperatures, and verification count with the repair.

Then try the practice exercises below — hands-on thermal work; scenarios differ from the quiz.

Practice Exercises

Anchor a soak to numbers (5 minutes, hands-on). Run a healthy device in its case under load with a thermocouple or thermal camera watching, and record how long it takes to reach steady temperature and what that number is — the baseline every soak recipe needs (thermal-imaging-and-camera-technique).
Read the direction, then summon with a witnessed soak (5 minutes, hands-on). From the device's fault history — real or given — state the direction first: warm-up, cold, or a band, and why that justifies soaking rather than chilling; then, on a practice device with a thermal intermittent — or a healthy one standing in — arm a tripwire or logger, soak toward the window, and note exactly when the observable would have caught the appearance (capturing-transients-and-single-shot-events).
Narrow by zones and reversal, then plan the proof (5 minutes, hands-on). On a warm board, chill one palm-sized zone at a time through a shield card, give each round settling time, and practise confirming a response by reversing it — clear, return, clear again; then write the verification plan the eventual repair would need: the same summons at the measured temperature, a run count that beats the fault's old rate, and the band to sweep (freeze-spray-and-localized-heat-for-isolation).
See the dew point at work (3 minutes, hands-on). Chill a small unpowered scrap board below room dew point, watch the condensation film form, then dry it fully and confirm with a close look — the protocol rehearsed where a mistake costs nothing.

These core steps — reading the window's direction, the witnessed global summons, the zone-to-component narrowing, the ratings-and-dew discipline, and verification at temperature — are tested in the Chapter Quiz at the end of this chapter, where a score of 80% is required to continue.

Key Takeaways

The history names the direction: a warm-up fault fails after running and recovers after rest, a cold fault fails from a cold start and clears warm, and some windows are bands — pushing the wrong direction moves the device out of its window and reads as false health (why-intermittents-are-the-hardest-faults).
A hidden thermal fault is summoned globally first — a thermal soak in the device's own case and load, or a power-off chill recreating the cold morning — with the observable armed before temperature moves, and the summons repeated until it is a recipe with measured numbers (capturing-transients-and-single-shot-events).
The narrowing is the localisation: zones then components, chilled or warmed through a straw and shield, with settling time and every response confirmed by reversal — the smallest area that still summons or clears the fault contains it (freeze-spray-and-localized-heat-for-isolation).
The discipline protects board and evidence alike: heat low, distant, moving, and inside ratings; spray short and off the fragile; and condensation respected — bulk chilling power-off, wet boards unpowered and dried, and wet-board behaviour quarantined until reproduced dry.
The repair is proven where the fault lived: the same measured summons re-run against the fix, repeated enough to beat the fault's old rate, swept across the window's band, and filed as the device family's recipe.

Skills Learned

You can now read a fault history for its thermal window — warm-up faults, cold faults, and the temperatures that define them.
You can now summon a thermal intermittent globally with a thermal soak or a controlled chill, observable armed.
You can now narrow a summoned fault from the whole device to a zone to a component with directed heat and cold.
You can now keep thermal provocation safe and honest — component ratings, gentle gradients, and condensation discipline.
You can now prove a repair across the thermal window, verifying at the temperatures that once summoned the fault.

Glossary Additions

thermal soak — running a device at a target temperature for long enough that the whole assembly reaches and holds it, used in intermittent diagnosis to summon heat-dependent faults on demand. The gentlest soak is the device's own operating heat — run in its case, under its working load, the way its owner uses it — with a warm environment or a distant, low heat source as measured assistance when needed; the temperature is read with a thermocouple, indicator, or thermal camera rather than guessed, because a soak with numbers is a repeatable recipe. A soak is run with an instrumented observable armed from the start, and its result — temperature, time, load, and whether the fault appeared — is recorded whether it summons the fault or stays quiet.
warm-up fault — an intermittent that appears after a device has run long enough to heat, and clears after a rest: the amplifier that dies after an hour, the console that crashes once it is warm, the board that fails sooner in summer or inside a cabinet. The mechanism is an unfinished failure pushed over the line by temperature — expansion opening a cracked joint, a semiconductor drifting past its margin — and its mirror is the cold fault, which fails from a cold start and heals as things warm. The distinction sets the provocation's direction: a warm-up fault is summoned by soaking toward operating heat and verified hot after repair, while pushing it cold moves it out of its window and produces a false acquittal.
condensation — the moisture film that forms on any surface chilled below the surrounding air's dew point, and the hidden hazard of cold provocation on electronics. On a powered board the film is a new circuit: leakage paths that invent faults the device never had, readings that mislead, and — with voltage present — corrosion and electrochemical migration that do lasting damage. The protocol: bulk chilling happens power-off wherever the failure window allows, a chilled board is powered only for the observation the recipe requires, a visibly wet board is unpowerable until confirmed fully dry, and any behaviour first seen on a wet board is attributed to the water until it reproduces on a dry one.

Suggested Next Sections

Must read next:

Mechanical Provocation — Flex, Tap, and Vibration — Section 9.3 arms the campaign's second provocation: the controlled flexing, tapping, and vibration that force cracked joints, fractured pads, and tired connectors to confess, with the discipline that keeps deliberate stress from creating the faults it hunts.

Recommended:

Capturing Transients and Single-Shot Events — the tripwires, persistence, and peak-detect that stand witness through every soak and chill.
Thermal Imaging and Camera Technique — the measurement skills that anchor soak temperatures and reveal which zones the assistance heating actually reached.