Hi,
i have tested with & without download manager, both in Internet Explorer 8 & Firefox.
also tested in safe mode + net with the same result.
also noticed that not only compressed files are corrupted. if you download movie you don't know if its corrupter because maybe one or two frames will be wrong but the movie will work, only if you compare with MD5 the file you know that its bad.
Apparently you are using x64 - 4gb mem. I only use IE8. need more info. trying to find if the MTU can be set differently. Most corruption if not by (rouge) AV. then it can be lost packets, due to MTU being set to high.
PS: Have you tested with only 2GB Memory?
A packet test can be :
orb -> cmd (run as admin) ping the ip
sample is: ping
www.microsoft.com
this sends a 4 count (default) to MS and if you have any packet loss it will show you.
sample:C:\Windows\system32>ping
www.dhcnetwork.com
Pinging dhcnetwork.com [208.101.21.58] with 32 bytes of data:
Reply from 208.101.21.58: bytes=32 time=30ms TTL=52
Reply from 208.101.21.58: bytes=32 time=27ms TTL=52
Reply from 208.101.21.58: bytes=32 time=28ms TTL=52
Reply from 208.101.21.58: bytes=32 time=28ms TTL=52
Ping statistics for 208.101.21.58:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 30ms, Average = 28ms
Please do not ping me - the responder will switch to redirect and that will mess up the count. Ping some big place or the IP where you are trying to get a movie or driver.
this is a 12 count to rose.com
C:\Windows\system32>ping -n 12
www.rose.com
Pinging rose.com [209.237.150.20] with 32 bytes of data:
Reply from 209.237.150.20: bytes=32 time=64ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Reply from 209.237.150.20: bytes=32 time=62ms TTL=24
Reply from 209.237.150.20: bytes=32 time=64ms TTL=24
Reply from 209.237.150.20: bytes=32 time=64ms TTL=24
Reply from 209.237.150.20: bytes=32 time=64ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Reply from 209.237.150.20: bytes=32 time=88ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Reply from 209.237.150.20: bytes=32 time=63ms TTL=24
Ping statistics for 209.237.150.20:
Packets: Sent = 12, Received = 12, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 88ms, Average = 65ms
-------------------------------------------------------------