Try restoring the logs manually to the standby server and see what, if any, error is received.

In the past while debugging, I have found alerts set up on production systems to monitor transaction log growth. When the log is 80% full, the alert truncates the log. Of course, this was done by an an inexperienced DBA attempting to stop "transaction log full" error messages.

Obviously, this would affect log shipping.