I lost about 48TB of data because of this issue. :/ The issue started happening to me when I was on a older version for over a month. I didn't upgrade or change anything and started having this chunkid="" issue. Stablebit is not finding chunks that do actually exist in Google Drive.
Open the technical details windows, and click on the "service logs" button.
This will open up a new window that will show the service log output. Click on the "Tracing levels" button, the "C" group and open the "Chunk ID helper" section. Select "Verbose" and then reproduce the issue.
Once you do the above you will most likely see something like this:
22:15:26.3: Information: 0 : [ChunkIdHelper:84] Chunk 366031 read (State=Found, ChunkId='')
22:15:26.5: Information: 0 : [ChunkIdHelper:89] Chunk ID for chunk 366031 is '' (via cache)
22:15:26.5: Information: 0 : [ChunkIdHelper:89] Chunk 366031 read (State=Found, ChunkId='')
If you see the above with ChunkId="" then you are affected by the same issue as me and a few others. Again, the chunk exists on Google Drive (I have verified this many times) but stablebit doesn't find it which causes corruption.