A smoking computer circuit board sits open beside a diagnostic screen as lightning flashes outside.
A reader's tale from The Register's "On Call" column shows how a Windows modem test can pass while the hardware is damaged. It's a good reminder that a clean software result doesn't mean a healthy device. It's also a fun story: a dial-up modem, a senior exec, an essay-writing side hustle and a lightning storm.

A smoking computer circuit board sits open beside a diagnostic screen as lightning flashes outside. The story as The Register tells it​

The column comes from a reader called "Lachlan," a pseudonym assigned by The Register. He did tech support for a senior executive who had a side business writing essays for Japanese university students at UK universities. The executive suddenly couldn't send or receive email. That was a real problem for the side business.

The incident happened in the dial-up era, so Lachlan reasonably suspected the modem. His checks went like this:

  1. He checked the network settings and found nothing wrong.
  2. He checked the cables and confirmed the phone line had a dial tone.
  3. He opened the modem's properties in Windows Device Manager. He used the advanced option that sends low-level AT commands to the modem and reads its responses.
  4. Windows reported the modem as healthy.

He then decided to replace the modem anyway. When he opened the PC, he caught a faint scorched-circuit-board smell. He also saw a black soot mark where the modem's line-protection chip sat, between the phone line and the sensitive chips. In his words, the chip had been vaporized.

He asked the executive when the email had stopped working and whether there had been any storms. The executive said it stopped while he was watching an impressive lightning display. Lachlan's verdict was that the chip "sacrificed itself for the greater good."

This is one reader's recollection. The Register didn't verify the modem model, the part involved, the electrical path or any measurements. Lachlan's "70V" figure for BT's line voltage is his own recollection. Treat the lightning explanation as plausible and unproven.

What the Windows test actually checks​

This isn't a case of Windows lying. In the Windows versions of that era, the modem's Diagnostics tab had a "Query Modem" button. The steps were: open Device Manager, expand Modems, open the modem's properties, click the Diagnostics tab and click Query Modem. Clicking the button returns responses from the modem.

A TechRepublic walkthrough says the button sends the same AT commands to the modem that you could type by hand in HyperTerminal. A Dynabook support page says that if the window lists AT command responses, the modem is correctly installed.

Those descriptions share a limit. The test confirms that the operating system can talk to the modem and get answers. It doesn't confirm that the modem can complete a call. Anyone who has seen a printer answer every status query and still jam on page one will understand.

The same sources show where the line sits. A Windows XP administration guide describes the test as a way to scroll through the output and look for errors. A community answer on a help forum says populated Command and Response columns mean the modem is "probably working." Both are cautious, and the caution is justified. A Dell diagnostic utility went further and tested for a dial tone, which suggests the vendor knew that talking to the modem is a separate matter from dialing out.

I can't tell from the column what Lachlan's modem still did after the damage. A modem's command-processing side can plausibly keep answering while the line-interface side is dead. That is an inference from how modems are built, not something the column establishes.

Why the protection chip took the hit​

Analog phone lines carry signaling voltages as well as voice, and a modem's line interface has to survive abuse. I couldn't retrieve the Analog Devices application note on modem line protection, so I'm relying on the research notes' summary of it. The note says modem line interfaces need protection from lightning, electrostatic discharge and accidental contact with mains power. It describes layered protection, with protection parts that act at a high threshold between the line's two conductors so they don't trigger during normal ringing. The general mechanism in Lachlan's story is plausible. That is a long way from proof that this chip failed that way.

Practical takeaways​

  • Treat a software pass as one data point. A passed query tells you the device and driver are talking. It doesn't tell you the device can do its real job, so test the real function too, such as placing a call.
  • Use your nose and eyes. A burnt smell or soot marks mean stop. Unplug the equipment from power and the phone line, and replace it or hand it to a qualified technician. This is general safety advice, not something the column says.
  • Ask about the weather. Lachlan's best diagnostic question was "when did it stop, and what was happening then?" Storms, power cuts and recent hardware moves often explain a sudden failure.
  • Isolate the line from the equipment. BT's current business guidance for phone faults says to unplug everything from the sockets, including PCs, faxes and modems. Then plug a working corded phone into the main socket. If calls work, the fault is likely in one of your pieces of equipment. If the phone fails at the main socket, BT's guidance has you try the test socket. If it fails there too, the fault is with the line and you report it to your provider. This is modern BT guidance, not what Lachlan did.
  • Use surge protection that covers the phone line. This is my own recommendation, not the column's. A mains-only surge strip doesn't protect a line that enters the PC through the phone socket. Many modern broadband setups still include a line path, so check what your protector covers.

Why this matters now​

Dial-up modems are gone from most desks, but the lesson carries over. Windows and vendor tools report what a driver or interface can see. A passing result from a health tool, a disk SMART status or a network adapter diagnostic can sit alongside a physical fault. When a "healthy" device still fails at its job, trust the symptoms and inspect the hardware.

That's what Lachlan did. The software said the modem was fine, but he opened the case anyway.

 

References

  1. Windows said modem worked fine. That unmistakable scorched electronics smell suggested otherwise The Register 2026-10-23T05:26:00+00:00
  2. Step-By-Step: How to use the HyperTerminal tool to troubleshoot modem problems - TechRepublic techrepublic.com
  3. I have a fault on my phone line. How do I test my equipment or wiring? | BT Business business.bt.com