here's a copy of my reply to your same question on the OBD11 forum:
"^^^ Please don't take offense - but I seriously doubt that those code-string changes could be made to your car and the car still works!!
Even if there were genuine attempts to make these amendments, most of the changes are impossible because the amended values impose a very different Byte count on the modules.
While I'm sure that the crazy, zany software guys/gals @ VOLTAS IT do their best to ensure that these history reports are accurate - the veracity of the information is really dependent on when the snap-shot of values is taken. For example, for VCDS, the data for the equivalent reports is locked-in just before the user presses the "Doit!" button - which is the same as the green tick in OBD11. This means that the history reports in VCDS show what the user asked the module to change - the reports don't show what actually changed! I don't know when OBD11 takes the data snap-shot for these reports - it could be the same as VCDS - perhaps if anyone from VOLTAS IT is reading this. they might respond?
What were you doing to the car @ about 1722 hours on 2018-11-26 (i.e. about 6 months ago)?
I suggest that you make a scan report of the car. Then perhaps check the code-string values on the modules in the scan report with those in the history report.
Don
Read more:
http://forum.obdeleven.com/thread/6070/history-long-coding-changes-make?page=1#ixzz5pGzZo0Jx