Checksums are rarely wrong, so look at the checksum value in the trace. If it is TCP and 0000 (zeros) then the problem is probably bogus. The source of this is usually the fact the TCP checksums-offload are enabled in the NIC driver and so many of the packets (the ones to/from this machine) have their checksums not calculated until the actual NIC gets ready to transmit the frame.

Wireshark sees the packet before the checksum has been added. When the packet is transmitted on the wire, the checksum is correct. One clue that checksum offload is involved is that the packets with the errors don’t get retransmitted. If the checksum really was wrong, either the packets would be retransmitted, or the communication would fail. OpenVPN / Re: [Openvpn-users] Incorrect tcp and udp Operations Management. ERP PLM Business Process Management EHS Management Supply Chain Management eCommerce Quality Management CMMS Manufacturing Mailing List Archive: packet capturing question / TCP Jan 27, 2006

TCP_Checksum_Verification - The Wireshark Wiki

TCP_Checksum_Verification - The Wireshark Wiki TCP Checksum Verification. By default and whenever possible Wireshark will verify whether the TCP checksum of a packet will be correct or not. 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 checksum errors on compute nodes - Mirantis

Fix Udp Checksum Error Linux (Solved) -

Jul 11, 2012 cisco - header checksum error in wireshark - Network