To be honest I don't see what TSGUI could do better than ADF-Blitzer when creating an ADF. I assume that both programs use trackdisk.device to read from floppy and dos.library to write to a file. There is no error detection involved apart from that of the two mentioned components.
All I could think of is that ADF-Blitzer quietly ignores read errors while TSGUI informs the user and lets him choose to retry, ignore or abort. TSGUI can also be configured to automatically retry a certain number of times before the error requester appears.
Another point could be hardware and RAM integrety. AFAIK ADF-Blitzer loads the entire image into RAM and then writes it to a file at once. TSGUI reads and writes track by track. So if your RAM is not ok, it might damage the image in memory before it is written to disk. The risk that this happens is surely higher if more RAM is used and the data is kept in RAM for a longer time, i.e. for ADF-Blitzer the risk is higher than for TSGUI.
