Powershell - Are the machines running the same version(s) of Powershell?
Execution Policy - Is it different on the failing machines (e.g. different GPOs being applied?)?
Language settings - are the machine language settings different?
Others have had similar issues in the past but with earlier versions of PSADT - the issues Ive read of also encountering this issue were either fixed in v3.8.3 (so should already be fixed in your version) or it could an encoding issue of your script.
I would suggest you have a read of this - as it might give you some clues as to the cause: