Hello,
If we summarize the dbcc check we can important objects (e.g. sys.sysobjvalues, REPOLOAD):
CHECKDB found 32 allocation errors and 28 consistency errors not associated with any single object.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'sys.sysobjvalues' (object ID 60).
CHECKDB found 0 allocation errors and 2 consistency errors in table 'g10.COV_GENDATA' (object ID 201155862).
CHECKDB found 0 allocation errors and 4 consistency errors in table 'g10.sap_stmt_workload' (object ID 661030282).
CHECKDB found 0 allocation errors and 2 consistency errors in table 'g10.sap_stmt_plan' (object ID 789030738).
CHECKDB found 0 allocation errors and 5 consistency errors in table 'g10.D010INC' (object ID 1630628852).
CHECKDB found 0 allocation errors and 27 consistency errors in table 'g10.D010TAB' (object ID 1662628966).
CHECKDB found 12 allocation errors and 0 consistency errors in table 'g10.sap_perfinfo' (object ID 1733034101).
CHECKDB found 16 allocation errors and 184 consistency errors in table 'g10.sap_workload_snapshot' (object ID 1797034329).
CHECKDB found 0 allocation errors and 43 consistency errors in table 'g10.REPOLOAD' (object ID 1881174593).
CHECKDB found 61 allocation errors and 295 consistency errors in database 'G10'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (G10).
The safest solution would be to restore your backups in another server (different disks, memory, ...) and check if your backups did not contain those corruptions.
As mentioned in note 142731:
Investigation of causes
Theoretically, every component of a database server, either software (SW) or hardware (HW), can cause a corruption. In practice, however, a corruption can almost always be traced back to hardware or driver problems. A defect in any HW component can cause corruption. For example, disks, RAID controllers, RAM, CPU and even defective fans can cause malfunctions due to overheating.
Regards,
Eduardo