Normally I would be inclined to blame the disc, or the scanning speed being too high (try 8x, or preferably 4x for questionable discs). But in this case it looks like the drive just has a very poor writing strategy.
The SH-S223C was a completely different beast to the rest of the 223 series. It was based on a Samsung/ARM controller chip, not Mediatek.
They were troublesome drives. IIRC, they may have had a higher than average hardware failure rate. But even healthy drives would produce results like yours (example).
The good news is that with later firmware revisions (SB05 onwards) the writing quality was a [I]lot[/I] better (and on MCC004 at least, actually quite good). The bad news is that it looks like the firmware was only released for the retail drive.
If you are comfortable with the risks (I don’t recall anyone trying this particular crossflash before), you can try crossflashing to the SH-S223C firmware. Opening up the SB07 executable (from Firmwarehq) with 7-Zip reveals that, like other Samsungs, it uses the TSDNWIN flasher. So the standard Samsung ‘-nocheck’ crossflash method [U]might[/U] work (here & here).