My 2nd rig has errored all (only 3) grav wave WUs, they're taking ages and then I get this "197 (0x000000C5) EXIT_TIME_LIMIT_EXCEEDED". Bearing in mind my 2nd rig's GPU has nearly double the DP power of my main rig.
2nd rig GPU driver is 19.9.1, updating to 20.4.2.....
I saw this mentioned in the 1st page, but I'm not reading all 12 pages of this thread to find the answer :p
Was their an easy answer?
[update]
Remaining time for it's current WU is 19hrs 40mins and climbing fast! So it's going to hit the time limit again. Updating the driver made no difference, so until/if I can fix this, I'm going to shut that rig down as it's a total waste of time & power :(.
Hope one of the AMD users can chime in and offer some suggestions.
FWIW, I am totally surprised that you somehow even managed to receive an old O2MD1 task. I haven't received one in months now that they have turned off the splitters for that work. Guess you managed to pick up a straggler resend.
Or are you confused and posted to the "wrong" cpu task thread and you actually are having issues with the O2MDF gpu tasks. Think that may be the case since you mention gpu drivers.
The original search was the O2MD1 cpu application. This thread was the original one that was started for that work. They later added a gpu application for the O2MDF tasks and a separate thread was started for the gpu search.
Earlier this year, they published their research paper from the analysis of the returned cpu task results.
And promptly stopped distributing any more cpu work for that search.
But they are continuing to distribute gpu tasks for the O2MDF search and there is plenty of work.
Hope you get some traction from your post from AMD users. I only have ever run Nvidia and am of no help for you.
Card hasn't died as it's been working for other things, tried 2 different drivers and no change, but it could still be a driver issue I suppose, although atm I think it's more likely it's something to do with Einstein.
Anyway, I'll try that other thread.
As for MW, I have run that (and probably will again), but I put my 7870 to einstein for a team 'sprint'.
My 2nd rig has errored all (only 3) grav wave WUs, they're taking ages and then I get this "197 (0x000000C5) EXIT_TIME_LIMIT_EXCEEDED". Bearing in mind my 2nd rig's GPU has nearly double the DP power of my main rig.
I guess by "2nd rig" you are referring to the one with the older GPU - a Tahiti series which does have very good DP capability. However, the GPU searches at Einstein don't need DP capability. The problem is that it's a GCN 1st generation card that just can't handle the current GW search at all. About a year ago, a number of us tested 1st gen cards and all found the same result - TIME LIMIT EXCEEDED - without even getting any significant "real" progress. There were a number of messages about this at the time.
If you put that GPU on the gamma-ray pulsar GPU search it will do very well. I run a couple of 7950s running 2 concurrent tasks and each pair of tasks get completed in about 25 mins or so. Just change your prefs to exclude the GW search and set the FGRPB1G GPU search for it. To not affect your other machine, you might put them in different 'locations' - aka 'venues'.
Thanks for your reply, somehow I missed this reply yesterday, sorry about that :o.
No need to guess, it's labelled 2nd rig in my sig ;), I'll reply to the rest in the crunchers corner thread.
I turned off sigs 15 years ago. Forum response times are now just slow, rather than completely woeful.
Even when people properly describe their hardware in a sig (and leave out all the other crap), I usually find that the host's 'details' page plus the information from the tasks list on the website gives a much quicker and easier route to problem resolution.
When reporting a problem, one of the most useful things to give is a direct link to the details page for the host in question. That page then has a direct link to the tasks. That will work even if hosts are 'hidden'.
Hallo! And when will start
)
Hallo!
And when will start these O3-run?
I hope eagerly, Bernd - and no one else too - has been catched by Covid-19!
Kind regards an happy crunching
Martin
My 2nd rig has errored all
)
My 2nd rig has errored all (only 3) grav wave WUs, they're taking ages and then I get this "197 (0x000000C5) EXIT_TIME_LIMIT_EXCEEDED". Bearing in mind my 2nd rig's GPU has nearly double the DP power of my main rig.
2nd rig GPU driver is 19.9.1, updating to 20.4.2.....
I saw this mentioned in the 1st page, but I'm not reading all 12 pages of this thread to find the answer :p
Was their an easy answer?
[update]
Remaining time for it's current WU is 19hrs 40mins and climbing fast! So it's going to hit the time limit again. Updating the driver made no difference, so until/if I can fix this, I'm going to shut that rig down as it's a total waste of time & power :(.
Any ideas anyone?
Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H.
Main rig - Ryzen 5 3600, 32GB DDR4 3200, RTX 3060Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win 7 64bit
Hope one of the AMD users can
)
Hope one of the AMD users can chime in and offer some suggestions.
FWIW, I am totally surprised that you somehow even managed to receive an old O2MD1 task. I haven't received one in months now that they have turned off the splitters for that work. Guess you managed to pick up a straggler resend.
Or are you confused and posted to the "wrong" cpu task thread and you actually are having issues with the O2MDF gpu tasks. Think that may be the case since you mention gpu drivers.
The thread that you should have posted is here:
discussion-thread-continuous-gw-search-known-o2md1-now-o2mdf-gpus-only
Didn't know their were CPU
)
Didn't know their were CPU tasks! ;)
And yea GPU tasks, didn't see anything in the title about CPU.
"Gravitational Wave search O2 Multi-Directional ("O2MD1")"
I'll check out that thread, thanks.
Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H.
Main rig - Ryzen 5 3600, 32GB DDR4 3200, RTX 3060Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win 7 64bit
The original search was the
)
The original search was the O2MD1 cpu application. This thread was the original one that was started for that work. They later added a gpu application for the O2MDF tasks and a separate thread was started for the gpu search.
Earlier this year, they published their research paper from the analysis of the returned cpu task results.
And promptly stopped distributing any more cpu work for that search.
But they are continuing to distribute gpu tasks for the O2MDF search and there is plenty of work.
Hope you get some traction from your post from AMD users. I only have ever run Nvidia and am of no help for you.
Sorry.
[TA wrote:Any ideas
)
Try it on MilkyWay. If it doesn't work there, then your card has died (or has a bad driver install).
Card hasn't died as it's been
)
Card hasn't died as it's been working for other things, tried 2 different drivers and no change, but it could still be a driver issue I suppose, although atm I think it's more likely it's something to do with Einstein.
Anyway, I'll try that other thread.
As for MW, I have run that (and probably will again), but I put my 7870 to einstein for a team 'sprint'.
Keith
Got ya, thanks :)
Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H.
Main rig - Ryzen 5 3600, 32GB DDR4 3200, RTX 3060Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win 7 64bit
{TA}Assimilator1 wrote:My 2nd
)
I guess by "2nd rig" you are referring to the one with the older GPU - a Tahiti series which does have very good DP capability. However, the GPU searches at Einstein don't need DP capability. The problem is that it's a GCN 1st generation card that just can't handle the current GW search at all. About a year ago, a number of us tested 1st gen cards and all found the same result - TIME LIMIT EXCEEDED - without even getting any significant "real" progress. There were a number of messages about this at the time.
If you put that GPU on the gamma-ray pulsar GPU search it will do very well. I run a couple of 7950s running 2 concurrent tasks and each pair of tasks get completed in about 25 mins or so. Just change your prefs to exclude the GW search and set the FGRPB1G GPU search for it. To not affect your other machine, you might put them in different 'locations' - aka 'venues'.
Cheers,
Gary.
Thanks for your reply,
)
Thanks for your reply, somehow I missed this reply yesterday, sorry about that :o.
No need to guess, it's labelled 2nd rig in my sig ;), I'll reply to the rest in the crunchers corner thread.
Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H.
Main rig - Ryzen 5 3600, 32GB DDR4 3200, RTX 3060Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win 7 64bit
I turned off sigs 15 years
)
I turned off sigs 15 years ago. Forum response times are now just slow, rather than completely woeful.
Even when people properly describe their hardware in a sig (and leave out all the other crap), I usually find that the host's 'details' page plus the information from the tasks list on the website gives a much quicker and easier route to problem resolution.
When reporting a problem, one of the most useful things to give is a direct link to the details page for the host in question. That page then has a direct link to the tasks. That will work even if hosts are 'hidden'.
Cheers,
Gary.