I just upgraded the OS on my old PC from XP to Win7 (32bit). The BOINC (7.14.2 for 32Bit XP/Win7/Win8) used to run pretty well with XP but now I get computation error for every task it runs. The error messege is like this https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=29982563. The installation programme of BOINC is still the one from XP system. No problem with installation process and nothing went wrong with WGC's OpenPandemics project. What's going on? Do I need to change any configuration?

They still offer x86 32 bit applications for Separation so that should have worked. I would reset the project and see if you can force a new interrogation of your computer hardware so the project can sort things out.
If that doesn't work, then I would uninstall BOINC and then reinstall it and add MW back in.
There is some kind of file permission problem from the error.

---

They still offer x86 32 bit applications for Separation so that should have worked. I would reset the project and see if you can force a new interrogation of your computer hardware so the project can sort things out.
If that doesn't work, then I would uninstall BOINC and then reinstall it and add MW back in.
There is some kind of file permission problem from the error.

I tried resetting the project and deleting/adding the project again. No change at all.

The interesting thing is that I can't help notice the error occurs when the programme reach 'check point' time, whihc in my case, 60sec. The computing went fine at the start but at about 63~64sec, it stopped and the error occured. I changed the check point time to 120sec once yesterday and it happened a few seconds after 120sec.

They still offer x86 32 bit applications for Separation so that should have worked. I would reset the project and see if you can force a new interrogation of your computer hardware so the project can sort things out.
If that doesn't work, then I would uninstall BOINC and then reinstall it and add MW back in.
There is some kind of file permission problem from the error.

I tried resetting the project and deleting/adding the project again. No change at all.

The interesting thing is that I can't help notice the error occurs when the programme reach 'check point' time, whihc in my case, 60sec. The computing went fine at the start but at about 63~64sec, it stopped and the error occured. I changed the check point time to 120sec once yesterday and it happened a few seconds after 120sec.

sorry I posted in the wrong thread

Your observation leads credence to my opinion that you have a write permission problem. The BOINC client needs write permission to create and update the checkpoint file and it is being blocked by your OS or virus blocker or something.

---

They still offer x86 32 bit applications for Separation so that should have worked. I would reset the project and see if you can force a new interrogation of your computer hardware so the project can sort things out.
If that doesn't work, then I would uninstall BOINC and then reinstall it and add MW back in.
There is some kind of file permission problem from the error.

I tried resetting the project and deleting/adding the project again. No change at all.

The interesting thing is that I can't help notice the error occurs when the programme reach 'check point' time, whihc in my case, 60sec. The computing went fine at the start but at about 63~64sec, it stopped and the error occured. I changed the check point time to 120sec once yesterday and it happened a few seconds after 120sec.

Can you change the checkpoint time to say 900 seconds, 15 minutes, and see if it gets all the way thru a unit? How much had the unit completed when it crashed? That should give you an idea of how long to make the time between checkpoints and crashes. But as Keith says that's not a real solution as it also means if you stop Boinc any and all tasks will be affected by the new checkpoint rules so all tasks could start at the beginning again.

Can you change the checkpoint time to say 900 seconds, 15 minutes, and see if it gets all the way thru a unit? How much had the unit completed when it crashed? That should give you an idea of how long to make the time between checkpoints and crashes. But as Keith says that's not a real solution as it also means if you stop Boinc any and all tasks will be affected by the new checkpoint rules so all tasks could start at the beginning again.

Ok, I'd done better. I set the checkpoint time exceeding the run time of a task. It worked. No error any more. And I'm not going to worry too much about the chek point rule thing 'cause I'm going to let the PC run 24/7 from now on LOL (just kidding). Thanks for the advice though.

Can you change the checkpoint time to say 900 seconds, 15 minutes, and see if it gets all the way thru a unit? How much had the unit completed when it crashed? That should give you an idea of how long to make the time between checkpoints and crashes. But as Keith says that's not a real solution as it also means if you stop Boinc any and all tasks will be affected by the new checkpoint rules so all tasks could start at the beginning again.

Ok, I'd done better. I set the checkpoint time exceeding the run time of a task. It worked. No error any more. And I'm not going to worry too much about the chek point rule thing 'cause I'm going to let the PC run 24/7 from now on LOL (just kidding). Thanks for the advice though.

I'm glad it's working for you!!

Hi there. Is normal, if the cpu temperatures arrives at 70 C ? Thanks.

---

Can you change the checkpoint time to say 900 seconds, 15 minutes, and see if it gets all the way thru a unit? How much had the unit completed when it crashed? That should give you an idea of how long to make the time between checkpoints and crashes. But as Keith says that's not a real solution as it also means if you stop Boinc any and all tasks will be affected by the new checkpoint rules so all tasks could start at the beginning again.

Ok, I'd done better. I set the checkpoint time exceeding the run time of a task. It worked. No error any more. And I'm not going to worry too much about the chek point rule thing 'cause I'm going to let the PC run 24/7 from now on LOL (just kidding). Thanks for the advice though.

I'm glad it's working for you!!

Thank you.
I finally made it work not by setting the checkpoint time but formatting the entire hardrive. I didn't realize it was actually the problem of the setting of the hard drive until I found out absolutely nothing can be written to it. Don't know what happened so I just format it. The problem solved once and for all.

Hi there. Is normal, if the cpu temperatures arrives at 70 C ? Thanks.

I don't monitor the temperature but I guess it's not. Can feel the heat sink is just a little bit warm with my hand. Anyway, it's winter and I put the PC very near a window, quite cold actually. The heater's not working very well in my room this winter.

Hi there. Is normal, if the cpu temperatures arrives at 70 C ? Thanks.

While crunching sure but if you are using a laptop be sure you have one of those things with the fans underneath it and in a desktop be sure you have plenty of airflow as well.