How to fully recreate database in MS SQL server 2016 from exported data
This is only a summary of some vague assumptions as a lot of details that should be added to the question were either discussed in a chat or have not yet been asked.


** Before you continue**

Create a database backup (WITH CHECKSUM) and store this database in a safe location. Even better: Seeing as your disk might be faulty, backup the database (WITH CHECKSUM) to an external drive and store in a safe location.

Possible reasons for data corruption on data growth




Your SSD disk has corrupt areas. DBCC CHECKDB... corrects the data (albeit with REPAIR_ALLOW_DATA_LOSS). Adding data places it in the corrupt areas of the SSD even though the SSD controller unit should avoid corrupt areas (once marked).


Solution: Check SSD S.M.A.R.T. parameters for errors and/or replace SSD.  

Reference: How to See If Your Hard Drive Is Dying with S.M.A.R.T. (How-To Geek Site)




Your motherboard's disk controller (SATA interface) is having issues handling the large amount of data. 


Solution: Replace disk controller and/or update disk controller driver.




The disk and/or disk controller is set to use a WRITE CACHE mechanism which is unable to keep up with the import of large amounts of data. The corruption is occurring on flushing. 


Solution: Turn off (disk) cache mechanisms.  

Reference: Disable Windows Disk Write Cache for Data Integrity and Better Performance (Long White Virtual Clouds)



General Reference: Data corruption (Wikipedia)