This probably means either there is a problem with your environment, configuration of the devices or the router. This is not a FW issue here.
The way I see it no configuration setting or client device should be able to cause a reboot with properly written firmware (short of going through the management console to invoke a reboot). I'm certain there isn't any FW for any device that is 100% bug free but not having spontaneous reboots isn't an unreasonable expectation. Configuration issues and misbehaving devices should be handled by the router more gracefully than crashing and burning. Proper error handling is part of any good design.
Maybe someone can review your router settings with you using Link> teamviewer if your interested. Its safe and secure.
The only thing worse than me spending more time on this is to have me
and someone else spend more time on this.
My configuration is fairly simple.
Start with default settings
+ mixed 802.11n/g, WPA2 only, AES
+ all devices using DHCP reserved IP's
+ port forwarding on 1339-1340 TCP to a reserved IP
The above was stable on 2.07 with many months of uptime. The only time I need to reboot it (deliberately) was after guests come over and bump up the number of wireless clients, after which I couldn't connect with certain devices (Win7 PC and BB Z10). Other Win7 PC's and various devices never have issues.
I have not seen any wireless issues on any build with my 655 Rev B.
Did you factory reset the router before and after when upgrading and downgrading the FW then set up from scratch?
I didn't do factory reset before the upgrade but I did a factory reset after and reconfigured from scratch. If I decide to give it one more kick at the can I'll try the factory reset before the upgrade as well.
Thanks for all the help you provide in this forum.