i cant update the drivers as its windows 7 beta, and nvidia just say use the ones that came with the ms install

i'm happy to stay with the previous version for now and wait for nvidia to come up with goods, unless installing vista graphics drivers is possible



keep up the good work :-)

---

63. (1) (b) "music" includes sounds wholly or predominantly characterised by the emission of a succession of repetitive beats

i cant update the drivers as its windows 7 beta, and nvidia just say use the ones that came with the ms install

More specifically, they say to use Windows Update to get the drivers.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

This build devoted to all who still experiences videodriver crash on VLAR tasks. It should abort its own execution if VLAR with AR <0.14 is detected (temporary measure, of course).
All thanks go to Crunch3r & Maikfor this mod.

http://lunatics.kwsn.net/gpu-crunching/modified-seti-mb-cuda-opt-ap-package-for-full-gpu-utilize.msg12725.html#msg12725

Well, I got my first driver crash. Downloaded your new V5A and restarted. It found a bunch of the problimatic WUs. This is one of them...

Task ID 1121437669
Name 08no08ab.19433.81017.6.8.62_0
Workunit 394710096
Created 13 Jan 2009 14:32:36 UTC
Sent 13 Jan 2009 16:05:24 UTC
Received 14 Jan 2009 0:48:51 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -6 (0xfffffffffffffffa)
Computer ID 4731257
Report deadline 1 Feb 2009 22:59:07 UTC
CPU time 0
stderr out

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.123395 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\seti_header.cpp
Line: 207


</stderr_txt>
]]>

Validate state Invalid
Claimed credit 0
Granted credit 0
application version 6.06

---

PROUD MEMBER OF Team Starfire World BOINC

Fine it seems you are first who confirmed that tis build works as intended. I have no VLARs now so can't do online testing.
This aborted task will go somwhere else and your host will be free from next driver crash that can influent on other results.
Till 6.08 arrives it seems viable solution for VLAR problem supplied.

(BTW, it worth to check 6.07 on beta - maybe it already solves VLAR issue for your GPU. It's more probably for faster GPU and less probably for mid to low end GPUs)

Probably wouldn't be for me then, I only have a GeForce 8500GT. A midrange at best. Hope the information I provided helps.

---

PROUD MEMBER OF Team Starfire World BOINC

Finally got my board today! started about an hour ago ,and have finished ~10 14 credit wus with 2 already recieving credit.
Using the v5a, with 180.48 on my win pd. Nothing running on my cpu no APS' downloaded yet. You can see on my tasks, before gpu 14 credits took 3800 sec. now about 300..I like it. Thanks fot all the work..cool your lastest app. came just as I started!!

Edit.. Well It kicked out a bunch of wus but didn't put any time in them.I guess they were the ones I don't want. No crashes, everything looks ok.

I installed Raistmer's_opt_package_V5.rar. I have amd 64 x2 6000+ and 8600GT (with ForceWare 180.84). after 11 min CUDA working computation error.

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce 8600 GT
totalGlobalMem = 268107776
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1188000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 4
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 8600 GT is okay
SETI@home using CUDA accelerated device GeForce 8600 GT
Rise priority modification by Raistmer based on rev400 of SETI@home sources
Priority of worker thread rised successfully
Total GPU memory 268107776 free GPU memory 224959232
setiathome_enhanced 6.02 Visual Studio/Microsoft C++
libboinc: 6.3.22

Work Unit Info:
...............
WU true angle range is : 0.008030
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_GetPowerSpectrum 0.00043 0.00000
v_ChirpData 0.01615 0.00000
v_Transpose4 0.01088 0.00000
FPU opt folding 0.01025 0.00000
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce 8600 GT
totalGlobalMem = 268107776
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1188000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 4
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 8600 GT is okay
SETI@home using CUDA accelerated device GeForce 8600 GT
Rise priority modification by Raistmer based on rev400 of SETI@home sources
Priority of worker thread rised successfully
Total GPU memory 268107776 free GPU memory 224959232
Restarted at 0.22 percent.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BTR/seticuda/seti_boinc/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unknown error.

</stderr_txt>
]]>

WU true angle range is : 0.008030
Optimal function choices:

You need version V5a VLAR version

---

There is known "feature" of BOINC 6.4.5 that now works more as bug - it sets process priority for CUDA application to "Normal" instead of "Idle"
It helps nothing because "Idle" priority of worker thread has the same value for "Normal" and "Idle" priorities of process (so called priority class) so thread priority should be adjusted, not process priority (not priority class). Setting process priority to "Normal" excessively increase control thread priority that caused sluggish OS behavior.

So for Don's (Geek@Play) request I did another cleanup for BOINC - now modded CUDA MB will adjust priority class as well. Hope it will give more smooth execution.

http://lunatics.kwsn.net/gpu-crunching/modified-seti-mb-cuda-opt-ap-package-for-full-gpu-utilize.msg12177.html#msg12177

I also tried the V5(a) on my 8800GTS 512 and it seems to work, it happily crunches away even after a VLAR unit:

Client state Compute error
Exit status -6 (0xfffffffffffffffa)
Computer ID 4242105
Report deadline 6 Feb 2009 14:18:00 UTC
CPU time 0
stderr out <core_client_version>6.5.0</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.009126 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\seti_header.cpp
Line: 207


</stderr_txt>
]]>

Validate state Invalid


Trying the *b* package now since the os was a bit sluggish with the first...

Keep it up!

it still keeps stalling tho, making me having to baby sit my computer.

---

it still keeps stalling tho, making me having to baby sit my computer.

More detailed info, please.

WU true angle range is : 0.008030
Optimal function choices:

You need version V5a VLAR version

I tried Raistmer's_opt_package_V5a and Raistmer's_opt_package_V5b, but the same error.

*in boinc messages*:

14/01/2009 17:49:33|SETI@home|Starting 08no08ab.7216.4571.9.8.113_1
14/01/2009 17:49:33|SETI@home|Starting task 08no08ab.7216.4571.9.8.113_1 using setiathome_enhanced version 603
14/01/2009 17:49:34|SETI@home|Computation for task 08no08ab.7216.4571.9.8.113_1 finished
14/01/2009 17:49:34|SETI@home|Output file 08no08ab.7216.4571.9.8.113_1_0 for task 08no08ab.7216.4571.9.8.113_1 absent


*in seti results*:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.008610 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\seti_header.cpp
Line: 207


</stderr_txt>
]]>



Any suggestions!??

WU true angle range is : 0.008030
Optimal function choices:

You need version V5a VLAR version

I tried Raistmer's_opt_package_V5a and Raistmer's_opt_package_V5b, but the same error.

*in boinc messages*:

14/01/2009 17:49:33|SETI@home|Starting 08no08ab.7216.4571.9.8.113_1
14/01/2009 17:49:33|SETI@home|Starting task 08no08ab.7216.4571.9.8.113_1 using setiathome_enhanced version 603
14/01/2009 17:49:34|SETI@home|Computation for task 08no08ab.7216.4571.9.8.113_1 finished
14/01/2009 17:49:34|SETI@home|Output file 08no08ab.7216.4571.9.8.113_1_0 for task 08no08ab.7216.4571.9.8.113_1 absent


*in seti results*:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.008610 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\seti_header.cpp
Line: 207


</stderr_txt>
]]>



Any suggestions!??

That's what the app is supposed to do. This is VLAR tasks, Very Low Angle Range tasks (0.1 angle range and below). If it did not create this error it might freeze up your computer or cause problems in tasks after this one. Everything is fine, just continue. Once you are out of this AR you should notice the tasks complete.

---

"14/01/2009 17:49:33|SETI@home|Starting task 08no08ab.7216.4571.9.8.113_1 using setiathome_enhanced version 603"


Raistmer, why is he still getting version 603 Work units? Shouldn't that be at least 606?

---

PROUD MEMBER OF Team Starfire World BOINC

he probably had 6.03 in his cache when he started using the mod app, and the mod app is able to process the 6.03 tasks.

---

Sorry, but I'm new in this CUDA working. You are saying that is problem in SETI, in the way they make WU!?? but why is problem in CUDA processing, not also in CPU processing? i think that CPU will process this WU, or not!?? thx

It is not a problem in SETI it is a problem in CUDA. When it tries to process either a VLAR or a VHAR wu it causes the graphics driver to freeze. Right now, Raistmer's package provides a work-around for this by killing these. Hopefully someone will be able to cure this problem in the future.

---

PROUD MEMBER OF Team Starfire World BOINC

WU true angle range is : 0.008030
Optimal function choices:

You need version V5a VLAR version

I tried Raistmer's_opt_package_V5a and Raistmer's_opt_package_V5b, but the same error.

*in boinc messages*:

14/01/2009 17:49:33|SETI@home|Starting 08no08ab.7216.4571.9.8.113_1
14/01/2009 17:49:33|SETI@home|Starting task 08no08ab.7216.4571.9.8.113_1 using setiathome_enhanced version 603
14/01/2009 17:49:34|SETI@home|Computation for task 08no08ab.7216.4571.9.8.113_1 finished
14/01/2009 17:49:34|SETI@home|Output file 08no08ab.7216.4571.9.8.113_1_0 for task 08no08ab.7216.4571.9.8.113_1 absent


*in seti results*:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>

VLAR WU (AR: 0.008610 )detected... autokill initialised
SETI@home error -6 Bad workunit header

File: ..\seti_header.cpp
Line: 207


</stderr_txt>
]]>



Any suggestions!??

No suggestions, all go as it should. Keep crunching.