HP2 computation errors

[Chumbucket843]

the errors strange because the HPF2 project description said they use the most stable version of rosetta. i guess that it has some of the memory instability issues that rosetta has. my old system ran these with no problems at all but my i7 fails them with in 20 minutes.

[Plan.B]

I have 7,979 results returned for HPF2, and numerous HPF2 tasks currently running, on xp and vista machines. I have a sapphire HPF2 badge (2 years). I've never had a problem with this project. I may have over-looked the odd error, I don't keep a super-close eye on my tasks status, but close enough to notice more than a few errors. I hate to drop it if it's doing good work, but I think I'll shift gears to my other favorite (HCC) for the rest of this week.

[D_A]

the HPF2 project description said they use the most stable version of rosetta.

I think that's the key.

hint: there's a LOT I'm not saying here.

[rwillis]

the errors strange because the HPF2 project description said they use the most stable version of rosetta. i guess that it has some of the memory instability issues that rosetta has. my old system ran these with no problems at all but my i7 fails them with in 20 minutes.

And they still do........... it's the least stable of the projects ATM.

[Thraxis]

Somewhat odd that my Q6600 (Main rig) Has not returned a single error with that project. However, All Athlon II X4 systems under my name (2 friends, one personal) have returned a page worth of errors. Sadly decided to disable them on all. Hopefully this will eventually get fixed.

[Kurz]

I just had a string of errors from HP2...
Took it off my work load.

[mreuter80]

good news: https://secure.worldcommunitygrid.or...e,yes#lastpost

Uplinger announces:

Greetings all,

We have recently updated the HPF2 science application. The BETA that was run a few weeks ago was confirmed by the researchers as being good. The new version will be 6.17 for all platforms. This latest version of HPF2 is to help decrease the number of Exit 1 status errors, people were getting on Windows.

Thanks,
-Uplinger

here from one of the scientists:

Hi,
I just wanted to add that I've verified a few proteins run with the new executable and they look good. Also, I'll update everyone with a status update soon, but I just wanted to add that I've sent IBM more work units. We're going to fold Chlamydomonas reinhardtii in the interim before we get to the microbiome project. It's a nice little single celled alga whose metabolism is being exploited to create clean sources of hydrogen.
--
Patrick

Other WCG users report they have picked up the new application.
So I gonna try and turn it on for my machines once the Supercomputerweek is over.

[T_M]

Im getting HFCC errors on every WU on one of my machines, but not others. I even reduced it to stock and still the same....

[mreuter80]

Im getting HFCC errors on every WU on one of my machines, but not others. I even reduced it to stock and still the same....

Is this with the new version 6.17?
What error do you get?

[T_M]

Result Name: HFCC_ s2_ 01839646_ s2_ 0001_ 1--
<core_client_version>6.10.43</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
]]>

[Kurz]

Result Name: HFCC_ s2_ 01839646_ s2_ 0001_ 1--
<core_client_version>6.10.43</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
]]>

I guess your client hasn't updated yet.

[T_M]

WHat do you mean?
Im talking about HFCC WU's

[mreuter80]

This thread is for HPF errors, can you please open another thread for your errors with HFCC.

The error is a nasty one. Nobody can really tell what the reason is, because there could be any reason for this one to happen.

Exit code -1073741819 (0xC0000005): This is the famous "General Access Violation". There a numerous reasons for this error to occur, from hardware problems to graphics drivers and more. Ideally when this happens, the "Windows Runtime Debugger" should start up and write a stack dump to stderr out that helps to further diagnose the problem. If the "Access Violation" is listed in the "*** Dump of the Graphics thread ***", it was almost certainly a problem with the graphics driver. The most common cause for an Access Violation listed in the "*** Dump of the Worker thread ***" shows "houghmap.c:" near the end of the first line of the Callstack. This is a problem that we might be able to do something about, we are currently hunting this. Apparently it only happens on certain machines, it might be related to the data these hosts are processing, but may also be a property of the hardware or other software on the system.

I could solve this error message once by re-seating my RAM modules. After taking out and putting them back in ti worked fine for me. But it could be anything on your machine.

I suggest open another thread for this error and maybe others can chime in to help you.

[don_xvi]

In spite of the new application, people are still reporting errors on HPF2 over at the WCG forums. I'll wait a bit longer before restarting work on it.

[Chumbucket843]

i'm no longer getting errors on HPF2 with v6.17. its worth a try.

[werdwerdus]

after may 8 i'm going to turn it back on long enough to get my gold badge, then I dono, probably go to Cancer and Aids

edit: make that a Ruby badge, I like how those look :P

[shifty803]

Sorry to resurrect a dead thread, but are these errors still around? Us new guys don't know all the history - might be good to add to the "Everything you need to know" sticky. I seem to have gotten a couple errors from each of my SB systems (i7 2600k and i3 2100). If it were just the 2600k I'd wonder if my overclock isn't stable... but the i3 is definitely stock and it's not even running the same OS. No invalids from either system so far.

Bummer. I like the protein folding project too. My 920 was able to crunch this project without any errors at all.

Guess I will have to downcheck that one.

[Rob_B]

I haven't seen an error with this project in a while now. I have crunch it on different systems with Windows and Linux.

And when I had an error, it was always right away. So no real time lost anyway.

[NKrader]

this project is hit or miss.

ive gotten like 3 failed results the whole time ive been crunching. and i run overclocked on main rig always, and alot of diff spec cpus.

some rigs have problems some dont. you should just check as you dont want to have a rig that is always failing just fail fail fail all day.

[shifty803]

I think for now I'll just quit this project. Considering I have like 20 days of cpu time on that project on only two errors, the frequency of errors is really low. However, I'd rather let people with no issues crunch that one and devote my cpu time where I know it will not go to waste.