Forum > GPU crunching
Completed, validation inconclusive
Jason G:
--- Quote from: Fred M on 07 Jul 2009, 06:23:55 am ---But it seem highly unlikely the this happens on two different computers with different brand 295 cards.
--- End quote ---
I agree, but not if there's some common factor, like cuda driver bug. The point is to eliminate things that it isn't, to narrow the field to find/isolate whatever the actual problem is, rather than guessing that there is something wrong with an app that others aren't reporting the same issues with.
[Edit: x64 Installer will be available soon in Beta, perhaps V12 with updated Cuda DLLs' (Totally different build) might either show same symptoms or correct them, in either case, that would confirm or eliminate some suspects]
efmer (fred):
--- Quote from: Jason G on 07 Jul 2009, 06:40:18 am ---
--- Quote from: Fred M on 07 Jul 2009, 06:23:55 am ---But it seem highly unlikely the this happens on two different computers with different brand 295 cards.
--- End quote ---
I agree, but not if there's some common factor, like cuda driver bug. The point is to eliminate things that it isn't, to narrow the field to find/isolate whatever the actual problem is, rather than guessing that there is something wrong with an app that others aren't reporting the same issues with.
--- End quote ---
Can't have anything to do with the bad WU's they are sending out lately. With a lot of noise in it, because I this is a memory overflow error.
I will try putting one machine to an earlier driver 185.85
Got Cuda 2.2, MB_6.08_mod_CUDA_V11_VLARKill_refined.exe. Is the VLARKILL V12 worth trying and with what memory model.
Jason G:
--- Quote from: Fred M on 07 Jul 2009, 06:45:31 am ---Can't have anything to do with the bad WU's they are sending out lately. With a lot of noise in it, because I this is a memory overflow error.
I will try putting one machine to an earlier driver 185.85
Got Cuda 2.2, MB_6.08_mod_CUDA_V11_VLARKill_refined.exe. Is the VLARKILL V12 worth trying and with what memory model.
--- End quote ---
WUs? a possibility, but unlikely, and if we can isolate it to that then great.
That's the same setup I used for a few months until yesterday, with a much lesser card (9600GSO).
V12 will be worth trying, and has some speed enhancements put in by Raistmer, and we've tweaked it a bit to be more display friendly. So yes it's worth a try, but won't necessarily solve whatever is causing your difficulty, but if it does the same, it would prove it wasn't the particular app build at least.
efmer (fred):
--- Quote from: Jason G on 07 Jul 2009, 06:53:44 am ---
--- Quote from: Fred M on 07 Jul 2009, 06:45:31 am ---Can't have anything to do with the bad WU's they are sending out lately. With a lot of noise in it, because I this is a memory overflow error.
I will try putting one machine to an earlier driver 185.85
Got Cuda 2.2, MB_6.08_mod_CUDA_V11_VLARKill_refined.exe. Is the VLARKILL V12 worth trying and with what memory model.
--- End quote ---
WUs? a possibility, but unlikely, and if we can isolate it to that then great.
That's the same setup I used for a few months until yesterday, with a much lesser card (9600GSO).
V12 will be worth trying, and has some speed enhancements put in by Raistmer, and we've tweaked it a bit to be more display friendly. So yes it's worth a try, but won't necessarily solve whatever is causing your difficulty, but if it does the same, it would prove it wasn't the particular app build at least.
--- End quote ---
I expect a driver problem... What version do you recommend or is tested on a 295...
Jason G:
--- 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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version