Hello,

I have a problem, with a Bluescreen of Death 0xf4
However, before I fix this problem by simply reinstall my current Windows 7,
My Attention is set to tell this issue with Wuprop Workunits.
If BOINC is running, when the System crashes, Wuprop (and only Wuprop) will resume with an calculation error, next time BOINC is started.
It's not only when Windows crash in a Bluescreen of Death, this situation appears sometimes, if you simply close BOINC, without pause the current Tasks.

Is this possible to fix?
How can I help?

Greetings

It would be NICE if it was FIXED so we do not loose all the accumulated computing hours since the last task reporting...

It has been this way as long as I have been at this project.

---

Can't say I have struck this problem, but then I don't have 64 bit Windows.

Does the System crash ever happen when BOINC is not running?

What else is running (other than BOINC) when the systen crashes?

Have you checked that you are not infected by a virus, trojan, etc.?

If WUProp tries to restart then errors out I can only think that the BOINC files have been corrupted when the system went down.

Finding the cause of the crashes would seem a prudent thing to do first, as I can't see how BOINC would be the issue here, so check any logs you can find (even BOINCs own logs) to get some ideas.

Other than that I don't know.

Conan

---

No it is NOT BOINC RELATED!

ANY BSOD/CRASH of Windows any version... I have had it happen to my PC's running XP, Vista, Win 7 and Win 8/8.1.

A momentary power glitch can be enough to make Windows "error" on restart and WuProp will 99% of the time be the ONLY ACTIVE BOINC TASK that is corrupted or unable to resume from where it was before the uninterrupted Windows shutdown.

---

As Dr Who Fan said, it's not related to the WUProp app, though it would be nice if the WUProp app didn't fail on system restart/if it could recover.

All sorts of things can cause a BSoD - power problems, minor hardware issues, operating system or software glitches. W7 system updates can cause WUProp failures when there is an auto-restart, though you would need to look in the System Error logs to see if there was a BSOD, as it's unlikely to be right there in front of you (the system restarted after the BSoD).

If the issue was related to Boinc it's most likely to be an app from another project causing the BSoD/restart and not the Boinc software.

In such cases I would always recommend a cold start; system shut down, power cable out for 1min and then connect it up and boot up again. That prevents issues caused by hardware holding some charge.

During last three days I had 3 BSODs and lost 137 hours total. In my case this is some problem with VirtualBox, without it system is stable (I suspect that it does not work well with Win10 or Kaspersky Total Security). I also recall some power outage in the past when I also lost some hours. Please fix this problem. It is acceptable for me to lost data recorded during few minutes before crash, but earlier records should be kept. Maybe copy data every minute to second file, and try to use it if primary file would get corrupted? Or upload results file as-is to server, and try to recover some data from it there?

---

There have been some really nasty VB apps lately. Frankly I don't trust the projects behind these problem apps & VB shouldn't be perceived as the way forward for Boinc.
Would be good if WUProp backed itself up every 10min & could recover from a backup following a failure, but that's down to the ability + availability of the project admin; who might not think it worthwhile (say if overall failures are <0.1%). BTW you can control task checkpoints in BM; options, computer preferences, but 1min checkpoints are probably not good for the disk or productivity - I use ~600sec (10min).

There have been some really nasty VB apps lately. Frankly I don't trust the projects behind these problem apps & VB shouldn't be perceived as the way forward for Boinc.
Would be good if WUProp backed itself up every 10min & could recover from a backup following a failure, but that's down to the ability + availability of the project admin; who might not think it worthwhile (say if overall failures are <0.1%). BTW you can control task checkpoints in BM; options, computer preferences, but 1min checkpoints are probably not good for the disk or productivity - I use ~600sec (10min).

Agree on the VBox Wrapper apps - Can be VERY UNSTABLE, USES LOTS OF EXTRA (OVERHEAD) RAM NOT REPORTED IN/TO BOINC MANAGER, DISK SPACE and IS EXTREMELY CPU & DISK INTENSIVE.

Suspect the NCI (Non Compute Intensive) apps such as WuProp have no way to perform checkpoint(s).

---

Today I had a "<error_code>-240" on a task that for some reason it ended with a "Outcome: Computation error"...

https://wuprop.boinc-af.org/result.php?resultid=71090860

Run time was NORMAL: 6 hours 1 min 25 sec

Stderr output

<core_client_version>7.7.2</core_client_version>
<![CDATA[
<message>
upload failure: <file_xfer_error>
<file_name>data_collect_v4_1494478201_51965_0_0</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>

</message>
]]>

---