GT-AX11000 keeps crashing after every few days (WiFi so it seems), and need to hard-reboot to get it working again

[Power2All]

see if you can find a replacement AC/DC adapter that fits as well. Use the DC voltage and current spec on the existing one .

Tip diameter and polarity are the tricky part of the spec. which ASUS doesn't specify, sadly.

Yah no worries, but for the moment I have no replacement yet.

 

[Power2All]

I've now installed:
GT-AX11000_3.0.0.4_388_24403-gd4e3d0c_ubi.w

See if this stays stable.

 

[Power2All]

Good news, so far I haven't seen it crashing yet.
Last time it even crashed within a day.
Perhaps this is something for the developers to look into, where this instability comes from in the release after the one I use now ?
See what has changed, and/or what could be causing it.

 

[John Fitzgerald]

Good news, so far I haven't seen it crashing yet.
Last time it even crashed within a day.
Perhaps this is something for the developers to look into, where this instability comes from in the release after the one I use now ?
See what has changed, and/or what could be causing it.

You may want to try the new Beta firmware, here:

Beta - Asuswrt-Merlin 3004.388.11 Beta is now available

Asuswrt-Merlin 3004.388.11 beta is now available. The focus of this release is merging a new GPL (largely security fixes), the removal of AiCloud due to repeated security issues, and the new Traffic Monitor redesign that was initially introduced in 3006.102. Changes: 3004.388.11...

www.snbforums.com

 

[Power2All]

You may want to try the new Beta firmware, here:

Beta - Asuswrt-Merlin 3004.388.11 Beta is now available

Asuswrt-Merlin 3004.388.11 beta is now available. The focus of this release is merging a new GPL (largely security fixes), the removal of AiCloud due to repeated security issues, and the new Traffic Monitor redesign that was initially introduced in 3006.102. Changes: 3004.388.11...

www.snbforums.com

I'll give it a shot, thanks for the tip

 

[John Fitzgerald]

I'll give it a shot, thanks for the tip

When going from stock firmware to RMerlin firmware, after you flash RMerlin you need to do a Factory Reset through the GUI to start clean. Do not import any old settings, start from scratch.

 

[Power2All]

When going from stock firmware to RMerlin firmware, after you flash RMerlin you need to do a Factory Reset through the GUI to start clean. Do not import any old settings, start from scratch.

Done, I did also a factory reset as said by you.
Let's see if it stays up for this week, I'll update here if I either got another crash, or if it works stable for a week.

 

[cjb4]

I had a similar problem, I fixed it by having my router reboot on its own every 2 days. When that worked I now have it reboot once a week at 2AM on mondays.

 

[Power2All]

I had a similar problem, I fixed it by having my router reboot on its own every 2 days. When that worked I now have it reboot once a week at 2AM on mondays.

Yah but I rather have a permanent solution, then a temporary fix.
Yours I have been thinking about, until it crashed within 1 or 2 days...

 

[cjb4]

Yes agree, but it got me thru the next firmware version which seemed to fix the problem.

 

[Power2All]

Sadly, the latest BETA (3004.388.11_beta1_rog) is also a dud.
It crashed now twice in the span when I notified about the installation (21 december 2025).
I'm downgrading again to GT-AX11000_3.0.0.4_388_24403-gd4e3d0c_ubi.w as that one was not crashing last time.
I've attached the log of the system, hopefully people can find the issue:

 

[128bit]

. . . just my 2 cents but there are a lot of us with gt-ax11000s and the fw's fine. so i'm not sure i'd go down that rabbit hole. sad as it is, you may have to replace the hw again. consider buying one off the shelf, perhaps a best buy. you'll have a window to return it.

 

[Power2All]

. . . just my 2 cents but there are a lot of us with gt-ax11000s and the fw's fine. so i'm not sure i'd go down that rabbit hole. sad as it is, you may have to replace the hw again. consider buying one off the shelf, perhaps a best buy. you'll have a window to return it.

I'm not from the US, and this device was very expensive.
Otherwise I'll keep it at a lower firmware, since the one I use now, was up for a week without a hitch.
So something is still up with the firmware, but I do have a lot of traffic coming over it, so perhaps most users don't have it in use as much as I do (home server which is getting a lot of traffic).
But from my understanding reading the logs, and letting AI read the logs, it all points towards the Broadcom chipset crapping out (or instable driver).

 

[Webheadfred]

Are you using a Firestick by chance? There is a known Amazon <-> Broadcom incompatibility issue. The MAC address decoded to some sort of Amazon device.

Amazon Wi-Fi stacks are well-known for

Poor WPA3 support (especially mixed WPA2/WPA3).
PMF (802.11w) negotiation bugs.
Aggressive reconnect behavior.
Retry storms instead of backing off.

Edit:
I had a similar issue with my GT-BE98 Pro. I had to isolate all my Amazon devices to a Amazon VLAN with Amazon friendly settings. It’s completely stable now.

 

[Power2All]

Are you using a Firestick by chance? There is a known Amazon <-> Broadcom incompatibility issue. The MAC address decoded to some sort of Amazon device.

Amazon Wi-Fi stacks are well-known for

Poor WPA3 support (especially mixed WPA2/WPA3).
PMF (802.11w) negotiation bugs.
Aggressive reconnect behavior.
Retry storms instead of backing off.

Edit:
I had a similar issue with my GT-BE98 Pro. I had to isolate all my Amazon devices to a Amazon VLAN with Amazon friendly settings. It’s completely stable now.

I have no USB in use.
Here a image.

 

[128bit]

I'm not from the US, and this device was very expensive.
Otherwise I'll keep it at a lower firmware, since the one I use now, was up for a week without a hitch.
So something is still up with the firmware, but I do have a lot of traffic coming over it, so perhaps most users don't have it in use as much as I do (home server which is getting a lot of traffic).
But from my understanding reading the logs, and letting AI read the logs, it all points towards the Broadcom chipset crapping out (or instable driver).

my bad here. after re-reading and seeing your pic, i just realized you are not talking about the "pro." something to consider btw, if opportunity knocks
sorry.

 

[Webheadfred]

I have no USB in use.
Here an image.

I’m referring to any Amazon devices like an Amazon Echo, or an Amazon Firestick for TV, or an Amazon Smart Plug. These devices don’t connect physically to the router; rather they’re devices connected to your network. They can wreak havoc on your network causing this instability. This seems like a client-side Wi-Fi stack bug triggering a Broadcom driver edge case. The fix is almost always security-mode simplification — not RF tuning.

‘CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set”

This Indicates:
The Wi-Fi driver (Broadcom wl) never finishes authorizing the client.
Hostapd thinks the client is valid.
Kernel driver says “nope”.
Router forcibly deauths the client.
Client immediately retries.

Edit:
Try disabling WPA3 temporarily to see if there’s any improvement.

 

[Power2All]

I’m referring to any Amazon devices like an Amazon Echo, or an Amazon Firestick for TV, or an Amazon Smart Plug. These devices don’t connect physically to the router; rather they’re devices connected to your network. They can wreak havoc on your network causing this instability. This seems like a client-side Wi-Fi stack bug triggering a Broadcom driver edge case. The fix is almost always security-mode simplification — not RF tuning.

‘CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set”

This Indicates:
The Wi-Fi driver (Broadcom wl) never finishes authorizing the client.
Hostapd thinks the client is valid.
Kernel driver says “nope”.
Router forcibly deauths the client.
Client immediately retries.

Edit:
Try disabling WPA3 temporarily to see if there’s any improvement.

Ah I understood it wrong then, thanks for clarifying it.
I'll try upgrading again later and disable WPA3.

As for WiFi devices, I basically have 2 heating devices connected to 2.4ghz, my phone and my PS4 (who is turned of for a long while now).

 

[Power2All]

I’m referring to any Amazon devices like an Amazon Echo, or an Amazon Firestick for TV, or an Amazon Smart Plug. These devices don’t connect physically to the router; rather they’re devices connected to your network. They can wreak havoc on your network causing this instability. This seems like a client-side Wi-Fi stack bug triggering a Broadcom driver edge case. The fix is almost always security-mode simplification — not RF tuning.

‘CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set”

This Indicates:
The Wi-Fi driver (Broadcom wl) never finishes authorizing the client.
Hostapd thinks the client is valid.
Kernel driver says “nope”.
Router forcibly deauths the client.
Client immediately retries.

Edit:
Try disabling WPA3 temporarily to see if there’s any improvement.

WPA3 was already disabled, it's set on WPA/WPA2-Personal for all the WiFi frequencies.
Also turned some stuff off like WiFi6 and such, and beaming, which is what I read is only for old devices.
See if these settings does anything.

 

[degrub]

i would disable 11b protocol if you have no device using it.