RT-BE92U Persistent Thermal Zone Faults

[RicoSuave]

First post here so bear with me if I miss anything. Since purchase, my RT-BE92U has been plagued with the same issues others have posted here. Up until the new firmware version dropped, I was having constant problems with network stability. I am currently running the latest firmware version (3.0.0.6.102_37435) and a lot of the issues seem to have been resolved except for one. Before the firmware update, I was seeing intermittent thermal zone errors in the system log. Since applying the update, I am consistently getting the following errors that appear every 3 seconds exactly:

Jan 4 18:29:52 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Jan 4 18:29:52 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Jan 4 18:29:52 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Jan 4 18:29:52 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)

On occasion, the errors coincide with a drastic decrease in wireless network performance. Under normal conditions, when connected to the 6GHz network, my wireless network download speed averages around 1100Mbps. This will drop to a nearly unusable 2-3Mbps. The 2.5GHz and 5GHz networks also see a decrease in speed to around the same 2-3Mbps. Wired clients seem unaffected. Once I perform a hard reset to the router, it seems to correct the speed issue for a while, but the thermal zone errors continue to persist. This seems to happen anywhere from once a week, to every day. Performing a hard reset isn't something I want to nor should have to keep doing to correct the issue every time it happens. Please let me know if there is anything else I can do to stop this from happening. I am getting very close to returning this router and exchanging it for a different brand. Thanks.

[Harriscd]

I've updated to 37500 and so far have 1d 8h up time without thermal errors. Never had stability issues with wifi while experiencing thermal logs, so maybe a difference with mine. I did not enable features which were off by default from the last hard reset. Did not hard reset after current update.  All 3 bands are On, plus an additional IoT ssid. I've reduced nightly reboots to 2x per week and may consider disabling that altogether to see how long it goes.

[senyk92]

After getting to 37500 and factory resetting, my router did still experience maxed out CPU's, thermal issues, and rebooting - I gave up on it and am returning it now, just doesnt seem worth it. Hate going to TP-link with the pending ban but cant deal with inconsistant internet while hopeing asus gets ontop of this.

[Lid]

I've been on 37748 for a bit and ASUS asked me to try 37803. I've got the file but not risked it yet as this is just taking up too much time being a lab rat.  37748 is stable enough but that's keeping most useful settings turned off.  Log file is still a disaster with so many deauth messages (like Feb 19 18:13:55 kernel: WLC_SCB_DEAUTHORIZE error (-30)) it's hard to find any sense!  No thermal and no CPU spikes. Wifi stability remains the biggest failure point.  I have had to put my desktop on awful homeplug ethernet as it's more reliable than the BE92U wifi.  Yuck!

[DannyXCM]

I have the exact same error ("WLC_SCB_DEAUTHORIZE error (-30)") on the latest firmware-37500.  Very frustrating, i'm not sure what to do- return the router or keep holding on.  It's like they are beta testing this thing with us. These errors should have been fixed by now; it's been months since this thing is on the market. 

[fairfacts]

Lid I think you actually may have bad hardware. I am only left with the thermal issue on 02 and yours seems to behave differently.

Look carefully at the deauth errors. Normal activity of devices joining and leaving the network is logged - check and see if the MAC address is the router or an external device.