Last night when I switched off, Sulphur hynn reported a 4.8% progress rate (it got as far as July 1840) but this morning that figure is back down to 0.08% (back to December 1810)
Did it start all over again? Why? The project has had more than 76 hours of CPU time and I have some problems, like Windows Explorer not starting up at times, that I can live with if it serves a purpose. If the same thing happens in 76 CPU hours\' time I might just consider unloading the software...

---

The computer summary on Your Account page shows nothing out of the ordinary.

Any error messages under the Messages tab? If so, please copy/past them here.


By the way, you have three P4 3.0 machines listed, two without credit. Are they all the same machine? If so, they can be \"merged\" from Your Account page, View Computers.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

RGtx,

This is the dreaded 1073807364 error code. It has been difficult to troubleshoot. Some people have had luck updating their video drivers, but for others it hasn\'t worked.

When I clicked on your name, then tried to look at your computers, none were listed.

OK, I have merged all three aliases into one.
Regarding the possibility there were some error messages, I didn\'t notice to be honest and think I might even have re-booted a couple of times since the dreaded problem struck without noting it had. The messages aren\'t stored in a log (or are they?) so this morning I don\'t see yesterday\'s.
Looking at my results, or rather the trickles, it would seem I got as far as timestep 54010; I\'m actually at just under 6000. I suppose the results will be reported correctly when I again reach and surpass 54010.
When I booted this morning, Explorer didn\'t kick in and I had to re-boot. This has become an everyday problem since loading BOINC. Any ideas?

---

RGtx, The errored results were two exit codes 1, and the -10xxxxxx error, as well as an aborted via GUI RPC. Quite a variety. I see you now have two new ones. Good luck with those.

The cloud/snow details (and other fields) can be smoothed/unsmoothed using the \"9\" hotkey when viewing the globe graphic in sulphur.

After updating the video card driver and receiving a couple of important updates from Microsoft as well, I\'ve not had any more problems with Explorer.
Sulphur hynn has had a further 100 hours running time but is nowhere near the 1840 mark I reached with 80 hours work previously. I\'ve done double the timesteps and only gotten as far as 1816. Apart from that, all seems to be going well now.

---

I\'ve had this problem twice in the last few days, firstly losing 80,000 steps and taday just a few. Any ideas as my PC is up to date with MS auto-update?

---

After updating the video card driver and receiving a couple of important updates from Microsoft as well, I\'ve not had any more problems with Explorer.
Sulphur hynn has had a further 100 hours running time but is nowhere near the 1840 mark I reached with 80 hours work previously. I\'ve done double the timesteps and only gotten as far as 1816.

Between the fifth and sixth trickle, your model obviously started back at the beginning of phase 1, but kept the CPU time. So, it did not provide the 6th trickle until a week after the 5th (because it won\'t list duplicate trickles). This is why your sec/TS is so high compared to the early trickles, and why it continues to drop.

This has happened to me three times over the 1.5 years I\'ve been running BOINC. Very frustrating. Each time it was because of a power failure, or unintended shutdown of the PC while BOINC was running.

I\'ve had this problem twice in the last few days, firstly losing 80,000 steps and taday just a few. Any ideas as my PC is up to date with MS auto-update?

We\'ve got a collection of ideas here : http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=4231

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

This thread is getting very confusing. The original poster had a problem with a WU restarting at 0% (without an error).

The next poster introduced a problem with exit code 0x40010004.

And the final post here refers to another thread that deals with 0xc0000005 and -161 errors.

The real solution to the original post is to gracefully end the client application (BOINC Manager, Commands, Suspend, then wait until the Work tab shows the Status as suspended) before shutting down the system.

Also regular backups of the entire BOINC folder help to recover from that situation.