• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

FILE IO ERROR?

S

Sunin

[H]ard|DCer of the Month - August 2008
Joined
Dec 27, 2005
Messages
3,421
I have one machine that just keeps throwing these file IO errors. Everything else works on the computer just endless IO errors... I've deleted teh F@H directories and reinstalled same thing. Says something about digital signature does not match.

If I get a chance I'll try to cut and paste it in.

Anyone ever see this?

Error: Bad work unit. Digital signatures don't match
Error: Could not open work file

Folding@home Core Shutdown: FILE_IO_ERROR
Finalizing output


 
Sunin said:
I have one machine that just keeps throwing these file IO errors. Everything else works on the computer just endless IO errors... I've deleted teh F@H directories and reinstalled same thing. Says something about digital signature does not match.

If I get a chance I'll try to cut and paste it in.

Anyone ever see this?

Error: Bad work unit. Digital signatures don't match
Error: Could not open work file

Folding@home Core Shutdown: FILE_IO_ERROR
Finalizing output


Click to expand...

I've had these before too....It will attempt to get the same packet like three times I think before it moves on to something else. The alternative is to just delete the contents and set it up again fresh, but it seems you've already tried that. Might just have to ride it out until it gets another packet.

Good luck....

 
My guess is you pushed on OC to far.

I've had some systems where they throw fits until I back off the OC 10Mhz and then they are happy.

 
It finally downloaded a new WU and is happy once again... very weird... I checked my OC by prime95 for an hour and no issues, temps all good, so I think I got a flaky WU. Thanks for the help everyone. :)

 
I would of guessed OCed too far, but I have seen the same thing happen.
1 WU it would choke on, after it cleared, new WU everything is fine.
Usually though if I back off the OC the problem WU would make it thru.
Well 8 out 10 times or so, sometimes there are just those problems WUs




 
Well the fun continues with this box... It reboot inthe middle of the night. So I went back to the basics... Memtest... and guess what 1,000 errors in five seconds...

Appears I have a bad set of ballistix memory... I will try moving the ballistix to other slots and worst case swap in another set. Hoping it is not the motherboard. I figure if I put them in a machine I know is having no issues and they error then its the ballistix...

Oye... bad thing is usually you can smell when ram is fried, they don't smell...



 
Sunin said:
Well the fun continues with this box... It reboot inthe middle of the night. So I went back to the basics... Memtest... and guess what 1,000 errors in five seconds...

Appears I have a bad set of ballistix memory... I will try moving the ballistix to other slots and worst case swap in another set. Hoping it is not the motherboard. I figure if I put them in a machine I know is having no issues and they error then its the ballistix...

Oye... bad thing is usually you can smell when ram is fried, they don't smell...



Click to expand...

I'm glad you haven't rolled over me yet.... but I wish it wasn't boxen malfunction that was the reason.

I hope you get everything back up soon.

 
Sunin said:
Well the fun continues with this box... It reboot inthe middle of the night. So I went back to the basics... Memtest... and guess what 1,000 errors in five seconds...

Appears I have a bad set of ballistix memory... I will try moving the ballistix to other slots and worst case swap in another set. Hoping it is not the motherboard. I figure if I put them in a machine I know is having no issues and they error then its the ballistix...

Oye... bad thing is usually you can smell when ram is fried, they don't smell...

Click to expand...

Bad Luck, man. Murphey's Law bites me all the time, too. :rolleyes:

I've got a stick of OCZ RAM that did the same thing - no smell, no indicator, no nothing. I just started getting 0x7B errors about two weeks after I started folding on this particular box. Memtest started dropping erros when I tested both sticks, so I isolated them and found the faulty RAM almost immediately. Right now that boxen only runs on 1 gig until I get the other one RMA'ed.

 
Yeah luckily, by a total fluke, I had ordered an extra ADATA 2x2Gb set and its due to arrive today. So I won't be down for long and I'm just RMA'n both I've had too many issues with Ballistix it is now on my never use list!



 
You must log in or register to reply here.
Back
Top