Windows 7: Windows 7 Corrupting Downloaded Files

thanks myke



Are all the files ok in vista, but not in win 7?

Yeah they work great in Vista but not 7. It's definately something to do with the downloading process on 7 - I thought maybe temporary files or something? Since it effects every way of downloading something.

CRC errors in compressed files are related to I/O efficiency. The file is likely in good order until it is extracted. When the file is written to the corrupting host, is your CPU running high or hot? Is your RAM OCed?

Eliminate any application that may be scanning the file prior/during extract.

Unrar with a different utility.

I've tried both WinACE and WinRAR, I don't know any others. I don't have a firewall or antivirus or anything running at the same time. My CPU is running normally. I don't know how to tell if my ram is OC'd.

Thanks

Boot in safe mode and try - just a thought. If this works, well...

Otherwise, run Disk Cleanup.
Run chkdisk.
Throw in a defrag for good measure.

Run the memory diagnostic.

The CRC error is coming from an error in I/O - of this, I am certain. I do not how to easily isolate the disk as the source of the error. It could be in the RAM or the CPU.

Note to self - ALWAYS REMEMBER DRIVERS AS CAUSE OF MANY PROBLEMS WITH NEW OS!

I could be completely wrong. And I am not saying that all compression related CRC errors are I/O - just that this particular case presents that way.

An interesting problem, indeed. I will be away from the PC a good bit of the day.

Boot in safe mode and try what? I don't understand what you mean. I defrag once a week and chkdsk came back fine this morning when I ran it. I'll try the memory diagnostic though. But I had Vista on here and it worked fine when I downloaded/extracted, it's only since I put 7 on.

Myke

I think antman is suggesting you try unraring a file in safe mode. Since he is offline try it.
K

Ok we have great progress! The checks all came back clean but the extract went fine in safe mode! Don't know if it was just a fluke but it seemed to work perfectly. Thanks!

Any ideas on how I can do this without safe mode?

If the test is NOT a fluke, you have isolated a driver problem. First suspect, chipset.

If the test IS a fluke, well...

Duplicate the positive result to determine flukiness. Or, better yet, assume chipset driver.

Okay I tried it again and it worked fine, what can I do to fix it now?