Forum > GPU crunching
Latest drivers (NVidia and ATI)
arkayn:
In other-words, skip this one as well.
I will stick with 290.53 for now.
PatrickV2:
--- Quote from: Claggy on 21 Feb 2012, 03:49:33 pm ---295.73 WHQL is out, downloading now.
Edit: the disappearing cuda device bug is still apparent in these drivers too.
Claggy
--- End quote ---
Damn. :( The performance increases for several of the games I play (or want to play) are very tempting.
IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?
Regards, Patrick.
Claggy:
--- Quote from: PatrickV2 on 22 Feb 2012, 01:49:08 pm ---
--- Quote from: Claggy on 21 Feb 2012, 03:49:33 pm ---295.73 WHQL is out, downloading now.
Edit: the disappearing cuda device bug is still apparent in these drivers too.
Claggy
--- End quote ---
Damn. :( The performance increases for several of the games I play (or want to play) are very tempting.
IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?
Regards, Patrick.
--- End quote ---
My E8500/9800GTX+ machine had no problem with the 295.51 drivers when connected through the VGA port, not tried 295.73 on it yet,
Claggy
PatrickV2:
--- Quote from: Claggy on 22 Feb 2012, 01:52:42 pm ---
--- Quote from: PatrickV2 on 22 Feb 2012, 01:49:08 pm ---
--- Quote from: Claggy on 21 Feb 2012, 03:49:33 pm ---295.73 WHQL is out, downloading now.
Edit: the disappearing cuda device bug is still apparent in these drivers too.
Claggy
--- End quote ---
Damn. :( The performance increases for several of the games I play (or want to play) are very tempting.
IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?
Regards, Patrick.
--- End quote ---
My E8500/9800GTX+ machine had no problem with the 295.51 drivers when connected through the VGA port, not tried 295.73 on it yet,
Claggy
--- End quote ---
Well, my 8800GTX is connected via DVI-D to my monitor. Will I run into this problem or not?
I suppose I could test this, but how can I detect this ASAP so that I don't trash too many WUs (if that happens)?
Regards, Patrick.
arkayn:
When I noticed it, I saw a lot of this in my events.
--- Quote ---1/31/2012 15:20:30 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.252_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:20:38 | SETI@home | Restarting task 04oc11ad.507.90813.6.10.118_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:20:58 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.85_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:06 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.185_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:26 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.28_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:34 | SETI@home | Restarting task 04oc11ad.507.4566.6.10.54_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:54 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.26_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:03 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.138_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:22 | SETI@home | Restarting task 04oc11ad.507.87132.6.10.207_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:32 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.149_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:50 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.79_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:00 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.119_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:18 | SETI@home | Restarting task 25oc11ab.4355.134274.16.10.91_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:29 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.147_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:47 | SETI@home | Restarting task 25oc11ab.4355.140409.16.10.114_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:57 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.254_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:14 | SETI@home | Restarting task 04oc11ad.507.90813.6.10.118_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:26 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.252_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:43 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.85_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:55 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.185_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:11 | SETI@home | Restarting task 04oc11ad.507.4566.6.10.54_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:23 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.28_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:39 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.26_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:51 | SETI@home | Restarting task 04oc11ad.507.87132.6.10.207_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:07 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.149_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:23 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.79_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:36 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.119_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:52 | SETI@home | Restarting task 25oc11ab.4355.134274.16.10.91_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:27:04 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.147_1 using setiathome_enhanced version 610 (cuda_fermi)
--- End quote ---
And we see this in the bench application when the DVI connected monitor goes to sleep.
--- Quote ---setiathome_CUDA: cudaGetDeviceCount() call failed.
setiathome_CUDA: No CUDA devices found
setiathome_CUDA: Found 0 CUDA device(s):
setiathome_CUDA: No SETI@home capabale CUDA GPU found...
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version