10Mbps ethernet problem on Groove 52 A

Hi!
I have a problem with my Groove 52A- ethernet port automatically switched to 10Mbps during working. If i try switch it to 100Mbps manually - link down. I replaced cable - nothing changed. Sometimes, after reboot i see in WinBox, that the link is 100Mbps again. I tested it with BTest utility result is 60-95Mbps, suddenly link down to 10Mbps and after this it not return to 100Mbps even by manually option. I tested cable by TP-Link router - all ok- stable 80-90Mbps, no losted packets. Cable’s length is around of 8-10 meters. 21,5 volts of power in WinBox. I updated Router OS to last version- 6.18 - nothing changed=( Groove connected to Mikrotik 751-2Hnd. Sample of my Log file:

02:04:41 interface,info ether1 link down 
02:05:04 interface,info ether1 link up (speed 10M, full duplex) 
02:05:04 system,info dns changed 
02:05:04 dhcp,info dhcp-client on ether1 got IP address 192.168.2.100 
02:05:08 interface,info ether1 link down 
02:05:16 hotspot,info,debug 2048-30-6-dt59sz (192.168.100.9): trying to log in by cookie 
02:05:16 hotspot,account,info,debug 2048-30-6-dt59sz (192.168.100.9): logged in 
02:05:31 interface,info ether1 link up (speed 10M, half duplex) 
02:05:32 interface,info ether1 link down 
02:05:53 interface,info ether1 link up (speed 10M, full duplex) 
02:05:55 interface,info ether1 link down 
02:06:18 interface,info ether1 link up (speed 10M, full duplex) 
02:06:19 interface,info ether1 link down 
02:06:28 interface,info ether1 link up (speed 10M, half duplex) 
02:06:29 interface,info ether1 link down 
02:06:40 interface,info ether1 link up (speed 10M, full duplex) 
02:06:41 interface,info ether1 link down 
02:06:48 system,info,account user admin logged out from 192.168.3.1 via winbox 
02:07:02 interface,info ether1 link up (speed 10M, half duplex) 
02:07:03 interface,info ether1 link down 
02:07:24 interface,info ether1 link up (speed 10M, half duplex) 
02:07:25 interface,info ether1 link down 
02:07:48 interface,info ether1 link up (speed 10M, full duplex) 
02:07:48 dhcp,critical,error dhcp-client on ether1 lost IP address 192.168.2.100 - received NAK from dhcp server 192.168.2.1 
02:07:48 system,info dns changed 
02:07:49 system,info dns changed 
02:07:49 dhcp,info dhcp-client on ether1 got IP address 192.168.2.100 
02:07:52 interface,info ether1 link down 
02:08:10 interface,info ether1 link up (speed 10M, full duplex) 
02:08:10 dhcp,critical,error dhcp-client on ether1 lost IP address 192.168.2.100 - received NAK from dhcp server 192.168.2.1 
02:08:10 system,info dns changed 
02:08:11 system,info dns changed 
02:08:11 dhcp,info dhcp-client on ether1 got IP address 192.168.2.100 
02:08:13 interface,info ether1 link down 
02:08:19 interface,info ether1 link up (speed 100M, full duplex) 
02:08:25 dhcp,critical,error dhcp-client on ether1 lost IP address 192.168.2.100 - received NAK from dhcp server 192.168.3.1 
02:08:25 system,info dns changed



jan/02/1970 02:00:26 system,info verified user-manager-6.18-mipsbe.npk 
jan/02/1970 02:00:28 system,info installed user-manager-6.18 
jan/02/1970 02:00:40 interface,info ether1 link up (speed 100M, full duplex) 
jan/02/1970 02:00:40 system,info item added 
jan/02/1970 02:00:40 dhcp,info dhcp-client on ether1 got IP address 192.168.3.3 
jan/02/1970 02:00:45 wireless,info BC:85:56:13:F0:43@wlan1: connected 
jan/02/1970 02:01:02 wireless,info 44:6D:57:7A:F7:0D@wlan1: connected 
jan/02/1970 02:01:09 wireless,info 30:14:4A:1A:1D:1D@wlan1: connected 
jan/02/1970 02:01:11 wireless,info C0:14:3D:D9:3C:6D@wlan1: connected 
jan/02/1970 02:01:12 dhcp,info dhcp1 deassigned 192.168.100.12 from C0:14:3D:D9:3C:6D

probably is simply broken…