A350 UTC data gone rogue

[BoeingSpeedbird]

Long haul from Kuala Lumpur - 2 hours in and this is the UTC data. What’s going on? If I re-insert the landing airport (EGCC) and STAR then, for a short while, the UTC info corrects, but it goes rogue again quickly after. Why? On Xbox. 

Edited March 8 by BoeingSpeedbird

[AirplaneEnjoyer]

Same issue, on xbox as well. 

Before T/C, all fixes UTCs seemed fine and logical. Only issue was DEST EFOB warning was displaying. Predicted fuel at destination was about -75.  

Fixes after T/C seemed fine as well, until my first step climb, which was displaying UTC times anywhere from -30 to 30. Once auto step climb performed my first step climb, that is when all UTC times went “rogue”. 

I deleted all step climbs from “STEP ALTS” in the perf page and re-inserted STAR and approach. This brought back the VNAV path on the bottom of ND. UTC times are now jumping back and forth between logical times, and somewhere between -30 to 30 with DEST EFOB warnings turning on and off. After a little, it eventually goes back to the way the picture shows above from OP. Only way to fix is to re-insert STAR and approach from which point the cycle repeats itself. 

I purchased the A350 yesterday, and my first flight (KATL-KDFW) to figure the airplane out, did not require a step climb, and everything went smoothly. This leads me to believe it’s an issue with step climb. 

Any help or suggestions would be greatly appreciated!

Update: After going to F-PLN page, clicking destination airport, and only selecting my intended runway (STAR stayed) then inserting into flight plan, everything seems to be normal. I even inserted a step climb later in the route and there are no erroneous UTC times. No more DEST EFOB errors either. Something I didn’t notice either was my cruise speed dropped to M.81, but now is back to M.85.   Honestly not sure what I did, but any explanation/advice to avoid this in the future would be awesome. 

Edited 5 hours ago by AirplaneEnjoyer
update