Forum > Windows
Help required! Cuda on new system crashes!
efmer (fred):
--- Quote from: Gizbar on 01 Nov 2009, 05:15:38 am ---Thanks for the info, Fred.
I'm just happy at the moment that it's running successfully without crashing. Never noticed it swapping wu before that's all. If it's normal behaviour I can live with it. My RAC is taking a dive with all this mucking around going on, but I need to find out what is going on.
As posted earlier I went back to version 6.6.38 from version 6.6.41, which I notice has now been pulled from Boinc downloads for Windows systems. Have you tried the 6.10.17 version yet?
Want to get it running properly before messing with another new Boinc version.
regards, Gizbar.
--- End quote ---
I will wait some time because 6.6.38 works without any problems for me. It's mainly for AMD/ATI users.
Claggy:
Gizbar,
I'd make sure you have Boinc 6.6.37 /.38 minimum, or go to 6.10.17, which is very stable now,
6.10.x was originally only getting ATI support, but has had a lot of other fixes / enhancement's since,
the one i like the most is the 'Show active Task' only button, cuts down on a lot of the traffic between
the boinc client and boinc manager.
I'm running it on both my Desktop and Laptop no problem, along with the new Beta 195.39 drivers,
again no problem there eithier, I'd try Boinc 6.10.17 first, then later with the new drivers,
and have a look if there are any later chipset drivers available as well.
The problems with Boinc 6.6.36 are that if you have a largie-ish cache, and you ask for Seti work
and if you get lots of shorties, then Boinc will go EDF on the GPU, start a shortie on the GPU,
it might complete some of it before switching to another since that is in worse deadline pressure the the first shortie,
that's O.K in itself, but the problem is that if Boinc switches GPU Wu's before the first wu has checkpointed,
then Boinc doesn't free up the GPU memory, and every GPU wu after that runs in CPU fallback mode,
taking a whole core, meaning you now have more CPU tasks than cores,
(I don't think that's your problem through)
6.6.37 fixes the problem of GPU tasks going into CPU fallback mode, but not the problem of the actual switching,
6.10.17 fixes the problem with switching GPU tasks, GPU tasks now run not quite FIFO order,
they run in received order by date/time, and subdivided into report deadline order.
Claggy
Edited and added more thoughts
efmer (fred):
--- Quote from: Claggy on 01 Nov 2009, 06:03:15 am ---Gizbar,
I'd make sure you have Boinc 6.6.37 /.38 minimum, or go to 6.10.17, which very stable now,
6.10.x was originally only getting ATI support, but has had a lot of other fixes / enhancement's since.
The problems with Boinc 6.6.36 are that if you have a largie-ish cache, and you ask for Seti work
and if you get lots of shorties, then Boinc will go EDF on the GPU, start a shortie on the GPU,
it might complete some of it before switching to another since that is in worse deadline pressure the the first shortie,
that's O.K in itself, but the problem is that if Boinc switches GPU Wu's before the first wu has checkpointed,
then Boinc doesn't free up the GPU memory, and every GPU wu after that runs in CPU fallback mode,
taking a whole core, meaning you now have more CPU tasks than cores,
(I don't think that's your problem through)
6.6.37 fixes the problem of GPU tasks going into CPU fallback mode, but not the problem of the actual switching,
6.10.17 fixes the problem with switching GPU tasks, GPU tasks now run not quite FIFO order,
they run in received order by date/time, and subdivided into report deadline order.
Claggy
--- End quote ---
Thanks, but the rapid pullback or the previous release got me a bit scared. ;D
Gizbar:
Thanks for the replies.
I've just heard from MarkJ on the Seti forum and he has explained that this could happen with the earlier versions of Boinc numbered 6.6.xx, and has been resolved in some of the later versions and suggested I upgrade to 6.10.17 as well. It has to do with the 'Task Switching Interval', which would let Boinc start a new task instead of running to completion. Please be aware I'm just relaying the information...
I think I'm proving that the card is stable on XPPro-32, it has been running for at least 2.5 hours now without a glitch, freeze, or crash. I'll leave it a bit longer and then start to try to install Win7-64HP again and see where that gets me to.
regards, Gizbar.
efmer (fred):
--- Quote from: Gizbar on 01 Nov 2009, 07:16:10 am ---Thanks for the replies.
I've just heard from MarkJ on the Seti forum and he has explained that this could happen with the earlier versions of Boinc numbered 6.6.xx, and has been resolved in some of the later versions and suggested I upgrade to 6.10.17 as well. It has to do with the 'Task Switching Interval', which would let Boinc start a new task instead of running to completion. Please be aware I'm just relaying the information...
I think I'm proving that the card is stable on XPPro-32, it has been running for at least 2.5 hours now without a glitch, freeze, or crash. I'll leave it a bit longer and then start to try to install Win7-64HP again and see where that gets me to.
regards, Gizbar.
--- End quote ---
The latest beta driver from nVidia and I got a kernell error after a few minutes. Haven't seen one of those for some time. They still have work to do.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version