Two Different Noises Appear at Once (Decision Tree)

Why this matters

A customer reports "a rattling and a squealing" or "a hum and a knock," and a tech who treats that as one noise with two adjectives ends up chasing a single cause that never fully explains the report. Two distinct sounds almost always mean two distinct sources, sometimes related, often not. Fix the loud one, declare victory, and the quieter one is still there when the customer calls back annoyed that "the noise" never actually went away. The discipline is to separate the two sounds before you touch anything, then diagnose each on its own track.

Start here: separate before you diagnose

Do not let the customer's combined description ("it grinds and rattles") stay combined in your head. Get each sound described on its own:

• What does each one sound like, using its own words: pitch, rhythm, texture.
• Does each happen at the same time, or does one happen only under certain conditions the other does not share (only at startup, only under load, only at a certain temperature)?
• Can you reproduce them independently, or do they always arrive together?

If the two sounds always occur together and never apart, they may share a single root cause producing two acoustic effects (a loose assembly that both rattles and, once it shifts far enough, catches and squeals). If they occur under different conditions, or one persists after the other has been addressed, they are very likely two separate faults that happen to be showing up in the same visit.

If one sound is much louder or more urgent, triage first

If either sound indicates an active hazard (grinding metal, a burning smell, a sound accompanied by heat or smoke), stop and address that one first regardless of what else is happening. See the article on responding to a burning smell or active hazard. Do not let a minor rattle distract from triage on the sound that could mean imminent failure.

If neither sound is urgent, proceed with isolating both in whichever order is more convenient.

If the two sounds occur at the same time, every time

Test whether stopping one sub-system silences both:

1. Isolate sub-systems one at a time (kill power to a specific blower, valve, or drive independent of the rest of the unit, where safe to do so) and listen for whether one or both sounds vanish.
2. If silencing one sub-system kills both sounds, you likely have a single source producing two acoustic signatures: a loose component that both vibrates (rattle) and periodically makes contact with something else (a knock or squeal). Look for one part doing both: a loose fan blade rattling against a shroud and occasionally clipping it, a belt that both slaps and squeals as it slips.
3. If silencing one sub-system kills only one sound, you have two independent faults sharing a visit. Continue isolating the second sound against the remaining running sub-systems.

If the two sounds occur under different conditions

If sound A appears only under load and sound B is constant regardless of load, they are almost certainly separate. Diagnose sound A using load-dependent fault logic (rotating-speed-tracking issues, coupling, bearing) and sound B using constant-condition logic (a loose panel, ambient resonance, a electrical hum from a relay or transformer).

If sound A appears only at startup and sound B appears only during steady running, treat them as sequential, unrelated faults. A startup-only sound often points to a belt or a component that needs to warm or seat before it quiets; a steady-running sound points to something continuously active, like a bearing or a flow-related noise.

Diagnose and fix in order, not simultaneously

Resist the urge to make one repair and test for "the noise" generically. After you fix the first identified fault, retest specifically for both original sounds, not just whichever one you were focused on:

1. Confirm the sound you targeted is gone.
2. Confirm the other sound is still present, absent, or unchanged, and note which.
3. If the second sound is still present, treat it as its own diagnostic task starting from its own characterization, not as a residual of the first fix.

Tell the customer you found two things, not one

When you report back, say plainly that you found two separate causes for what sounded like one complaint, and what each one was. A customer who was told "fixed the noise" and later hears the second sound assumes the first fix failed, even though it did not; a customer told upfront "there were two things going on, here's what each one was" understands why a second sound persisting does not mean the first repair was bad.

Decision recap

1. Get each sound described and, where possible, reproduced on its own terms before diagnosing anything.
2. Triage any sound tied to an active hazard first.
3. If the sounds always occur together, test whether isolating one sub-system silences both; if so, look for a single part producing two effects.
4. If the sounds occur under different conditions, treat them as separate faults and diagnose each on its own logic.
5. Fix and retest for both original sounds, and tell the customer explicitly that two causes were involved.

References

• Trade-standard practice for multi-fault isolation and sequential diagnosis
• See related: Why a New Noise Isn't Always a New Problem
• See related: Belt, Coupling, or Bearing Noise Decision Tree