Welcome to MilkyWay@home

Posts by pirogue

1) Message boards : Number crunching : I need latest driver? (Message 47824)
Posted 14 Apr 2011 by pirogue
Post:
nevermind-can someone delete this reply?
2) Message boards : Number crunching : I need latest driver? (Message 47823)
Posted 14 Apr 2011 by pirogue
Post:
I was installing a new program, rebooted, and got new WUs--version 0.62.
Whatever changed in the last 10 minutes or so seems to have fixed the problem.
3) Message boards : Number crunching : I need latest driver? (Message 47821)
Posted 14 Apr 2011 by pirogue
Post:
11.3 is the latest I can find.

4/13/2011 11:42:45 PM ATI GPU 0: ATI Radeon HD5800 series (Cypress) (CAL version 1.4.1332, 1024MB, 2203 GFLOPS peak)
4/13/2011 11:43:18 PM Milkyway@home Message from server: ATI GPU: Upgrade to the latest driver to process tasks using your computer's GPU
4) Message boards : Number crunching : Old WU still awating validation (Message 41471)
Posted 15 Aug 2010 by pirogue
Post:
I've been away for a few months and was just checking on some recently returned WUs. At the bottom of the list, I saw this one:

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=91484344

It's been sitting there since April. Will this one ever get validated?
5) Message boards : News : issue with not getting work resolved (Message 39066)
Posted 23 Apr 2010 by pirogue
Post:
I've been having issues for a few hours now with MW@H. I'm running BOINC_64 6.10.43 and there's no WU's available for me. Earlier I was running a World Community Grid-branded Manager (on the BOINC Manager now) but I updated that since I had the 32-bit version and wanted to grab the 64-bit version that I have now. I've got a Radeon HD 3850 awaiting WU's (I only crunch MW@H on the GPU and WCG on the CPU--an E6300@4GHz)

I can't post on XS yet because I haven't been validated or whatever it's called. Based on this:
Well I managed to add 200MHz to my overclock (3.8 to 4.0 on the E6300). Upgraded BOINC to the 64-bit version (6.10.43), but now my GPU (Radeon HD 3850-256) isn't being identified.

22 Apr 2010 2:42:54 AM Starting BOINC client version 6.10.43 for windows_x86_64
22 Apr 2010 2:42:54 AM log flags: file_xfer, sched_ops, task
22 Apr 2010 2:42:54 AM Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
22 Apr 2010 2:42:54 AM Running as a daemon
22 Apr 2010 2:42:54 AM Data directory: C:\ProgramData\BOINC
22 Apr 2010 2:42:54 AM Running under account boinc_master
22 Apr 2010 2:42:54 AM Processor: 2 GenuineIntel Pentium(R) Dual-Core CPU E6300 @ 2.80GHz [Family 6 Model 23 Stepping 10]
22 Apr 2010 2:42:54 AM Processor: 2.00 MB cache
22 Apr 2010 2:42:54 AM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 syscall nx lm vmx tm2 pbe
22 Apr 2010 2:42:54 AM OS: Microsoft Windows 7: x64 Edition, (06.01.7600.00)
22 Apr 2010 2:42:54 AM Memory: 6.00 GB physical, 6.00 GB virtual
22 Apr 2010 2:42:54 AM Disk: 298.09 GB total, 119.90 GB free
22 Apr 2010 2:42:54 AM Local time is UTC -4 hours
22 Apr 2010 2:42:54 AM No usable GPUs found

Any way to get MilkyWay@home-GPU to work again? I tried updating from Catalyst 10.1 to 10.3 but that didn't work. I'm trying to switch back to 9.12 (iirc) now, partly because CCC really sucks. MW@h-GPU was working pretty well before, and I regularly got >18k BOINC ppd from it. 

I'd say that you didn't get the Protected application execution checkbox unchecked when you installed the newer version.
Right-click on the BOINC tray icon, choose Exit, check the "Stop running services..." checkbox, and then uninstall the BOINC client.
Reinstall the BOINC client, making sure you're installing it to the same location.
When you get to the Configuration dialog, click Advanced, and then uncheck the Protected Application execution box.
This should get your GPU working again.




©2024 Astroinformatics Group