Had something very strange happen today.
Milky way started thrashing my hard drive, after about a minute the computer locked up and blue screened on me.
Im running windows 7 pro 64 bit.

When I restarted and restarted boinc, I got a bunch of error messages for every milky way Project I had currently on the drive.

1/15/2011 6:57:39 PM [error] Task de_separation_16_3s_fix_2_915973_1295086392_0 outside project in state file

this pretty much was for anything milky way. Once Boinc finally started it was like milky way was never there, it disconnected me from MW, took it out of the list of projects and I had to reconnect and log in again like I never was here on this computer.

Needless to say the tasks I had waiting to run are gone, and im starting again.

Any idea what caused this to happen?

Aaron

Not sure of the cause in your case, but MilkyWay disappeared from my BOINC Manager recently after I had problems with Collatz.

Thought I would try a few of the new longer Collatz tasks. As soon as Collatz started to run the screen got little coloured squares all over it then froze. I rebooted and the computer froze instantly when I started BOINC. This happened multiple times, so I eventually deleted the 2 Collatz tasks from the BOINC directory before starting BOINC. When I restarted it MilkyWay had disappeared from the list of projects in Projects tab, even though it was still there in C:\ProgramData\BOINC\projects. So I had to attach again.

Haven't tried Collatz again since. Not sure what caused it, perhaps my 5970 has been running at a low memory speed so long it refused to run when I increased the memory speed to 1,000 MHz to run Collatz. Maybe the card has been damaged by constantly running at full load and the extra strain of running at a higher memory speed causes it to fail.

After I reattached to MilkyWay, before I downloaded any new work I detached and reattached again to clean out lots of old stars and parameters files and to make sure nothing there was corrupted.

I think this a BOINC thing. Last year there were serious power fluctuations in my area and made my boxes restart several times. 2 boxes crunching MW and 1 box crunching Collatz detached from both projects.

I've also had projects detach after power failures. Not often but it happens.

I have had some continuing problems with disk thrashing then freezing / BSD so did a full disk diag and found some bad sectors in the boinc directory. I ended up detatching from one project and letting windoze 'fix' the hdd and so far it seems like the problem has gone away. Im assuming I might have had a bad project which caused a lockup or something right at the wrong moment in time when a disk write was occurring, which caused the corruption, which then continued to cause probs on subsequent runs with it.

Let's hope everything plays nicely now.

Aaron

In my case, I think BOINC assumed that the projects were causing the restarts so it detached the projects. I don't know about the current version, I was using 6.10.18 at that time.

Run this:
chkdsk C: /f