Speaker Still No Sound or Crackling After the Basic Checks? Advanced Differentiation: Services, Drivers, Enhancements, Speaker Units, Cables, Chips, and BIOS

Premise: This Is the Advanced Article, Not a Rewrite of the Basics

The earlier article, "Laptop Speaker No Sound or Crackling: Identify the Symptom First, Then Check Settings, Drivers, and External Devices", already covered the basic checks. This article only cites it here as a premise and does not rewrite that content. It assumes you have already done the basics: restarted, checked volume and mute, chosen the output device, reinstalled the driver, and tested with headphones, yet the speaker still has no sound, crackles, or drops in and out.

The core principle of advanced differentiation is simple: one symptom does not equal one cause. No sound can sit at the routing, service, driver, enhancement, format, speaker unit, cable, chip, or firmware layer. Without hands-on inspection, any cause is only a possibility, not a diagnosis. Change only one variable at a time, test the same audio clip after each change, and write the result down before changing the next thing, or you will never know which step mattered. Before touching BIOS settings, firmware updates, or opening the machine, back up important data; if you are unsure, stop and send it in. If you see heat, discoloration, a burnt smell, or smoke, stop using it at once and do not keep testing. Speaker repair pricing is quoted in writing after inspection, and this article gives no specific speaker repair figure.

Step 1: Separate the Output Scope: Built-in Speakers, or Every Output

After the basics, the first step is not to reinstall the driver again. It is to play the same audio clip through each output in turn: built-in speakers, wired headphones, Bluetooth headphones or speakers, a USB headset, and an HDMI display output. When testing the built-in speakers, disconnect Bluetooth first and unplug USB and HDMI devices, so the sound is not still going somewhere else. Routing errors are common: after connecting Bluetooth headphones, an HDMI display, a USB controller, or a dock, Windows sometimes sends sound to the wrong device while the built-in speakers are perfectly fine.

Output comparison result	More likely layer	Next differentiation
Only the built-in speakers are silent; headphones and Bluetooth are fine	Output routing, a disabled speaker, a stuck jack sensor, or the built-in speaker path	See Steps 2, 7, and 8, not the board layer at once
Headphones are silent too; every output is silent	Driver, Windows Audio service, system settings, audio chip, or board layer	See Steps 4 and 5, then Step 9
A USB headset works, but the built-in speakers and the wired jack both fail	The built-in audio jack side or the built-in audio path	Note that USB audio bypasses the built-in path, then compare the jack
Bluetooth works, but wired headphones and built-in speakers both fail	Driver or audio service layer	Check services and drivers first, not just another headset
An HDMI display has sound, but the built-in speakers do not	Routing or the built-in speaker path	Disconnect HDMI and test the built-in speakers again to confirm routing has returned
The built-in speakers recover after unplugging headphones	A stuck headphone jack sensor or a jack contact problem	See the jack part of Step 8, and record the change before and after unplugging

Two details matter here. First, a speaker appearing in Settings does not mean it is the default playback device. In Settings, System, Sound, More sound settings, Playback, right-click the device and choose Set as Default Device before the choice counts. Second, the speaker may simply be disabled: right-click empty space in the Playback list, tick Show Disabled Devices, and enable any device listed. Missing either step sends the whole advanced differentiation in the wrong direction.

Step 2: One Side or Both Sides: Balance, Mono, and Channel Type First

One-sided silence or one-sided quiet sound should never be read at once as a dead speaker on that side. Windows left and right balance can drift independently. The main volume can look normal while balance has been pushed fully to one side, producing exactly the same symptom as a dead speaker. Check in Settings, System, Sound, choose the speaker device, open More sound settings, choose the speaker, open Properties, then Levels, Balance, and confirm left and right carry the same value. If the one-sided fault disappears after centring balance, it was a setting fault, not a hardware fault.

One-sided symptom	Check this first	How to read the result
One side silent, the other normal	Whether left and right balance is centred	Recovery after centring points to a balance offset
One side quiet, the other normal	Balance values and the mono switch	Mono audio sits in Settings, Accessibility, Audio, and should stay off
Only one song or one clip sounds one-sided	How that recording itself distributes channels	Content recorded only on the left channel will only play on the left; that does not mean the speaker is broken
After swapping headphones or external speakers, the quiet side follows the hardware	A swap-device comparison	A fault that follows the hardware points at that device itself
After swapping, the quiet side stays on the same side	The settings or driver path	A fault that stays with the machine points at settings, drivers, or the system layer
The speaker type setting is wrong	Whether the stereo speaker type is correct	A wrong type setting can distort channel behaviour; correct it before judging hardware

The swap-test logic needs stating plainly. Built-in speakers cannot have their wires swapped, but swapping headphones or external speakers is the equivalent test. Connect the same headphones to another device: if the imbalance remains, the headphones are the direction; if balance is normal on the other device, the original machine's settings or driver path is the direction. One-sided distortion with the other side normal, where driver changes and output changes have all failed, is described in community discussion as leaning toward a one-sided hardware fault, but this article keeps that uncertainty explicit. It is a leaning, not a diagnosis, and confirmation needs inspection. A maker's pre-boot hardware test can supply a second, independent piece of evidence, for example a brand-specific key at power-on entering component tests followed by an audio playback test, but keys and menus vary by brand and must not be written as a universal procedure.

Step 3: Crackling, Silence, or Intermittent Sound: Three Symptoms, Three Routes

Crackling, complete silence, and intermittent sound are three different routes, and they cannot share one checklist. Crackling starts with the processing layer and the volume layer. Silence starts by separating a missing device from a present but silent device. Intermittent sound widens the search to related drivers and power management. Sorting the symptom wrongly sends every later step wrongly too.

Symptom	More likely layers, in order	Key comparison test
Crackling, distortion, or static	Audio enhancements, default format, exclusive mode, volume ceiling, driver, speaker unit	Turn enhancements off, turn exclusive mode off, change format, one variable at a time
Complete silence, device present in Settings	Output routing, default device, disabled device, audio service, enhancements	Change output, set default, restart services, one at a time
Complete silence, no device listed in Settings	Missing, disabled, or unloaded driver, BIOS disabled audio	Show hidden devices, scan for hardware changes; a hidden device points at the driver layer
Intermittent, popping, or brief dropouts	Related drivers, power management, system file layer	Wi-Fi on and off comparison, USB device removal comparison, power plan comparison
Only one application silent, others normal	That application's volume mixer and output device	Check that application first, not driver reinstallation or a new speaker
Silence suddenly after an update	Update, driver, and service layers	Follow the official order: pending updates, driver update, driver rollback, service restart, with no skipped step

The silence split deserves emphasis. A missing device follows the Device Manager, hidden device, and driver installation route. A present but silent device follows the output choice, default device, service, and enhancement route. Writing the two routes as one list only confuses the reader. For intermittent sound, one more point matters: a normal-looking processor load does not rule out driver blocking, because graphics, network, Wi-Fi, Bluetooth, USB, storage, or chipset drivers holding the system for a long time can still delay audio data, producing clicks, pops, or a momentary pause.

Step 4: How to Recognise a Stuck Windows Audio Service

When the driver looks normal, the device exists, yet the whole machine is silent, or the built-in troubleshooter has already run without effect, the next layer is the Windows Audio service. This layer is easy to overlook, because the speaker icon may show no error and changing drivers has no effect. When a service is stuck, the hardware and the driver can be completely normal while every sound stays silent, system sounds and applications alike.

Service check item	What it should be	How to read the result
Windows Audio	Status Running, startup type Automatic	If not running, right-click and choose Start, then test audio
Windows Audio Endpoint Builder	Status Running, startup type Automatic	Check both services together, not just one of them
Remote Procedure Call	Status Running	Both audio services depend on this service; if it stops, the audio services struggle to stay running
Sound returns at once after restarting both services	A one-off stuck service	Write this result down, so the next failure points back to this layer
The service stops again at once after restart	A driver or device initialisation problem	Do not retry endlessly; move to dependency and driver initialisation checks
No sound on every boot, briefly restored after restart	A startup type or boot initialisation problem	Confirm the startup type is Automatic, then look at the driver layer
Sound present but quiet or distorted	A service factor is still a possible cause	Do not jump to speaker ageing; rule out the service factor before discussing the speaker unit

The official post-update silence order is worth recording in full: first install pending Windows updates and restart, then update the audio driver, then roll back the audio driver, and finally restart the Windows Audio service. The order itself is a differentiation clue: only move to drivers when updates have failed, and only move to rollback when a driver update has failed. To restart the services, type the services tool in the Start menu, right-click Windows Audio and choose Restart, do the same for Windows Audio Endpoint Builder, then test audio. A service that stops again immediately is an important warning sign. Do not keep restarting it; continue with dependency and driver checks. When only one application is silent, do not disable or change the startup type of unrelated Windows services at random; stay focused on the audio-related services.

Step 5: The Driver Layer: Update, Rollback, Reinstall, and Generic Driver Comparison

The driver layer has four actions, and each one fits a different condition. A yellow warning sign under Sound, video and game controllers in Device Manager is direct evidence of a driver problem, ahead of any thought of opening the machine. Updating means right-clicking and choosing Update driver, then automatic search. If Windows says the best driver is already installed yet the fault remains, go to the computer or sound card maker's support site, download the latest driver for that Windows version, install it, and restart.

Driver action	When it fits	Note
Update driver	A yellow warning sign, or a driver suspected to be outdated	Try automatic search first, then the maker site version
Roll back driver	The fault appeared after a driver update	Only available when an older driver exists; a greyed-out button means no older driver is available
Uninstall, then restart for reinstallation	An update failed, or the driver is suspected to be damaged or incompletely installed	Restart is required so the system reinstalls automatically; do not skip the restart
Delete the driver software on uninstall	When that option is shown	The reinstall is cleaner, but confirm a driver source exists afterwards
Generic driver comparison	The maker driver keeps failing	Choose High Definition Audio Device; basic sound may return, but maker extra features may stop working
Maker driver comparison	Generic driver works but the maker driver fails	Points at the maker driver or audio package, not at the speaker unit

The generic driver comparison is a valuable advanced test. Sound returning on the generic driver points at the maker driver or audio package. Continued distortion or silence on the generic driver means the maker driver is not the only variable, and the service, format, and hardware layers still need attention. Conversely, a normal-looking driver display does not prove the hardware is fine, and a failed driver reinstall does not prove the hardware has failed; the service, enhancement, format, and firmware layers sit in between. When Device Manager shows no device at all, the official approach is to expand Sound, video and game controllers, right-click a visible device and choose Enable device, or, if nothing is visible, choose View, Show hidden devices, then Action, Scan for hardware changes. Whether a hidden device appears is the first fork between an unloaded driver and undetected hardware. The built-in troubleshooter sits in Settings, System, Sound, under Advanced, Troubleshoot, or in Settings, System, Troubleshoot, Other troubleshooters, under the audio item; follow the on-screen instructions.

Step 6: Three Processing-Layer Variables: Enhancements, Exclusive Mode, and Default Format

For crackling, the processing layer is the most important one. Audio enhancements, exclusive mode, and the default format can each distort sound while the speaker unit itself is completely fine. Turning enhancements off gives the cleanest signal chain for comparison, and it is a required step in any crackling investigation.

Processing-layer variable	Where to check	Comparison approach
Audio enhancements switch	Settings, System, Sound, choose the device, Advanced settings, Audio enhancements	Set it to Off, then test the same audio clip
Legacy control panel enhancements switch	Open the sound control panel, right-click the speaker, Properties, Enhancements tab	Tick Disable all enhancements, then Apply and OK
Enhancement option location varies by driver	Settings page, legacy control panel, or the maker audio application	Absence on the Settings page does not mean no enhancements exist; check the legacy panel instead
Exclusive mode, first box	Device Properties, Advanced tab, Exclusive Mode	Clear Allow applications to take exclusive control of this device
Exclusive mode, second box	The same tab, under Exclusive Mode	Clear Give exclusive mode applications priority; both boxes must be cleared
Default format comparison point	Device Properties, Advanced tab, Default Format	Try 16 bit 44100 Hz first, then try other format levels
An excessively high format setting	The same location	An excessively high quality setting can conflict with hardware; find the balance that suits that device

Enhancements and exclusive mode interfering with sample rate are a common software-layer cause of crackling. If crackling disappears after turning enhancements and exclusive mode off, the fault sits in the processing layer. If crackling remains after both are off, move to the driver, format, and hardware layers. One warning must not be blurred: turning enhancements off is not the same as deleting the maker audio package. Laptop speakers are small, so makers add a software tuning layer, called Audio Processing Objects in Windows, which typically does equalisation, bass enhancement, and limiting. The limiter also protects the speaker by preventing loud passages from distorting. Deleting the tuning layer leaves the speaker receiving an untuned raw signal, without the limiter, so loud passages may distort more easily. This article therefore does not encourage deleting maker audio folders or packages; turning enhancements off for comparison is enough.

Step 7: Speaker Unit Damage Clues: The Volume Boundary and the Source Comparison

Speaker unit damage cannot be concluded from the word crackling alone. It needs the volume boundary and the source comparison to narrow it down. Speaker units are small and fragile, and sustained loud playback or an impact can tear the cone, producing a persistent buzz or rattle. Common blown-speaker signs include distortion, complete silence, a sudden volume drop, and rattling; cone damage or voice coil trouble can each cause distortion. Any one of these signs alone is not enough for a conclusion; the comparisons below give them differentiation value.

Speaker unit comparison test	Result	How to read it
Distortion only near maximum volume, normal at medium volume	The clean output limit may have been reached	Suspect the output limit and enhancement settings first, not a dead unit
Distortion already at low volume, especially on one side only	Further checking is warranted	Raises suspicion of unit damage, a loose part, or a blocked grille
One side distorted at the same volume, the other normal	The fault is concentrated on that side	Check for a blocked grille, a loose part, or damage on that side
Distortion across different sources	A voice recording, music without heavy bass, and a clearly spoken video all distort	The fault is more likely in the machine audio path than in one file
Only one audio clip distorts	Other sources are normal	Suspect that clip itself first, not the speaker
Distortion disappears at medium volume	An output-limit direction	Write down the volume boundary where distortion appears; it is useful for inspection
Persistent buzz or rattle, unrelated to volume	A cone or loose-part direction	Present even at low volume, so it should not be blamed on enhancements alone

Dust, debris, or a loose part can also cause rattling. If touching the speaker grille or the palm rest area changes the noise, arrange inspection rather than pressing hard. Visually checking a cone for tears, holes, or loose wires is an opened-machine task, and this article does not ask readers to open the speaker themselves. The one-line summary for the unit layer is this: the volume boundary, plus the source comparison, plus one-sided or two-sided, together carry differentiation power; any one of them alone is only a clue.

Step 8: Speaker Cables, the Jack Sensor, and Intermittent Contacts

Sound that changes with movement is the strongest pointer toward cable and connector trouble. A fixed driver fault struggles to explain why moving the machine changes the sound. The thin wires connecting the speakers to the board can loosen after an impact, a hinge repair, or an earlier repair, producing intermittent crackling or one-sided silence.

Movement or contact clue	More likely direction	Correct handling
Pressing the speaker area removes distortion; releasing brings it back	A poor signal wire solder joint, temporarily fixed by pressure	Record the pattern; do not keep pressing to hold it in place; send it in
Moving or shaking the machine worsens crackling	A loose wire, with intermittent contact switching the speaker rapidly between signal and no signal	Record which movement triggers it, and describe it clearly for inspection
Touching the speaker grille or palm rest changes the noise	A loose part or a contact problem	Do not press hard; arrange inspection
Sound changes after opening or closing the lid	A hinge-area cable may be affected	Record the before and after change, and mention any earlier hinge repair
The speakers recover after unplugging headphones	A stuck jack sensor	Dirt or damage in the jack can make the machine think headphones are still plugged in, muting the speakers
The plug only works when held at an angle	A jack contact problem	Record the angle and the trigger condition; do not keep holding it at an angle in daily use
The headphone jack shows dirt, looseness, or damage marks	A jack-side problem	Cleaning the jack and unplugging headphones are investigation steps, but do not poke a metal tool inside

For the inspection layer, the boundary is worth understanding without asking readers to measure it themselves: during inspection, a steady tone is played at maximum volume while an instrument measures the alternating voltage across the speaker contacts on the board. A reading points more toward the speaker or cable side; no reading at all points more toward the amplifier or board side. Similarly, if headphones work but a known-good speaker still produces no sound on the same machine, the fault is more likely between the audio codec and the speaker connector, including the amplifier stage, its power or enable circuit, or the speaker cable. These are inspection directions, not conclusions a reader can reach from symptoms alone.

Step 9: Separating the BIOS and Firmware Layer from the Audio Chip and Board Layer

The BIOS and firmware layer, the audio chip layer, and the board layer come last, because they explain only a narrow range of symptoms and cannot be used to explain every speaker fault. The BIOS layer mainly explains a device that does not appear, a device that has been switched off, or a fault that appeared after an update. It does not explain headphones working while only one speaker crackles, or sound returning only when pressed, where unit or cable pointers are strong.

Layer	Cases it can explain	Cases it cannot explain
Onboard audio switched off in BIOS	A device completely absent from the system	One-sided crackling, or sound returning only when pressed
Outdated BIOS or chipset driver	Audio performance affected, or a fault after an update	A fixed one-sided unit damage pattern
Restoring BIOS defaults	Clearing a wrongly changed setting that may affect audio	A case already shown to be a unit or cable fault
Audio chip or board layer	Every output silent, driver already reinstalled, a known-good speaker still silent	A single speaker unit fault cannot explain every output being silent
Every output silent, no improvement after driver reinstallation	Board audio circuitry may need repair; this kind of fault is less common but more serious	Do not conclude a chip fault from silence alone; the service and driver layers still apply
A device still completely absent after driver updates and restarts	A stronger hardware suspicion	A plain speaker unit fault usually does not make the whole device disappear
A brand built-in hardware test	Plays audio independently of Windows and drivers, then asks whether it was heard	Heard points at software or settings; unheard produces an error code, but the code alone does not name the failed part

Common BIOS setting names for onboard audio include Onboard Audio, HD Audio Controller, and similar names, and they need to be Enabled. Exact names vary by brand, so this article does not fix one brand's key or menu name, and readers should not change unfamiliar firmware settings. Official troubleshooting also includes referring to the restore-BIOS-settings guidance first, then updating and confirming BIOS, Windows packages, and drivers to the latest versions, since regular updates can improve system stability and performance. A BIOS update still belongs late in the order, after output, service, driver, enhancement, and format causes have been ruled out, and any update needs a backup and a steady power supply first. Board-layer repair scope includes the audio chip, the amplifier stage, power circuits, and cable connectors, but which one applies needs the machine opened and inspected, and this article assigns no repair method from symptoms alone. As a pricing reference for comparison, board-level chip repair starts at HK$880, while speaker repair itself is always quoted in writing after inspection, and the two must not be confused.

Step 10: Clues After Liquid Exposure, a Drop, or Pressure, and When to Stop

Liquid exposure, a drop, and pressure work by different mechanisms, and they should not be lumped together as generic physical damage. Liquid spilled near the keyboard or the speaker grille can corrode speakers and connectors. Crackling or muffled sound from a speaker can follow liquid exposure, and laptop speaker diaphragms made of paper are easily damaged by liquid. A drop points more toward a torn cone or a loosened cable. Pressure, or sound that comes and goes when pressed, points more toward an intermittent solder joint or connector contact, rather than a plain dead speaker.

Physical history clue	More likely direction	Why it deserves prompt inspection
Muffled or crackling sound after liquid exposure	Liquid corrosion of speakers, connectors, or cables	Corrosion can keep spreading even after the surface looks dry
Residue near the keyboard, vents, ports, hinge area, speaker grille	Liquid residue	Green or blue deposits, white powder, rust-coloured marks, or a sticky film are outward clues
The machine looked normal after a spill, then faults began a week later	Delayed liquid damage	A delayed start does not break the link with the spill; mention the spill history
Beyond the speaker, random shutdowns, screen flicker, key faults, battery faults, or charging or USB failure	Liquid may already have reached the board layer	Accompanying symptoms matter more for inspection than a single speaker fault
Distortion or silence only after a drop or impact	A torn cone or a loosened cable	A clean exterior does not prove the inside is undamaged
Sound that comes and goes after heavy pressure	An intermittent solder joint or connector contact	Do not press hard to hold it in working order
Liquid marks at bottom cover seams, screw holes, or the machine base	Liquid has entered the machine	Do not treat this as an ordinary driver fault

The stop rules need stating plainly. On heat, discoloration, a burnt smell, or smoke, stop using it at once. On suspected liquid exposure, do not keep powering on to test sound, because corrosion keeps spreading. On a suspected loose cable, do not keep pressing or shaking the machine to hold sound in place. On unfamiliar BIOS settings, do not change settings at random. These stop points are not caution for its own sake; they prevent a fault that inspection could narrow down from becoming wider damage. For inspection, liquid, drop, and pressure history must be volunteered, together with the timing, how long after the event the speaker fault appeared, and whether other functions failed at the same time.

Frequently Asked Questions

After the basic checks, how do I tell a speaker-path fault from a system-layer fault?

Play the same audio clip through each output in turn. If only the built-in speakers fail while headphones, Bluetooth, and USB external outputs are all normal, the direction points more toward output routing, a disabled speaker, a stuck jack sensor, the speaker unit, the cable, or the amplifier stage. If every output fails, the direction points more toward drivers, the Windows Audio service, system settings, or the audio chip layer. Sorting the scope wrongly sends every later step wrongly, and any conclusion is subject to inspection. Speaker repair pricing is quoted in writing after inspection.

If crackling remains after turning enhancements off, does that mean the speaker is broken?

No. Turning enhancements off, turning exclusive mode off, and changing the default format are three steps, and only after all three still leave crackling is the processing layer ruled out. The driver layer, the generic driver comparison, the system file layer, the unit layer, and the cable layer still remain. Check the volume boundary in particular: crackling only at high volume, with medium volume normal, points more toward the output limit and enhancement settings, while crackling already at low volume, especially on one side only, raises suspicion of a unit fault. Never delete the maker audio package, because the limiter inside the tuning layer also prevents distortion.

The service stops again at once after restart. What should I do?

Do not retry endlessly. A service that stops at once points at a driver or device initialisation problem, so move to dependency and driver initialisation checks, including confirming that Remote Procedure Call is running, then looking at driver update, rollback, or reinstallation needs. Sound returning at once after restart is the one-off stuck service pattern. Record which of the two patterns you saw, and describe it clearly for inspection.

What test results should I bring before inspection?

Bring the checklist below, not just the words that the speaker has no sound. Each item only needs an answer of yes or no, which side, or when it appears, so inspection staff do not need to ask everything again before narrowing the range. For other repair pricing references, see Pricing; to arrange an inspection, go to Book a diagnostic. Speaker repair pricing is quoted in writing after inspection. Shop details: Room 1209, Daly Plaza, Shek Mun, Sha Tin; phone +852 2186 8010; WhatsApp +852 6558 6806; opening hours 12:00-19:00.

Inspection item	What to answer
Output device setting	Which output device is currently chosen, whether Speakers is set as default, and whether disabled devices were shown and checked
Built-in speaker behaviour	Both sides silent, or only left or only right silent; when sound is present, whether it is normal, quiet, muffled, crackling, buzzing, or rattling
Wired headphone comparison	The result for the same audio clip on wired headphones, and whether the built-in speakers recovered after unplugging headphones
Bluetooth comparison	The result on Bluetooth headphones or speakers, and whether Bluetooth was disconnected before testing the built-in speakers
USB and HDMI comparison	Where sound went with a USB headset, an HDMI display, or a dock attached, and whether those devices were removed before testing the built-in speakers
Crackling trigger conditions	At what volume it appears, whether every source crackles or only one clip or one application, and whether turning enhancements off was compared
Movement trigger conditions	Whether moving, shaking, touching the grille, opening or closing the lid, or an earlier repair changed the sound, and whether the change was an improvement, a worsening, or intermittent
Jack condition	Whether the jack shows dirt, looseness, or damage marks, and whether the plug only works when held at an angle
Device visibility	Whether the speaker appears in Settings and Device Manager, whether it is disabled, whether it shows a warning sign, and whether drivers were updated or reinstalled
BIOS and firmware history	Whether settings were changed or BIOS, system, or drivers were updated before the fault, recorded only as changed or not changed, without changing settings at random
Liquid, drop, and pressure history	Any spill, liquid entry, drop, impact, or heavy pressure, how long after the event the speaker fault appeared, and whether other functions failed at the same time
Accompanying symptoms	Beyond the speaker, any random shutdowns, screen flicker, key faults, battery faults, or charging or USB failure
Brand built-in test result	Whether a brand built-in hardware or audio test was run, whether sound was heard or not heard, and whether speakers or headphones were used for listening
Machine basics	Brand and model, system version, the date the fault first appeared, sudden or gradual onset, and any earlier repair to speakers, hinges, or the board