I got lot of Completed, validation inconclusive 100.... on different computers.http://setiathome.berkeley.edu/workunit.php?wuid=473007709Are these WU really bad or is something wrong with this VLAR KILL version.Because my wingman looks ok on the CPU version.
Quote from: Fred M on 07 Jul 2009, 03:05:14 amI got lot of Completed, validation inconclusive 100.... on different computers.http://setiathome.berkeley.edu/workunit.php?wuid=473007709Are these WU really bad or is something wrong with this VLAR KILL version.Because my wingman looks ok on the CPU version.It's hard to tell from a single example, since either result could be closer to 'right'. If you seee more examples of this mismatch, let us know. There could have been some problems in either processing run, host or build, communications, cosmic rays causing one-off bit errors in ram etc. I would be inclined to watch to see how the reissue comes in, but only get worried if it happens a lot (repeatability is important). The redundancy process seems to be doing its job.
Since I haven't seen reports of validation issues with the build, I would suggest to begin some basic checks without boinc running, to eliminate some possible issues. That might include sytem memory , temps, OC backoff, normal divers checks etc .For the Video Card I use AtiTool (http://www.techpowerup.com/atitool) to scan for artefacts (Yes it does so work on nVidia cards! ). Even If that goes OKay for an hours running (without any artefacts / beeping at you in 'Scan for Artefacts Mode'), I would double check for known issues with those drivers/cards too (especially CUDA related), maybe there is something there that may warrant looking at another version.
But it seem highly unlikely the this happens on two different computers with different brand 295 cards.
Quote from: Fred M on 07 Jul 2009, 06:23:55 amBut it seem highly unlikely the this happens on two different computers with different brand 295 cards.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.
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.85Got Cuda 2.2, MB_6.08_mod_CUDA_V11_VLARKill_refined.exe. Is the VLARKILL V12 worth trying and with what memory model.
Quote from: Fred M on 07 Jul 2009, 06:45:31 amCan'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.85Got Cuda 2.2, MB_6.08_mod_CUDA_V11_VLARKill_refined.exe. Is the VLARKILL V12 worth trying and with what memory model.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.
I expect a driver problem... What version do you recommend or is tested on a 295...
Quote from: Fred M on 07 Jul 2009, 06:58:55 amI expect a driver problem... What version do you recommend or is tested on a 295... 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.
And wingmate shows no overflow in task?
