Router Reboots When Several Devices Start Video Calls

Router stays stable at idle but restarts during multiple active calls. A partial failure matters: one capability still functions, while a closely related step does not. This guide focuses on isolating that difference in wi-fi and routers, not on indiscriminate resets. Use the known-good behavior as your control, change one variable at a time, and retest the original scenario after each intervention.

Quick decision path

Baseline test: Check uptime and power supply temperature immediately after reboot. Record the current device model, OS or firmware version, and whether this occurs with one file, account, network or source. A reproducible contrast is more informative than a vague message such as “not working.” If the control fails too, stop treating this as a feature-specific problem and investigate the shared dependency first.

What the evidence means

Correction without unnecessary resets

Route A — Correct the observable mismatch

Install supported firmware and test with fewer simultaneous calls while improving ventilation. Start only after capturing the baseline. When the recommended control is not present on your model, look for its supported equivalent in the product documentation rather than following screenshots from another version.

Return immediately to the failing task and check whether the outcome changed. If it did, preserve the working setting and avoid piling on additional changes. If it did not, undo the change where appropriate before moving to deeper checks.

Protect your setup: Do not substitute incorrect voltage or polarity power supplies. Keep the current SSID, encryption, DNS and router configuration documented. Use a trusted network and never weaken firewall or WPA settings just to make a test pass.

Advanced isolation and compatibility

Route B — Test the underlying dependency

Check system log around reboot and test known-compatible power adapter of exact rating. This advanced comparison is worthwhile only if the simple check did not resolve the problem. The first two possibilities to separate are weak power adapter causes voltage drop and firmware crash under traffic load. Do not interpret their presence as proof of a diagnosis; a compatible device and a partially failed service may coexist.

Route C — Handle a limitation or persistent fault

A third explanation is router thermal problem. Check whether the feature requires particular hardware, account privileges, region settings or source formats. When a feature is unsupported, there may be no legitimate settings-only fix; use the vendor-documented alternative rather than an unsafe workaround.

Verify the result

Success looks like this: Router uptime stays stable through comparable multi-call workload. Run this check on the same device and account that originally failed. A different device passing is useful as a comparison, but it does not prove the original issue is fixed.

What to check if it still fails

Before contacting support, collect the exact model and version, the outcome of the baseline test, and whether the controlled correction changed anything. Keep passwords, private media, account identifiers, serial numbers and network keys out of screenshots or shared logs. Do not substitute incorrect voltage or polarity power supplies.

After the fix

Repeat the original action once under normal conditions and once after a routine reconnect or reopening, if relevant. Router uptime stays stable through comparable multi-call workload. Keep a brief note of the app, input, account or firmware state that changed so you can recognize a recurrence.