After Update, receiving DHCP error and disconnecting

Hi, Today I upgraded my HEX 750GR3 to 6.46.5.

After that, the router is giving a lot of errors trying to apply DHCP address to a Bridge interface. Freezes and disconnect.
Cannot do anything else.

The error on log is:
APSala: bridge port received packet with own address as source address (b8:69:f4:54:42:7b), probably loop

Also, I get a lot of :
LAN offering lease 192.168.88.203 for B8:69:F4:54:42:7A without success

I have 2 APs here. Each on one interface of Mikrotik.
On two of them I see the router connected on their list, but one of then shows an incorrect IP address of the router. My router has 191.168.88.1, and the one with b8:69:f4:54:42:7A (the one with DHCP error) show it has 192.168.88.102
The other, with MAC B8:69:F4:54:42:7A show correct IP address

This is my Router / Bridge MAC address

didn’t change anything, just upgraded. Firmware is also upgraded.

From time to time my connection via inbox is lost. All network activity is lost.
Please… help me…

Let me update my own case. In case I can help somebody or help understand what was happening here…

Due to urgency (home-office and remote classes) and no answers, I decided to Downgrade my router to the previous version.
Did not help. took a look on all configuration, disabled Firewall rules, nothing worked.

So I reset all configuration. Upgraded again to last version, reset configuration again and started from scratch.
In the middle of my reconfiguration session, I noted a slight difference from previous config. on of the ports on my Bridge config ware set as (sorry if this is not the term, I completely forgot) designated and the other two as backup. I don’t remember exactly it may the the oposite: one backup and two designated. On the new configuration, I have all 3 ports as designated state.

I think this configuration is due to the IP address was being set to the specific port of the bridge, not the bridge itself. I remember I had to change this configuration to set the ip to the bridge. I think this may addressed the issue, but I’m not sure, because I reconfigured everything.

I also don’t know why this configuration changed with the upgrade.