This is due to TCP Checksum offloading often being implemented on those NICs and thus, for packets being transmitted by the machine.
If you capture on a recent Ethernet NIC, you may see many such 'checksum errors'. There are causes where you might see lots of checksum errors. TCP checksum offloading (lots of checksum errors) Still, it should be VERY rare to see this for packets that actually are corrupted. It should be VERY VERY rare to see corrupted packets in today's networks unless you have a router or a switch with a bad RAM module with a sticky bit. But then again, short packets will be ignored by the desegmentation engine anyway.
The TCP checksum will only be tested for packets that have been fully captured, and thus for short packets, the checksum will not be verified. these packets will be ignored by the TCP_Reassembly engine and reassembly will not work. TCP packets that have invalid checksums will be marked as such with a warning in the information column in the summary pane and also, most important, if the checksum is BAD that tells wireshark that the packet is corrupted and it will NOT be included in any TCP_Reassembly. By default and whenever possible Wireshark will verify whether the TCP checksum of a packet will be correct or not.
