Scope first: this article is only for WiFi still dropping after the basic checks
This article covers only one situation: the basic checks have already been done, and the laptop WiFi still drops repeatedly. It does not re-teach basic WiFi faults, and it does not cover a broadband line fault itself. Basic WiFi faults, such as failing to connect the first time, a wrong password, or wireless function switched off, belong to the existing basic WiFi article. If the machine has never been through the basic checks, start with the basic article first; the layered method below is only for WiFi that still drops repeatedly after those checks.
Every layered method proposed below is a working method proposed in this article, not an industry standard. Before changing any setting or sending the machine for inspection, back up important data first, and note that setting locations may differ by model and system version.
The three basic checks, already done: one short recap, not a re-teaching
This section is only a recap, kept short on purpose. The three basic checks are treated as already done: restarting the router, forgetting the network and reconnecting, and a basic driver reinstall. If any of those three has not actually been done, the rest of this article is premature, because a fault that would have cleared at the basic stage can look exactly like an advanced fault. The value of the recap is the boundary it draws: from here on, every drop is read as a still-dropping-after-basics drop, and every layer below is judged against that starting point. Having restarted the router once does not clear the router layer; the router layer below looks at patterns and comparisons beyond a basic restart.
The six-layer method at a glance: from environment to hardware, layer by layer
The working method proposed in this article is as follows, and this method is a working method proposed in this article, not an industry standard: split the WiFi dropping path into six layers, and rule them out from outside in, so that whichever layer stops the drops when changed is the layer where the problem more likely stops. The six layers are: first, the signal and environment layer; second, the router and access point layer; third, the adapter and driver layer; fourth, the power-management layer; fifth, the system and network-stack layer; sixth, the hardware antenna and adapter layer.
| Layer | What it covers | When it rises in suspicion |
|---|---|---|
| Signal and environment | Laptop position, distance, obstacles, surrounding wireless environment | Drops appear in only one room, and stop in another position |
| Router and access point | The state and load of the router or wireless access point | All devices drop together, or drops follow a fixed time pattern |
| Adapter and driver | The laptop wireless adapter driver version and adapter-related settings | Drops began after a driver or system update |
| Power management | How sleep, wake, and power-saving behaviour affect the adapter | Drops appear only after sleep and wake |
| System and network stack | System network settings, network-stack state, background network-related software | Drops track a system change, a settings change, or a software install |
| Hardware antenna and adapter | The internal antenna path and the adapter hardware itself | Drops persist after the other layers are ruled out |
Symptom-pattern table: read the pattern first, then choose where to start
The table below is a working method proposed in this article, not an industry standard. It only helps the reader classify what is seen; it is not a diagnosis, and every judgement below uses only "more likely points to" language, never a certainty.
| Drop pattern | More likely points to | What to note |
|---|---|---|
| Drops only in one room, normal elsewhere | The signal and environment layer | Which room drops, which position stays normal, and how distance and obstacles differ |
| Drops everywhere in the home | The router and access point layer or a laptop-side layer, still to be separated by comparison | Whether other devices on the same network drop too |
| All devices drop together | The router or wireless access point side | Whether the drops and recoveries line up in time across devices |
| Only this laptop drops, other devices normal | The laptop side: position, driver, power, system, and hardware layers still to be separated | The laptop drop record across positions and times |
| Drops at a fixed time, for example the same period each evening | Router or access point load, or an environment change, still only as a likelihood | The drop time, how long it lasts, and whether it repeats daily |
| Random drops, no fixed time | Rule out layer by layer; do not judge from a single drop | The time, position, and sleep and wake state of each drop |
| Drops only after sleep and wake, never while active | The power-management layer, firmware, or driver-state layers | How soon after waking the drop appears, and whether reconnecting stays stable |
| Drops suddenly while active, unrelated to wake | The power-management layer becomes relatively less likely, but is not excluded | What was happening just before the drop, and whether the signal display changed |
| Reconnects automatically after a drop | The pattern still needs recording; automatic reconnection does not mean the problem is solved | How long reconnection takes, and whether it drops again shortly after |
| Needs manual reconnection after a drop | A pattern worth recording, but not enough on its own to name a layer | Whether manual reconnection stays stable, or drops again soon after |
The signal and environment layer: one position and another position mean different things
This layer covers laptop position, distance, obstacles, and the surrounding wireless environment. Its characteristic is position: if drops appear in only one room and stop in another position, the signal and environment layer rises in suspicion; if drops happen everywhere, that layer becomes relatively less likely, and judgement moves to other layers.
Two misreadings must be avoided. First, a full signal display does not prove a stable connection; the signal display is only a rough reference, and it cannot by itself clear the signal and environment layer. Second, normal behaviour in one position does not prove normal behaviour in another position, because distance, obstacles, and the surrounding wireless environment are all different. The most useful comparison is the same laptop, in the same period, in different positions: when the drops follow the position, the environment layer deserves ruling out first; when the drops stay the same however the position changes, the environment layer can be set aside for now, and other layers take over.
Need a laptop repair expert?
Free diagnosis · Transparent pricing · No fix, no fee · 180-day warranty
The router and access point layer: first separate one laptop dropping from the whole home dropping
This layer covers the state and load of the router or wireless access point. Its most important comparison is not another restart, but other devices: whether other devices on the same network drop at the same time. If all devices drop together, the router and wireless access point side rises in suspicion; if only this laptop drops while other devices stay normal, the laptop side rises in suspicion. That comparison must be made close to the moment of a drop; a later impression that other devices seemed fine carries little evidence value.
A fixed time pattern is also worth recording. Drops at a fixed time, for example the same period each evening, more likely point to router or access point load, or an environment change, but still only as a likelihood, never a confirmation. Random drops should not be judged from one time alone; repeated records must show a real repetition before a pattern is claimed. Before changing any router or access point setting, note the original setting, change only one item at a time, and do not change settings that are not understood; record whether the drops change after each change. A basic restart has already been done, so repeating a restart is not new ruling-out evidence.
The adapter and driver layer: drops that began after a driver version change deserve attention
This layer covers the laptop wireless adapter driver version and adapter-related settings. Its characteristic is timing: if drops began after a driver or system update, the adapter and driver layer rises in suspicion; if drops have no connection to any update, that layer becomes relatively less likely, but is not excluded. A driver version change does not prove a driver fault; timing is only one clue, and it still needs the other layers to be ruled out before any judgement carries weight.
Adapter-related settings are discussed here only as general concepts, with no specific setting items or values named. In concept, individual adapter settings can affect dropping behaviour, so note the original setting before any change, change only one item at a time, and record whether the drops change. If a change brings no improvement, restore the original setting, and do not leave behind a pile of changed and unrecorded settings; otherwise even the record of what was changed is lost, and later ruling out only becomes harder. The driver layer must also be read together with the power-management layer: a pattern that began after an update and appears only after waking raises both the driver-state layer and the power-management layer for consideration.
Driver timing needs a second check as well: whether drops began at the same time as a driver change, or only weeks later. Drops that began at the same time as a change carry a stronger timing clue than drops that began long after, because a long gap leaves room for other causes to enter, including position changes, network changes, and later software changes. That gap does not clear the driver layer, and it does not blame it either; it only weakens the timing clue, so the other layers must carry more of the judgement. A driver layer judged on timing alone, without position records, other-device comparisons, and wake records, is a guess, not a ruling out.
The power-management layer: drops after sleep and wake are a different matter from drops while active
This layer covers how sleep, wake, and power-saving behaviour affect the adapter. Its characteristic is state: drops that appear only after sleep and wake, and never while active, raise the power-management layer, firmware, or driver-state layers; drops that appear suddenly while active, with no connection to waking, make the power-management layer relatively less likely. Mixing those two patterns together is the most common source of misjudgement here.
In concept, power-saving behaviour can leave the adapter unable to restore a normal connection promptly in certain states; that is only a general concept, not a judgement about any particular machine. Judging this layer depends on wake records: how soon after waking a drop appears, whether reconnecting stays stable, or whether it drops again shortly after. If every wake is followed by a drop, but active use never drops, that pattern itself is strongly pointing; if both waking and active use drop, the power-management layer is not the only direction, and the signal, router, driver, system, and hardware layers must be revisited.
The system and network-stack layer: settings and network-stack possibilities
This layer covers system network settings, network-stack state, and background network-related software. Its characteristic, again, is timing and change: if drops began after a system change, a settings change, or a software install, the system and network-stack layer rises in suspicion. Its most easily missed corner is background software: individual background network-related software can affect connection behaviour, but this article names no software, and judgement rests only on timing and step-by-step ruling out.
This layer is also a ruling-out position: if the laptop drops in every position while other devices on the same network stay normal, the signal and router layers have become relatively less likely, and the remaining directions include driver, power, system, and hardware layers. The system layer cannot be judged from a single drop; repeated records must show whether drops track a particular system state, or have no connection to system state at all. Before changing any system network setting, note the original setting, and change only one item at a time.
One more comparison belongs here: a different network. If the same laptop drops on a second, unrelated network as well, the laptop side rises in suspicion, because the network side has changed while the laptop has stayed the same. If the laptop stays stable on the second network and drops only on the first, the first network side, including its router and environment, rises instead. That comparison is only a likelihood, and it needs repeated records on both networks before it carries weight, because a single stable session on a second network proves little on its own.
The hardware antenna and adapter layer: an inspection-level layer, and when to stop
The hardware antenna and adapter layer covers the internal antenna path and the adapter hardware itself. It is considered only after the other layers are ruled out and drops still persist, and it is an inspection-level layer: it should not be concluded by the user alone. The internal structure of a laptop should not be opened by the user for inspection, because opening it can cause further damage and can affect warranty, so judgement at this layer belongs to the inspector.
Stop and send the machine in, rather than opening it yourself, in any of the following cases: drops persist after the other layers are ruled out; the machine has been dropped, pressed, repaired before, or is suspected of liquid damage, in which case the liquid-damage direction applies and this article does not continue it; there is a burnt smell, abnormal heat, body deformation, smoke, sparks, or a suspected battery or circuit safety problem, in which case stop using the machine at once and send it in; the machine is still within its warranty period and opening it could affect the warranty, so do not open it yourself; or a safe distinguishing test cannot be completed, in which case sending it in is the endpoint.
Before changing settings or sending the machine in, back up important data: copy important files to a second location, then open them on another device to confirm they open. The table below is only a template structure. Every field is to be filled in by the reader from their own actual situation, and must never be treated as real data.
| Information item | How to prepare |
|---|---|
| Drop pattern | One room or everywhere, fixed time or random, automatic or manual reconnection |
| Other-device comparison | Whether other devices dropped at the same time, or only this laptop dropped |
| Position record | Which position drops, which position stays normal, and how distance and obstacles differ |
| Time record | The time of each drop, how long it lasted, and whether it repeats daily |
| Sleep and wake record | How soon after waking a drop appears, and whether reconnecting stays stable |
| Steps already tried | The three basic checks, and each later change made one variable at a time |
| Backup confirmation | Confirm important files already open from a second location before sending the machine in |
| Item | Price |
|---|---|
| Battery | HK$580 up |
| Screen | HK$1,280 up |
| Main board chip-level | HK$880 up |
| Keyboard | HK$480 up |
| Other repairs, including WiFi disconnection repair | Quoted in writing after inspection |
Summary
To summarise: when basic checks are done and WiFi still drops repeatedly, read the drop pattern first, run the other-device comparison, then rule out the six layers in order: signal and environment, router and access point, adapter and driver, power management, system and network stack, hardware antenna and adapter. Change only one variable at a time, and record position, time, other-device results, and sleep and wake state each time. This layered method is a working method proposed in this article, not an industry standard, and every judgement is only a likelihood, never a confirmation. Back up important data before changing settings or sending the machine in, and stop and send it in when safe distinguishing is impossible, or when drops persist after the other layers are ruled out.
Need Professional Laptop Repair?
Laptop King has 15+ years of repair experience in Shek Mun, Sha Tin. Free diagnosis, transparent pricing, no fix no fee. 180-day warranty for your peace of mind.
