Forum > GPU crunching
Completed, validation inconclusive
Jason G:
FYI: 'first cut' (untested) Win64 updated installer is just upload to Beta Downloads now. Will start a beta thread for that one shortly.
efmer (fred):
--- Quote from: Jason G on 07 Jul 2009, 07:03:19 am ---
--- Quote from: Fred M on 07 Jul 2009, 06:58:55 am ---I expect a driver problem... What version do you recommend or is tested on a 295...
--- End quote ---
The top machines with 295's (on x64) appear to be using either 185.85 or the slightly newer one as you are. It might be worth to consider also checking mobo chipset drivers etc, are up to date, among the other checks mentioned. Beyond that I have no direct experience with 295's.
--- End quote ---
On both machines I did a downgrade of the driver to 185.85
1) V11 VLAR killer still a lot of -9 errors 100+
2) V12 VLAR killer the -9 errors are almost gone. 100+
Raistmer:
And wingmate shows no overflow in task?
efmer (fred):
--- Quote from: Raistmer on 09 Jul 2009, 04:17:07 am ---And wingmate shows no overflow in task?
--- End quote ---
No overflow on the wingman, most of the time.
And the WU is not marked as invalid for some reason but as Initial
SETI@Home Informational message -9 result_overflow - Initial
And 2 cards, different brands, all giving the same error?
Is the Cuda buffer the same length?
And... at the moment it takes forever to see any changes in the database, that is waaaay behind.
Raistmer:
most likely it's driver issues.
Try to use V12+185.85+CUDA RT2.2
BTW, do overflows disappear after restart (at least for awhile)? Do result's stderrs contain any CUDA-related errors?
I had overflows on x64 host with older driver+CUDA RT time to time before. Restarting usually helped.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version