| Author |
Message |
|---|
|
|
|
Well since today/yesterday my gtx260 is giving out only compute errors! I didnt change anything on it so I wonder how that is possible.
here is a Link from a compute error WU:
http://www.gpugrid.net/result.php?resultid=540426
ty for and advices! |
|
|
MarkJ  Volunteer moderator
Volunteer tester
Send message
Joined: 24 Dec 08
Posts: 738
Credit: 200,909,904
RAC: 0
Level
Scientific publications
      |
Well since today/yesterday my gtx260 is giving out only compute errors! I didnt change anything on it so I wonder how that is possible.
here is a Link from a compute error WU:
http://www.gpugrid.net/result.php?resultid=540426
ty for and advices!
You might not have noticed but the GPUgrid app went from 6.62 to 6.63 in the last day or so.
I also got a compute error on my GTS250, and its brand new. My wu is here and has a nice dump in it. Possibly something to do with the app upgrade.
____________
BOINC blog |
|
|
|
|
|
Ur card atleast gave out an finished Wu after the corrupt wu, mine gtx260 gave out 11 computing errors till today, so something must be really wrong!
Currently testing some seti Wus, since i cant get any new from gpugrid and they are doin fine ;< |
|
|
|
|
|
It's remarkable that your problems started right when the app switched from 6.62 to 6.63. Others are running fine with the new client, or at least don't get errors, so this may not neccessarily be related.
Did you do basic trouble shooting? Restart BOINC, reboot, power off and remove power cord for >10 mins, update NV driver (or downgrade if you have some latest beta)?
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
|
|
Well i can reboot my pc now and see when i get new Wus, since it says that i wont get any new since the daily limit is reached :s |
|
|
MarkJ Volunteer moderator
Volunteer tester
Send message
Joined: 24 Dec 08
Posts: 738
Credit: 200,909,904
RAC: 0
Level
Scientific publications
|
Well i can reboot my pc now and see when i get new Wus, since it says that i wont get any new since the daily limit is reached :s
According to your computer details you have 178.28 driver which is fairly old. You might want to upgrade it. I believe the latest "release" version is 182.50, but can't vouch for it as I haven't tried it. You can get them from the Nvidia web site. Click on the Download Drivers button.
I am running 182.08 drivers on the rig in question and a beta-test version of BOINC (6.6.23). It had completed one GPUgrid wu without any issues and its 78% through another one at the moment. The GTS250 was fitted yesterday so it has been rebooted/powered off fairly recently.
I have BOINC 6.6.23 on all my other cuda-capable machines and 182.06 drivers.
____________
BOINC blog |
|
|
|
|
|
Well i was very satisfied with the driver i have now since it got my 260 to 15k rac or even more i cant remember correctly. So changin the driver will be the LAST option! |
|
|
|
|
|
What you needed to get the RAC up was time, not a special driver. Check out the 185 series (not sure if .65 or .66 is for XP32), it's a little faster than previous versions.
And don't worry if your RAC drops soon: just remember that right now you're not doing any GPU-Grid work and it will take about 1 months for this incident to disappear from the stats. And the credits have recently been increased to bring them in line with seti.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
|
|
Where can i find news about the changed GPUGRID thing then? or arent there any? O,o |
|
|
|
|
|
Which *thing*? There's a sticky about the new apps and the credit calculations here.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
|
|
The driver might be the first thing you might want to try...
The compiled a new application, and likely with the latest development kit and there is the slightest possibility that some subtle new feature was included in the new application which might mean that an older driver will not work that well.
I have been running off quite a few of these tasks now on GTX295 and GTX260 cards with no failures that I have been able to see ... |
|
|
|
|
|
I now tryd the restart comp / cut power thing and i got an computing error, so I tested the latest official driver for my card 182.50 and it directly stopped again with a computing error!
What more can I do now ? ;< |
|
|
|
|
|
It looks like you have a task now for about 2.5 hrs. and I don't see an error returned yet p1410000-GIANNI_pYIpYV0804-7-10-RND_0, did it error?
If you are still having problems maybe try running some stress tests on the card itself to see if we can help you narrow down where you problem is, isolating it from GPUGrid.
Steve |
|
|
jrobbioSend message
Joined: 13 Mar 09
Posts: 59
Credit: 324,366
RAC: 0
Level
Scientific publications
 |
I now tryd the restart comp / cut power thing and i got an computing error, so I tested the latest official driver for my card 182.50 and it directly stopped again with a computing error!
What more can I do now ? ;<
Any reason why you still have SP2 on the your XP machines?
Try enabling some of these Flags (or Here) in Boinc and post the error messages.
Try:
<coproc_debug>
<guirpc_debug>
<mem_usage_debug>
<state_debug>
<statefile_debug>
<task_debug>
Rob |
|
|
|
|
It looks like you have a task now for about 2.5 hrs. and I don't see an error returned yet p1410000-GIANNI_pYIpYV0804-7-10-RND_0, did it error?
If you are still having problems maybe try running some stress tests on the card itself to see if we can help you narrow down where you problem is, isolating it from GPUGrid.
Steve
I wont do any stress tests, cuz Seti wus run without any problems and so did the grid wus, before this update stuff!
and to that xml stuff, i neither wont do that because its more then user unfriendly, all this stuff is explained in english and english is not my mother tongue so its kinda hard to understand what its all about and i really dont have the time to figure all that out you know.
If there is any ideas for a more simply fix of this issue you are more then welcome to hook me up, but as long as there isnt ill stay at seti even tho i think its not as good as GPUGRID :| |
|
|
jrobbioSend message
Joined: 13 Mar 09
Posts: 59
Credit: 324,366
RAC: 0
Level
Scientific publications
|
..all this stuff is explained in english and english is not my mother tongue so its kinda hard to understand what its all about and i really dont have the time to figure all that out you know.
Translated via Bablefish in German. Should be "reasonably" accurate |
|
|
|
|
..all this stuff is explained in english and english is not my mother tongue so its kinda hard to understand what its all about and i really dont have the time to figure all that out you know.
Translated via Bablefish in German. Should be "reasonably" accurate
I cant find the cc_config.xml which i need to do thoose configurations(?). Tryd evev via the windows search and i have unhidden all files. |
|
|
STE\/ESend message
Joined: 18 Sep 08
Posts: 368
Credit: 324,597,298
RAC: 642,912
Level
Scientific publications
|
|
It should be in the BOINC Folder Directory, the one with the Project's & Slots in it. But I have seen some of mine without the cc_config.xml file in it before & have had to just add the whole file. |
|
|
|
|
|
I just cant find it lol :< |
|
|
|
|
|
The cc_config.xml file is not there unless you create it, as normal users wouldn't have to use it anyway.
EDIT: go to "the BOINC Folder Directory, the one with the Project's & Slots in it", create a new textfile, copy the contents into it and name it "cc_config.xml" instead of "*.txt".
What about the WU which is still in progress on your machine? Is it running or waiting to run because of seti?
Regarding a stress test: your problem seems to be software related. However, as has been discussed elsewhere before, SETI is putting less stress on the GPUs. So that you can run SETI does not neccessarily mean that your hardware is fine for GPU-Grid. I'd expect a half or one hour of 3D Mark06 to be sufficient to rule out hardware problems.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
|
|
And again, GPUGRID runned perfect untill thoose new application stuff came!
also I still aint got the slightest clue whats about this xml stuff and what exactly i got to do.. -.-
and the in progress wu has also an computing error i just didnt upload it yet cuz i set gpugrid on pause so i dont get new wus which error out.
edit_ I just tested to run a wu on standart clocks, it immedatly errord out also! |
|
|
jrobbioSend message
Joined: 13 Mar 09
Posts: 59
Credit: 324,366
RAC: 0
Level
Scientific publications
|
edit_ I just tested to run a wu on standart clocks, it immedatly errord out also!
Do you have more than one profile on your Windows XP Pro machine? I had problems with my XP home machine where it errored out when I logged in with certain profiles (in my situation it was concurrently). Have you started using another profile recently?
Rob |
|
|
|
|
|
You can set GPU-Grid to "no new work" in the projects tab.
The stadard clock attempt tells us that the problem is very likely software and not hardware. You probably don't need the stability test, but a single run of 3D Mark wouldn't hurt, either.
What I'd try: use driver cleaner (or a similar tool) to completly deinstall the driver. Then check again with maybe 182.50. Version 181.20 would also be worth a try, since it runs app 6.63 just fine on your other machine. Or the 185.6x beta.
And the problem seems to happen right at the WU startup. The app doesn't even initialize properly. Thats why someone asked you for the BOINC debug info, maybe some hint can be found there. Which part of the instructions is it that you don't understand?
And again, GPUGRID runned perfect untill thoose new application stuff came!
It's a major science update and your machine is the only reported case of such problems.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
|
|
I just removed the driver with driver cleaner pro and installed 181.20, started a new WU and it give an comeputing error out right at the beginning again! |
|
|
|
|
I just removed the driver with driver cleaner pro and installed 181.20, started a new WU and it give an comeputing error out right at the beginning again!
See: Client Configuration
Take this following snippet:
<cc_config>
<log_flags>
<file_xfer>0</file_xfer>
<checkpoint_debug>0</checkpoint_debug>
<cpu_sched_debug>0</cpu_sched_debug>
<coproc_debug>0</coproc_debug>
<guirpc_debug>0</guirpc_debug>
<mem_usage_debug>0</mem_usage_debug>
<state_debug>0</state_debug>
<task_debug>0</task_debug>
<statefile_debug>0</statefile_debug>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<report_results_immediately>0</report_results_immediately>
<zero_debts>0</zero_debts>
</options>
</cc_config>
Paste it into a notepad file and save it with the name cc_config.xml
Edit the file and change the "0" flags to "1" for the debug sets you want to turn on ...
Open the directory where you saved the file and check to make sure it is named cc_config.xml and not cc_config.xml.txt (if it has .txt attached, rename it to the correct name).
move/copy the file to the BOINC directory. Where the client_state.xml file is (it may be hidden, but if you search for the client_state file and include hidden directories you should be able to find it).
In the Advanced Menu, select "Read configuration file..."
Save the logs in the messages tab after the failure and post them here...
Edit the file to change the flags to 0, and re-read the configuration file.
{edit}
Added flags from message below ...
{edit2}
Unset RTI to zero
Also note, the clear debts only works on BOINC Client restarts, it will not clear debts on a read while BOINC is running... |
|
|
|
|
|
26.02.2006 05:47:09 Starting BOINC client version 6.6.20 for windows_intelx86
26.02.2006 05:47:09 log flags: task, sched_ops, task_debug, guirpc_debug, mem_usage_debug, coproc_debug
26.02.2006 05:47:09 Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
26.02.2006 05:47:09 Data directory: C:\Dokumente und Einstellungen\zept0r\Eigene Dateien
26.02.2006 05:47:09 Running under account Philipp
26.02.2006 05:47:09 Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz [x86 Family 6 Model 15 Stepping 2]
26.02.2006 05:47:09 Processor features: fpu tsc pae nx sse sse2 mmx
26.02.2006 05:47:09 OS: Microsoft Windows XP: Professional x86 Editon, Service Pack 2, (05.01.2600.00)
26.02.2006 05:47:09 Memory: 2.00 GB physical, 3.85 GB virtual
26.02.2006 05:47:09 Disk: 74.52 GB total, 1.78 GB free
26.02.2006 05:47:09 Local time is UTC +1 hours
26.02.2006 05:47:09 CUDA device: GeForce GTX 260 (driver version 18120, CUDA version 1.3, 896MB, est. 96GFLOPS)
26.02.2006 05:47:09 Not using a proxy
26.02.2006 05:47:09 [state_debug] Client state summary:
26.02.2006 05:47:09 5 projects:
26.02.2006 05:47:09 http://boinc.fzk.de/poem/ min RPC -1073088.593750.0 seconds from now
26.02.2006 05:47:09 http://cbl-boinc-server2.cs.technion.ac.il/superlinkattechnion/ min RPC -475819.031250.0 seconds from now
26.02.2006 05:47:09 http://setiathome.berkeley.edu/ min RPC -311.562500.0 seconds from now
26.02.2006 05:47:09 http://www.gpugrid.net/ min RPC -176.125000.0 seconds from now
26.02.2006 05:47:09 http://www.rechenkraft.net/yoyo/ min RPC -1814778.968750.0 seconds from now
26.02.2006 05:47:09 113 file_infos:
26.02.2006 05:47:09 poem_1.0_windows_intelx86 status:1 inactive
26.02.2006 05:47:09 JParmJan97 status:1 inactive
26.02.2006 05:47:09 loadd_1.22_windows_intelx86.exe status:1 inactive
26.02.2006 05:47:09 killd_1.22_windows_intelx86.exe status:1 inactive
26.02.2006 05:47:09 superlink_1.22_windows_intelx86.exe status:1 inactive
26.02.2006 05:47:09 template_1.22_windows_intelx86 status:1 inactive
26.02.2006 05:47:09 superlink_logo_minimized.gif status:1 inactive
26.02.2006 05:47:09 arecibo_181.png status:1 inactive
26.02.2006 05:47:09 sah_40.png status:1 inactive
26.02.2006 05:47:09 sah_banner_290.png status:1 inactive
26.02.2006 05:47:09 sah_ss_290.png status:1 inactive
26.02.2006 05:47:09 setiathome_6.08_windows_intelx86__cuda.exe status:1 inactive
26.02.2006 05:47:09 cudart.dll status:1 inactive
26.02.2006 05:47:09 cufft.dll status:1 inactive
26.02.2006 05:47:09 libfftw3f-3-1-1a_upx.dll status:1 inactive
26.02.2006 05:47:09 setiathome-6.08_cuda_AUTHORS status:1 inactive
26.02.2006 05:47:09 setiathome-6.08_cuda_COPYING status:1 inactive
26.02.2006 05:47:09 setiathome-6.08_cuda_COPYRIGHT status:1 inactive
26.02.2006 05:47:09 setiathome-6.08_cuda_README status:1 inactive
26.02.2006 05:47:09 seti_608.jpg status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.162 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.210 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.195 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.181 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.138 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.184 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.207 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.186 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.189 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.162_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.210_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.195_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.181_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.138_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.184_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.207_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.186_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.189_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.255 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.233 status:1 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.255_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.233_1_0 status:0 inactive
26.02.2006 05:47:09 28dc08aa.32338.8252.8.8.108 status:1 inactive
26.02.2006 05:47:09 28dc08aa.32338.8252.8.8.108_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08ab.18652.384303.7.8.122 status:1 inactive
26.02.2006 05:47:09 27dc08ab.18652.384303.7.8.122_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.28555.9888.7.8.0 status:1 inactive
26.02.2006 05:47:09 27dc08aa.28555.9888.7.8.0_0_0 status:0 inactive
26.02.2006 05:47:09 28dc08aa.32338.11933.8.8.42 status:1 inactive
26.02.2006 05:47:09 28dc08aa.32338.11933.8.8.42_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.28555.11524.7.8.253 status:1 inactive
26.02.2006 05:47:09 27dc08aa.28555.11524.7.8.253_1_0 status:0 inactive
26.02.2006 05:47:09 03fe09af.12191.18068.6.8.89 status:1 inactive
26.02.2006 05:47:09 03fe09af.12191.18068.6.8.89_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08ab.18652.391256.7.8.161 status:1 inactive
26.02.2006 05:47:09 27dc08ab.18652.391256.7.8.161_1_0 status:0 inactive
26.02.2006 05:47:09 28dc08aa.32338.14796.8.8.123 status:1 inactive
26.02.2006 05:47:09 28dc08aa.32338.14796.8.8.123_1_0 status:0 inactive
26.02.2006 05:47:09 03fe09af.12191.20113.6.8.44 status:1 inactive
26.02.2006 05:47:09 03fe09af.12191.20113.6.8.44_1_0 status:0 inactive
26.02.2006 05:47:09 03fe09af.12191.20522.6.8.43 status:1 inactive
26.02.2006 05:47:09 03fe09af.12191.20522.6.8.43_0_0 status:0 inactive
26.02.2006 05:47:09 28dc08aa.32338.16023.8.8.122 status:1 inactive
26.02.2006 05:47:09 28dc08aa.32338.16023.8.8.122_1_0 status:0 inactive
26.02.2006 05:47:09 28dc08aa.32338.16432.8.8.235 status:1 inactive
26.02.2006 05:47:09 28dc08aa.32338.16432.8.8.235_1_0 status:0 inactive
26.02.2006 05:47:09 03fe09af.12191.22567.6.8.121 status:1 inactive
26.02.2006 05:47:09 03fe09af.12191.22567.6.8.121_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08ab.18652.396164.7.8.62 status:1 inactive
26.02.2006 05:47:09 27dc08ab.18652.396164.7.8.62_1_0 status:0 inactive
26.02.2006 05:47:09 29ja09aa.1052.977138.8.8.118 status:1 inactive
26.02.2006 05:47:09 29ja09aa.1052.977138.8.8.118_0_0 status:0 inactive
26.02.2006 05:47:09 27dc08ab.18652.396982.7.8.127 status:1 inactive
26.02.2006 05:47:09 27dc08ab.18652.396982.7.8.127_1_0 status:0 inactive
26.02.2006 05:47:09 27dc08aa.28555.17659.7.8.219 status:1 inactive
26.02.2006 05:47:09 27dc08aa.28555.17659.7.8.219_0_0 status:0 inactive
26.02.2006 05:47:09 logops3grid.png status:1 inactive
26.02.2006 05:47:09 project_1.png status:1 inactive
26.02.2006 05:47:09 project_2.png status:1 inactive
26.02.2006 05:47:09 project_3.png status:1 inactive
26.02.2006 05:47:09 acemd_6.63_windows_intelx86__cuda.exe status:1 inactive
26.02.2006 05:47:09 tcl85.dll status:1 inactive
26.02.2006 05:47:09 cudart.dll status:1 inactive
26.02.2006 05:47:09 cufft.dll status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-LICENSE status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-COPYRIGHT status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-p160000-GIANNI_pYEpYI1004-6-10-RND_1 status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-p160000-GIANNI_pYEpYI1004-6-10-RND_2 status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-p160000-GIANNI_pYEpYI1004-6-10-RND_3 status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-pdb_file status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-psf_file status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-par_file status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-p160000 status:1 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0_0 status:-161 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0_1 status:-161 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0_2 status:-161 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0_3 status:-161 inactive
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0_4 status:0 inactive
26.02.2006 05:47:09 muonwrapper_1.10_windows_intelx86.exe status:1 inactive
26.02.2006 05:47:09 yoyo_graphics_1.01_windows_intelx86.exe status:1 inactive
26.02.2006 05:47:09 muon_1.00_logo.jpg status:1 inactive
26.02.2006 05:47:09 muon44d_win32.exe status:1 inactive
26.02.2006 05:47:09 Helvetica.txf status:1 inactive
26.02.2006 05:47:09 muon_unzip_1.01_win32.exe status:1 inactive
26.02.2006 05:47:09 muon_user_1.01.txt status:1 inactive
26.02.2006 05:47:09 muonjob_1.04_windows_intelx86.xml status:1 inactive
26.02.2006 05:47:09 muon_config_1.02.txt status:1 inactive
26.02.2006 05:47:09 muon_datafiles_1.01.zip status:1 inactive
26.02.2006 05:47:09 default_stat_icon_01.png status:1 inactive
26.02.2006 05:47:09 rkn_01.png status:1 inactive
26.02.2006 05:47:09 ogr_01.png status:1 inactive
26.02.2006 05:47:09 evo_01.png status:1 inactive
26.02.2006 05:47:09 muon_01.png status:1 inactive
26.02.2006 05:47:09 5 app_versions
26.02.2006 05:47:09 poem 100
26.02.2006 05:47:09 loadd 122
26.02.2006 05:47:09 setiathome_enhanced 608
26.02.2006 05:47:09 acemd 663
26.02.2006 05:47:09 muon 110
26.02.2006 05:47:09 29 workunits
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.162
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.210
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.195
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.181
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.138
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.184
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.207
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.186
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.189
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.255
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.233
26.02.2006 05:47:09 28dc08aa.32338.8252.8.8.108
26.02.2006 05:47:09 27dc08ab.18652.384303.7.8.122
26.02.2006 05:47:09 27dc08aa.28555.9888.7.8.0
26.02.2006 05:47:09 28dc08aa.32338.11933.8.8.42
26.02.2006 05:47:09 27dc08aa.28555.11524.7.8.253
26.02.2006 05:47:09 03fe09af.12191.18068.6.8.89
26.02.2006 05:47:09 27dc08ab.18652.391256.7.8.161
26.02.2006 05:47:09 28dc08aa.32338.14796.8.8.123
26.02.2006 05:47:09 03fe09af.12191.20113.6.8.44
26.02.2006 05:47:09 03fe09af.12191.20522.6.8.43
26.02.2006 05:47:09 28dc08aa.32338.16023.8.8.122
26.02.2006 05:47:09 28dc08aa.32338.16432.8.8.235
26.02.2006 05:47:09 03fe09af.12191.22567.6.8.121
26.02.2006 05:47:09 27dc08ab.18652.396164.7.8.62
26.02.2006 05:47:09 29ja09aa.1052.977138.8.8.118
26.02.2006 05:47:09 27dc08ab.18652.396982.7.8.127
26.02.2006 05:47:09 27dc08aa.28555.17659.7.8.219
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND
26.02.2006 05:47:09 29 results
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.162_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.210_1 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.195_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.181_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.138_1 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.184_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.207_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.186_0 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.189_1 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.255_1 state:2
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.233_1 state:2
26.02.2006 05:47:09 28dc08aa.32338.8252.8.8.108_0 state:2
26.02.2006 05:47:09 27dc08ab.18652.384303.7.8.122_1 state:2
26.02.2006 05:47:09 27dc08aa.28555.9888.7.8.0_0 state:2
26.02.2006 05:47:09 28dc08aa.32338.11933.8.8.42_1 state:2
26.02.2006 05:47:09 27dc08aa.28555.11524.7.8.253_1 state:2
26.02.2006 05:47:09 03fe09af.12191.18068.6.8.89_1 state:2
26.02.2006 05:47:09 27dc08ab.18652.391256.7.8.161_1 state:2
26.02.2006 05:47:09 28dc08aa.32338.14796.8.8.123_1 state:2
26.02.2006 05:47:09 03fe09af.12191.20113.6.8.44_1 state:2
26.02.2006 05:47:09 03fe09af.12191.20522.6.8.43_0 state:2
26.02.2006 05:47:09 28dc08aa.32338.16023.8.8.122_1 state:2
26.02.2006 05:47:09 28dc08aa.32338.16432.8.8.235_1 state:2
26.02.2006 05:47:09 03fe09af.12191.22567.6.8.121_0 state:2
26.02.2006 05:47:09 27dc08ab.18652.396164.7.8.62_1 state:2
26.02.2006 05:47:09 29ja09aa.1052.977138.8.8.118_0 state:2
26.02.2006 05:47:09 27dc08ab.18652.396982.7.8.127_1 state:2
26.02.2006 05:47:09 27dc08aa.28555.17659.7.8.219_0 state:2
26.02.2006 05:47:09 p160000-GIANNI_pYEpYI1004-7-10-RND_0 state:3
26.02.2006 05:47:09 0 persistent file xfers
26.02.2006 05:47:09 3 active tasks
26.02.2006 05:47:09 27dc08aa.29856.2935.6.8.162_0
26.02.2006 05:47:09 28dc08aa.32338.8252.8.8.108_0
26.02.2006 05:47:09 03fe09af.12191.20522.6.8.43_0
26.02.2006 05:47:09 Poem@Home URL: http://boinc.fzk.de/poem/; Computer ID: 40371; location: (none); project prefs: default
26.02.2006 05:47:09 superlinkattechnion URL: http://cbl-boinc-server2.cs.technion.ac.il/superlinkattechnion/; Computer ID: 47839; location: (none); project prefs: default
26.02.2006 05:47:09 SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4850935; location: (none); project prefs: default
26.02.2006 05:47:09 GPUGRID URL: http://www.gpugrid.net/; Computer ID: 25204; location: (none); project prefs: default
26.02.2006 05:47:09 yoyo@home URL: http://www.rechenkraft.net/yoyo/; Computer ID: 25215; location: (none); project prefs: default
26.02.2006 05:47:09 Poem@Home General prefs: from Poem@Home (last modified 26-Feb-2006 05:47:09)
26.02.2006 05:47:09 Poem@Home Host location: none
26.02.2006 05:47:09 Poem@Home General prefs: using your defaults
26.02.2006 05:47:09 Reading preferences override file
26.02.2006 05:47:09 Preferences limit memory usage when active to 2046.42MB
26.02.2006 05:47:09 Preferences limit memory usage when idle to 2046.42MB
26.02.2006 05:47:09 Preferences limit disk usage to 1.75GB
26.02.2006 05:47:09 [guirpc_debug] Local control only allowed
26.02.2006 05:47:09 [guirpc_debug] Listening on port 31416
26.02.2006 05:47:09 [mem_usage_debug] enforce: available RAM 2046.42MB
26.02.2006 05:47:10 [guirpc_debug] got new GUI RPC connection
26.02.2006 05:47:10 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><nonce>1140929230.125000</no'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth2><nonce_hash>336d353b251c86faeb740b6811fbf292</nonce_hash></auth2></boinc_gui_rpc_request>'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><unauthorized/></boinc_gui_'
26.02.2006 05:47:10 [guirpc_debug] error -155 from handler, closing socket
26.02.2006 05:47:10 [guirpc_debug] got new GUI RPC connection
26.02.2006 05:47:10 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><nonce>1140929230.125000</no'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth2><nonce_hash>336d353b251c86faeb740b6811fbf292</nonce_hash></auth2></boinc_gui_rpc_request>'
26.02.2006 05:47:10 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><unauthorized/></boinc_gui_'
26.02.2006 05:47:10 [guirpc_debug] error -155 from handler, closing socket
26.02.2006 05:47:10 [guirpc_debug] got new GUI RPC connection
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><nonce>1140929233.328125</no'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><auth2><nonce_hash>04c140a35ad6515489c4a6e41590cd3f</nonce_hash></auth2></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><authorized/></boinc_gui_rp'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><exchange_versions> <major>6</major> <minor>6</minor> <release>20</release></exchange_versions></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><server_version> <major>6'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><acct_mgr_info/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><acct_mgr_info> <acct_mgr'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_state/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><client_state><host_info> '
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_host_info/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><host_info> <timezone>36'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_project_init_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><get_project_init_status> '
26.02.2006 05:47:13 [guirpc_debug] got new GUI RPC connection
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_host_info/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><host_info> <timezone>36'
26.02.2006 05:47:13 [guirpc_debug] error -102 from handler, closing socket
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><acct_mgr_info/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><acct_mgr_info> <acct_mgr'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_project_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><projects><project> <ma'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>0</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:13 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:14 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:14 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:14 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>260</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:14 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:15 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:15 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:15 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>264</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:15 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:16 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:16 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:16 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>268</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:16 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:17 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:17 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:17 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>272</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:17 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:18 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:18 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:18 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>276</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:18 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:19 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:19 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:19 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>280</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:19 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:20 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:20 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:20 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>284</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:20 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:21 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:21 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:21 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>288</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:21 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:22 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:22 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:22 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>292</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:22 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:23 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:23 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:23 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>296</seqno></get_messages></boinc_gui_rpc_request>'
26.02.2006 05:47:23 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><msgs><msg> <project></pro'
26.02.2006 05:47:24 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_cc_status/></boinc_gui_rpc_request>'
26.02.2006 05:47:24 [guirpc_debug] GUI RPC reply: '<boinc_gui_rpc_reply><cc_status> <network_stat'
26.02.2006 05:47:24 [guirpc_debug] GUI RPC Command = '<boinc_gui_rpc_request><get_messages> <seqno>300</seqno></get_messages></boinc_gui_rpc_request>'
already getting this log without any actice wus, can there already an error be seen? |
|
|
jrobbioSend message
Joined: 13 Mar 09
Posts: 59
Credit: 324,366
RAC: 0
Level
Scientific publications
|
|
I see a couple of error messages error -155 from handler, closing socket and error -102 from handler, closing socket, but I do not know what they mean.
I've also noticed that you are pretty low on free space on the hard drive and you allow Boinc to use as much space as you have free (1.75Gb), which may or may not be an issue.
I saw on another forum that Malware had caused problems within Boinc. Just to rule it out, try scanning with Malware Bytes.
Rob |
|
|
|
|
|
I just made 10gig hdd space free and let that malware thing run tru its already running for 2hrs and found 20 objects and that with 2 active antivir progs -.- |
|
|
|
|
|
@ jrobbio
It makes sense to me now.
I have 2 profiles on my XP Console. Mind it is a gaming console but found out that when Twyla (my wife) would log in her "side" I would have errored out WU with GPUGRID when Seti was fine and crunching.
I since disabled the BOINC client to autostart in the "msconfig" and run it only on my side now.
It just seems that GPUGRID is a bit more "fussy" than Seti@Home and you cannot do whatever you want while it is crunchig.
I had the most formidable load of errors from GPUGRID while I was gaming.
My GPU can't obviously crunch while gaming with a high end game (farcry2).
But it took me a whole week to understand that.....
So when I game I just suspend the work of GPUGRID then resume thereafter.
It crunches 0.016 WU every 3 second and takes about 5.02 hours to do a whole WU wich in return will grant between 3-6000 "average work done".
I have a Intel Q9550 cpu with a Gigabyte P35-DSP3 MB with a Gigabyte GTX285 Vid card, 4 GID OCZ Ram with a Thermaltake V1 cpu cooler encased in a Apevia X-Cruiser ATX Mid Tower.
Is there an "optimized apps" out there for GPUGRID?
Or any other way I can maximized my "returns"?
Martin Chartrand |
|
|
|
|
|
well as said earlier i made 10 GB moire disk space free and let this malware thing run tru, tryd a new wu and it directly errored out again!
And btw im not using anything on that machine since its a pc that is 24/7 crunching. |
|
|
|
|
|
I would try uninstalling the BOINC.
Make sure you delete the folder in the C:\Program Files\BOINC
Reboot and reinstall.
I have had many instance where this worked for me.
I also went back to version 6.4.7 since 6.6.2 seemed to give me a lot of grief for some reason.
Even a computer has it own preferences it seem.
I switched a couple years ago to a new modem and behold I had the most terrible time with it. Everything was crashing left and right and even the tech guys and IT were baffled by it. I went back to the old modem (which was better anyways) and never had problems since.
Matter of personnal opinion here but I also reformat both my computers once a year.
Martin Chartrand |
|
|
|
|
|
I already tried the reinstall earlier before. |
|
|
|
|
|
Why don't you try the older version?
Like I said I had all kind of problems with 6.6.2 for unknown reasons.
Since I went back to 6.4.7 everything is fine.
Also like I said in a previous post GPUGRID is a bit more suspect to crash than SETI (in my case).
So when I crunch GPUGRID I have no screen saver going nor do I make it go into snooze or whatever.
I just let the monitor open and just let it go.
I am not an expert by any means but found out that it helped me.
I had 20+ error prior to do this. And again I don't know why.
I don't believe that starting playing with the GPU settings and changing this or that withing the software and/or physically will solve anything but will make it worst.
If it worked fine before it should do it now as well.
I have the latest drivers which are CUDA 182.50 directly from NVidia.
This is just to try to help. Like I said I am not an expert.
Martin Chartrand
|
|
|
|
|
|
I just completly removed boinc again and reinstalled the version 6.4.5 which worked fine for me untill i went to 6.6.20 like 2 weeks ago. Since i reached the daily wu limit (which is 2 now -.-) I gotta wait till tomorrow morning for more testing since im goin to work in a few hrs.
ty for ur tryin to help me mate. ;) |
|
|
|
|
|
Yes.
I could not get any work unit since the server saw that I had so many errors.
I had to be patient and got 1 and completed it then I got 4 yesterday and completed 3 so far. The more you will crunch good WU the more GPUGRID will send you.
Always glad to be helping as much as I can.
Martin Chartrand |
|
|
|
|
|
Just tried a Wu on boinc client 6.4.5 -> errored out immedatly :<
Any1 any more ideas ? |
|
|
STE\/ESend message
Joined: 18 Sep 08
Posts: 368
Credit: 324,597,298
RAC: 642,912
Level
Scientific publications
|
Just tried a Wu on boinc client 6.4.5 -> errored out immedatly :<
Any1 any more ideas ?
Have you tried the 260 in one of your other Box's yet to see if it will run the WU's in a different Box ??? Just Suspend all the GPU WU's in the Box you want to try the 260 in, then put it in the Box and once it's started just un-suspend 1 WU to see if it will even run the WU's any more. If it will then fine, at least you know the Cards still good but if it won't then the Card is just bad probably & you only lost 1 WU trying it in a different Box.
I had a 8800GT OC Card that was running the WU's just fine & then it wouldn't any more for some reason no matter what Box I put it in but would run the SETI CUDA WU's like your card will. The SETI WU's just aren't as demanding as the GPUGrid WU's I guess and was why the 8800 would run them but not the GPUGrid WU's any more.
|
|
|
 Zydor Send message
Joined: 8 Feb 09
Posts: 252
Credit: 1,309,451
RAC: 0
Level
Scientific publications
|
Just tried a Wu on boinc client 6.4.5 -> errored out immedatly :<
Any1 any more ideas ?
The XP machines are on SP2, try updating to SP3 - its a good principle to get SP3 anyway.
BOINC releases 6.4.5, and 6.6.20 are the latest stable releases - the former was the first "CUDA" quick release, 6.6.20 has been developed with primarily CUDA in mind. Try running 6.6.20, all the versions between (and after) the two are development versions only, not for use in a Production environment, and can have varied results and problems in many situations.
It does not take much to make these things unstable, and a combination of XP SP release and BOINC release together with the new GPUGRID apps may have tipped the balance in your situation.
Another long shot - it happened to me recently, is memory. I had a motherboard burnout on me (old one - not project related) and a graphics card go on another machine at the same time (Murphys law.....). Upshot was a rebuild of both machines. On one I bought new matched Corsair memory for the new motherboard. That machine started to error out SETI and GPUGRID, I took it 'offline' to have a look. After a frustrating four days, I discovered that the new Corsair memory was defective, but was only erroring out under extreme load - it took 7 runs of memtest to "prove" it, but finally the supplier acknowledged the problem as a defective board on the pair and accepted RMA. Not had any hassles since. Maybe you have a memory fault on of the memory boards?? It can produce real wierd errors when that happens, with me other applications ran fine, so was hard to spot.
Regards
Zy
|
|
|
|
|
|
As soon as i find my motherboard drivers for that machine, ill try to run vista ultimate on it, which will be my last try to fix it, otherwise im gone to seti for good ;< |
|
|
|
|
|
A fresh install of any (supported) OS should have a pretty good chance of solving the problem. Unless it's somehow hardware related, in which case swapping the card into a working PC would be the way to go.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
/ 
Reply
Quote
