Please try this new BIOS. It can be installed with Xmodem transfer protocol from your terminal program (hyperterminal):
This BIOS atualization will fix the reboot problem ???
Normis, do you recommend the new BIOS’s instalation even at the boards that are ok?
yes the bios will fix this problem,
you can install this bios even on good boards.
Any way to do it remotely? it’s easy to add on the new boards… a little bit harder on the ones already installed 
just put file to root on your RB and do:
/system routerboard print (upgrade firmware: 2.13)
/system routerboard upgrade
/system reboot
Normis: thanks, we will test it.
Normis, We upgraded both OS and firmware. We are applying RB600 mainly outdoor. We noticed that polling and “disable CSMA” are both disabled. Only Nstreme is enabled “on wds-bridge side”. When we are using bridge mode it is appearing again!!
We are using R52. can you chek it!!
please contact the support@mikrotik.com about this issue with detailed info.
I have one RB153 with the same rebooting problem of some RB600. Can I try to instal this BIOS atualization on that board ?
no, this problem is entirely related to the RB600, your problem must be different. contact support for help. this BIOS file is only for Rb600
I succesfully upgraded the firmware to v 2.13 and the random reboots totally disapear.
But now I have two minor issues. In winbox appears to be disabled enable polling and disable CSMA also framer policy and framer limit too, this is only on winbox, in the console everything is ok. The other issue is that the ether1 reports inconsistents traffic values.
iterlink,
this is specially made so, because you don’t need to change those values if the wireless interface is in the station mode. Those seetings are only needed for the AP interface as the AP interface will tell it’s clients what nstreme settings to use.
So, that is what I was saying before…OK.
But kindly include the new bios upgrade into 3.7 package because we have already have cutomers running on RB600 on outdoor units which hardly to do xmodem on them.
If so, when this can be done?
Hi guys and thanks to Normis…
Like k3dt said… Load the file to the root
/system upgrade
/system reboot
We did this remotely to ALL our RB600’s (we were not having any problems but upgraded anyway) and it worked a treat..!!!
As an aside - I doubt whether new fixes would be issued which could not be installed across the network…??? Pretty pointless if you “might” have to travel 1000 kms to a BSS… so again.. thanks for the upgrade..
Regards
Tanker
Is it good for 333 board?
read the topic again!
its only for rb600
If you experience the same symptoms like for RB600 board, then please contact the support@mikrotik.com with a detailed description and the support output file after the reboot issue.
Reboot Problem still there!
We had firmware V 2.13 for all the weekend and board was rebooting for no apparent cause.
So this morning i’v try to upgrade to 2.14…
5 min later board was rebooting again…
12 min later again
After that i had this line in log
system error critical : router was rebooted without proper shutdown (cause 1)
Now up for 34 min and still working
Setup is
RB600 with 4 WMR-400 Card in it.
3 card in 5.8Ghz mode Ap-bridge and
1 card in 2.4Ghz Mode Station.
Power Supply 20V 3A In Power jack
routerboard: yes
model: “600”
serial-number: “160201xxxxx”
current-firmware: “2.14”
upgrade-firmware: “2.14”
uptime: 19m54s
version: “3.4”
free-memory: 49656kB
total-memory: 62416kB
cpu: “e300c1”
cpu-count: 1
cpu-frequency: 399MHz
cpu-load: 37
free-hdd-space: 32148kB
total-hdd-space: 61440kB
write-sect-since-reboot: 162
write-sect-total: 232281
bad-blocks: 0
Any idea?
Samuel Allard
Digicom Technologies
upgrade to latest version