I am randomly getting reboots on the device, the longest it manages to stay running is about 4 hours and then it will just reboot. I have the following in the 'sys ver dbg' output. Any clues anyone?

Router Model: Vigor2860n+ Version: 3.8.9.3_BT English
Profile version: 3.0.0 Status: 1 (0x482a57ec)
Router IP: 172.16.25.254 Netmask: 255.255.255.0
Firmware Build Date/Time: Aug 29 2018 15:38:11
Router Name: xxxxxxxx
Revision: 76226 V389_2860
Current VDSL2 Firmware Version: 05-07-06-0D-01-07
ADSL Firmware Version: 05-07-02-08-00-01 Annex A
VDSL2 Firmware Version: 05-07-06-0D-01-07

---

firmware exception debug info

---

EPC=80a87f34, Cause=00800028, Status=1100fc03, BadAddr=00000003, RetAddr=80a2405c
exception id=10(RI: Reserved Instruction)
exception occured in TASK Lavel
task_id=114, SP=0x816b2110(4306 bytes free, 1192 used bytes)
system tick =1698
CURRENT_VERSION : 3.8.9.2_R
get from address : 80004000
Dump CPU registers:

---

$ 0: 00000000 899c0000 08000000 00000003
$ 4: 08000040 00000000 00000200 83ea2920
$ 8: 00000000 08000200 00000000 00000000
$12: 822d3ffc 1100fc01 80eb8178 ffffffff
$16: 08000000 01798000 00000001 00000003
$20: 00000020 00000008 824660e0 81ad6348
$24: 00000000 80a0f1f4 00000000 fff9c6f9
$28: 815fe000 816b2110 819c0000 80a2405c
List a possible caller functions:

---

func( 0)=80f764dd
func( 1)=80a82294
func( 2)=80f72d9d
func( 3)=80a820f4
func( 4)=80ffcaae
func( 5)=80a82294
func( 6)=80033bc4
func( 7)=80eb8178
func( 8)=80033e1c
func( 9)=80a24194
func(10)=80065c80
func(11)=80706998
func(12)=80ffcaac
func(13)=800671c0
List backtrace functions:

---

func( 0)=80a87f34
func( 1)=83c56149

If you're seeing debug log information, that means it's an unexpected crash, typically caused by a firmware problem. However I've just noticed - the firmware shown in the debug message is the previous firmware version (3.8.9.2), which means these crashes are either not being caused by the firmware (power supply?) or the router isn't able to log the fault (less likely, but could also indicate power issue).

I recommend contacting the support team for assistance with the problem regardless. I also recommend checking the router's syslog output as that may list repeating events preceding each crash, which would give good ideas on what the main cause could be.