I have been using F@H for about a week now and have completed about 10 WUs. Once a WU actually starts there are never any problems. However, I seem to get this problem between just about every WU, and this time it has been happening for about 12 hours or more (it usually corrects itself within a half hour or so).
Etc. etc. etc. In case you don't want to read that, the error is "Couldn't v3Decompress", then "Error: Could not open work file", then "FILE_IO_ERROR CoreStatus = 75 (117)". This happens whether I run from C:\Program Files\Folding@Home or a new installation at C:\Folding@Home, whether or not I use -forceasm, and whether or not I use -advmethods.
There is no overclocking involved and my CPU rarely hits 50 C under load from F@H.
My specs:
Shuttle SN95G5
Athlon 64 3500+ Winchester
2 x 512 MB Corsair DDR400
2 x Western Digital Raptor 36 GB in RAID 0 (C drive)
Windos XP SP2
FILE_IO_ERROR would seem to point to a hard drive problem, but the Raptors are in perfect working order and I scan/defrag them every week. The rest of my system has no problems and is totally stable, Prime95 stress-tested etc.
I looked for answers on the F@H board but it didn't help. I figured maybe you guys could lend a hand. Thanks!
EDIT: Just restarted and managed to start a WU. However, as I mentioned, this happens pretty much every time I finish one, so if you know the cause I would still appreciate hearing about it.
[16:22:43] Folding@Home Gromacs Core
[16:22:43] Version 1.70 (October 24, 2004)
[16:22:43]
[16:22:43] Preparing to commence simulation
[16:22:43] - Assembly optimizations manually forced on.
[16:22:43] - Not checking prior termination.
[16:22:43] Couldn't v3Decompress
[16:22:43] - Fatal: Could not decompress work unit data.
[16:22:43] Error: Could not open work file
[16:22:43]
[16:22:43] Folding@home Core Shutdown: FILE_IO_ERROR
[16:22:48] CoreStatus = 75 (117)
[16:22:48] Error opening or reading from a file.
[16:22:48] Deleting current work unit & continuing...
[16:22:52] - Preparing to get new work unit...
[16:22:52] + Attempting to get work packet
[16:22:52] - Connecting to assignment server
[16:22:52] - Successful: assigned to (171.65.103.156).
[16:22:52] + News From Folding@Home: Welcome to Folding@Home
[16:22:52] Loaded queue successfully.
[16:23:07] + Closed connections
[16:23:12]
[16:23:12] + Processing work unit
[16:23:12] Core required: FahCore_78.exe
[16:23:12] Core found.
[16:23:12] Working on Unit 06 [February 24 16:23:12]
[16:23:12] + Working ...
[16:23:12]
[16:23:12] *------------------------------*
[16:23:12] Folding@Home Gromacs Core
[16:23:12] Version 1.70 (October 24, 2004)
[16:23:12]
[16:23:12] Preparing to commence simulation
[16:23:12] - Assembly optimizations manually forced on.
[16:23:12] - Not checking prior termination.
[16:23:12] Couldn't v3Decompress
[16:23:12] - Fatal: Could not decompress work unit data.
[16:23:12] Error: Could not open work file
[16:23:12]
[16:23:12] Folding@home Core Shutdown: FILE_IO_ERROR
[16:23:16] CoreStatus = 75 (117)
[16:23:16] Error opening or reading from a file.
[16:23:16] Deleting current work unit & continuing...
Etc. etc. etc. In case you don't want to read that, the error is "Couldn't v3Decompress", then "Error: Could not open work file", then "FILE_IO_ERROR CoreStatus = 75 (117)". This happens whether I run from C:\Program Files\Folding@Home or a new installation at C:\Folding@Home, whether or not I use -forceasm, and whether or not I use -advmethods.
There is no overclocking involved and my CPU rarely hits 50 C under load from F@H.
My specs:
Shuttle SN95G5
Athlon 64 3500+ Winchester
2 x 512 MB Corsair DDR400
2 x Western Digital Raptor 36 GB in RAID 0 (C drive)
Windos XP SP2
FILE_IO_ERROR would seem to point to a hard drive problem, but the Raptors are in perfect working order and I scan/defrag them every week. The rest of my system has no problems and is totally stable, Prime95 stress-tested etc.
I looked for answers on the F@H board but it didn't help. I figured maybe you guys could lend a hand. Thanks!
EDIT: Just restarted and managed to start a WU. However, as I mentioned, this happens pretty much every time I finish one, so if you know the cause I would still appreciate hearing about it.