Mechanical Keyboard Numpad Dead? Here's How to Diagnose and Fix It
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard TesterA dead numpad on a mechanical keyboard is almost always a broken PCB trace, a failed column or row diode, or a collapsed hot-swap socket pin — not a driver problem. The numpad sits at the far right edge of a full-size or 1800-compact PCB, which makes its copper traces the longest and most vulnerable to flex stress when the board is carried without a case. Diodes in that matrix block fail silently after years of thermal cycling, and hot-swap sockets — especially the Kailh PG1511 CPG151101S11 variant used on budget boards — lose contact tension after repeated switch pulls.
Confirm the Scope of the Failure First
Before you open anything, you need to know whether you have a full numpad blackout, a partial row or column failure, or a Num Lock state problem. Open MiniTestLab Keyboard Test and press every numpad key individually. The tool lights up each keycode as it registers. Note exactly which keys are dead and map them on paper.
A full numpad blackout with Num Lock LED still functioning points to a shared row or column trace break, or a gate diode on the matrix entry point. A dead Num Lock LED alongside a dead numpad means the failure is upstream, closer to the microcontroller pin or its pull-down resistor. A checkerboard pattern of dead keys — alternating live and dead — is the classic signature of a single broken column trace running through the numpad zone.
- Press Num Lock. If the LED toggles but no numpad key registers, the MCU is reading Num Lock correctly — the matrix scan for that key cluster is broken downstream.
- If the numpad keys send wrong keycodes (numpad 4 fires as left arrow), Num Lock is simply off. Toggle it and retest.
- If you own a Ducky One 2 or One 3 series and the ducky keyboard numpad not working symptom appeared after a firmware flash, hold Fn + Alt + P for three seconds to reset the key mapping layer before doing any hardware work.
PCB Trace and Diode Diagnosis
Set your multimeter to continuity mode. You do not need a schematic. On any standard mechanical keyboard matrix, each key switch sits at the intersection of a row and a column trace. Each switch position also has a 1N4148 SOD-123 surface-mount diode in series, oriented cathode-toward-column. These are 0402 or 0603 package components and they fail open, not short.
- Remove the numpad keycaps and switches (or just the keycaps if the board is soldered).
- Probe across each visible diode pad pair in the dead zone. A good diode shows roughly 0.55–0.65 V forward voltage in diode mode. An open diode reads OL. Replace any that read OL with a fresh 1N4148 in the matching SOD-123 package — under $5 for a reel of 100 from any electronics supplier.
- Trace the copper runs visually under a loupe or phone macro lens. Flex cracks appear as a hairline interruption in the copper, sometimes with a slight green discoloration in the soldermask. A cracked trace between Numpad 7 and Numpad 4 will kill an entire column.
- Bridge a confirmed cracked trace with a strand of 30 AWG kynar wire soldered across the break. Apply liquid flux first, then a small iron tip at 320°C for no more than two seconds per pad.
On Aula keyboards — the F75 and F87 are the most common models where the aula keyboard numpad not working report surfaces — the numpad column traces run very close to the right PCB edge and crack at the mounting screw hole nearest the Numpad 3 key. Remove the four Phillips PH1 screws along the bottom case seam, the two hidden under the top right label sticker, and inspect that area first.
Hot-Swap Socket Failure and Switch Seating
If your board uses Kailh PG1511 CPG151101S11 hot-swap sockets and the dead keys are clustered rather than forming a clean row or column pattern, the sockets themselves are the likely culprit. The retention arms on these sockets lose spring tension after roughly 10–15 swap cycles, allowing the switch pins to make intermittent contact.
| Socket Type | Pin Retention Cycles (rated) | Common Failure Mode | Fix |
|---|---|---|---|
| Kailh PG1511 CPG151101S11 | 100 | Arm spread, intermittent contact | Reseat or replace socket |
| Millmax 0305 / 7305 | 500+ | Pin corrosion in humid environments | IPA flush, re-tin switch pin |
| Gateron hot-swap (KS-33 compatible) | 35 | Socket delamination from PCB | Reflow socket pads |
To test a suspected Kailh socket, insert a switch and wiggle it laterally by 1–2 mm while watching the Keyboard Test live view. If the key flickers in and out, the socket retention arm is the problem. Use a dental pick to gently squeeze the two retention arms inward before reinserting the switch. If the socket pad has lifted from the PCB, reflow it with flux and fresh 63/37 solder at 330°C.
Firmware and Layer Configuration
On QMK-based boards (many Aula F-series, Keychron Q-series, and custom builds), a misconfigured layer can make the numpad appear dead while the hardware is fine. Connect the board, open QMK Toolbox, and confirm the correct .hex or .uf2 firmware is flashed. In Via or Vial, navigate to Configure > Layers > Layer 0 and verify that numpad keycodes KC_P0 through KC_PDOT and KC_NLCK are assigned and not overwritten by a transparent key on an active layer above Layer 0.
For Ducky boards running Ducky Macro 2.0 firmware, hold Fn + Alt + R for five seconds to perform a full factory reset. This clears any macro reassignment that may have nulled out the numpad cluster. After reset, retest with the Keyboard Test before reassembling the case.
If you want to cross-check whether the issue is isolated to the numpad or affecting modifier key timing globally, run the Mouse Test alongside to confirm USB hub bandwidth is not the variable — shared USB controllers on cheap hubs occasionally drop HID reports from one device when another spikes bandwidth.
Frequently Asked Questions
Why did my numpad stop working after I cleaned my keyboard?
Liquid almost certainly entered the hot-swap sockets or bridged a diode pad. Remove the switches in the dead zone, flush each socket with 99% isopropyl alcohol using a syringe, and let the board dry vertically for 48 hours before retesting. Do not use compressed air directly into sockets — it drives liquid deeper into the pad joint.
My Ducky keyboard numpad not working after a firmware update. What happened?
Ducky firmware updates occasionally reset the Num Lock default state or overwrite custom layers. Hold Fn + Alt + P for three seconds to reset key assignments, then toggle Num Lock once. If the numpad still does not register, reflash the previous firmware version from Ducky's official support page and retest.
Can a single bad diode kill all numpad keys?
Yes, if the failed diode is on the shared matrix entry row or column that feeds the entire numpad cluster. A single open 1N4148 at the junction point of the numpad's first row will make every key in that row read as dead, which on a standard layout is Num Lock, Numpad Divide, Numpad Multiply, and Numpad Minus simultaneously.
My Aula keyboard numpad not working but the rest of the keyboard is fine. Is it the PCB?
On Aula F75 and F87 models, check the trace near the bottom-right PCB mounting screw first. That screw hole sits directly over the Numpad 3 column trace and stress cracks are common there. Also inspect the ribbon cable connector if your model uses a daughterboard for the numpad — reseat the ZIF connector and confirm the locking tab is fully closed.
How do I know if the problem is the switch or the socket?
Pull the suspect switch and insert a known-good switch from a working key position into the dead socket. If the replacement switch also fails to register, the socket or the PCB trace below it is the fault. If the replacement switch works, the original switch has a bent or corroded pin — straighten the pin with needle-nose pliers or replace the switch.
Does the mechanical keyboard numpad not working issue affect wireless mode differently?
On 2.4 GHz wireless boards, a dead numpad in wireless mode but functional in wired USB mode points to a firmware polling issue or a corrupted wireless profile, not hardware. Re-pair the dongle by holding the pairing button for six seconds, then retest. If the numpad works in wired mode and fails wirelessly, the wireless firmware profile for that key cluster needs to be reset or reflashed.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard Tester