PDA

View Full Version : Solo_Collatz error ATI HD5870



DrPop
04-29-13, 02:02 AM
Not sure what is causing this, but I have tried the new solo_Collatz on two separate days now, and both times the WUs immediately error out on my HD 5870. It will crunch the regular Collatz just fine. If there's any similarities between the two projects, it errored out Donate WUs immediately too, although I was told that could have been Donate's server problem. It runs every other GPU project just fine.

The new Solo_collatz seems to be working on the one nVidia card I have, so it must be something with that HD 5870 - driver? Settings? Not sure...
Any suggestions? :)
Thanks for your time.

Fire$torm
04-29-13, 03:33 AM
Not sure what is causing this, but I have tried the new solo_Collatz on two separate days now, and both times the WUs immediately error out on my HD 5870. It will crunch the regular Collatz just fine. If there's any similarities between the two projects, it errored out Donate WUs immediately too, although I was told that could have been Donate's server problem. It runs every other GPU project just fine.

The new Solo_collatz seems to be working on the one nVidia card I have, so it must be something with that HD 5870 - driver? Settings? Not sure...
Any suggestions? :)
Thanks for your time.

Ran that a few days ago. None of my ATIs had an issue. What driver version are you running?

Oh and I checked a couple of your wu status logs and saw this



Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000076F6E4B4 write attempt to address 0x00000024

(Link to Task 139531538 (http://boinc.thesonntags.com/collatz/result.php?resultid=139531538))

Sounds like a memory issue or maybe your firewall is restricting app execution? Assuming you are running a firewall... :P

DrPop
04-29-13, 12:24 PM
Hmmm...looks like it's running Catalyst version 13.1 - should that work? Not sure why it would give me a memory error when the regular Collatz works so well? Sits pegged at 97 to 98% GPU usage, and hardly any CPU use at all, and no stuttering issues with the screen or anything. But then I try the new Solo_Collatz and it immediately errors out.

On the firewall side of things - wouldn't it affect the other version of Collatz as well, or do you think they are pulling some different IP address or something? Seems strange...

Fire$torm
04-29-13, 01:37 PM
Please realize my suggestions are off the cuff so to speak. Just spouted out the first things that came to mind. Thats why I posted the link to the task log, so someone more knowledgeable might take it upon themselves to investigate.....

Anyhoot, it can't hurt to try resetting the project. Also try running only Collatz on that system, just to see.

artemis8
05-08-13, 11:42 AM
Yeah I tried solo wus for about week, they always failed so I just decided to stop accepting them.

kmanley57
05-08-13, 06:14 PM
I tried a couple different times to run the solo WU's and then just decided to uncheck the box for them and not try to run them again. :confused:

Tried everything I could think of except rolling the driver version back to an old one. Will just not run them I guess.

pinhodecarlos
05-08-13, 06:24 PM
Wu's won't work with Catalyst version 13.1, you need to go for 12.10. Please read first three topics: http://boinc.thesonntags.com/collatz/forum_forum.php?id=25

Fire$torm
05-08-13, 07:05 PM
Okay here is info on my 6970



01 5/8/2013 1:36:50 PM Starting BOINC client version 7.0.31 for windows_x86_64
02 5/8/2013 1:36:50 PM log flags: file_xfer, sched_ops, task
03 5/8/2013 1:36:50 PM Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
04 5/8/2013 1:36:50 PM Data directory: C:\ProgramData\BOINC
05 5/8/2013 1:36:50 PM Running under account *********
06 5/8/2013 1:36:50 PM Processor: 6 AuthenticAMD AMD Phenom(tm) II X6 1090T Processor [Family 16 Model 10 Stepping 0]
07 5/8/2013 1:36:50 PM Processor: 512.00 KB cache
08 5/8/2013 1:36:50 PM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
09 5/8/2013 1:36:50 PM OS: Microsoft Windows 7: Ultimate x64 Edition, (06.01.7600.00)
10 5/8/2013 1:36:50 PM Memory: 4.00 GB physical, 7.99 GB virtual
11 5/8/2013 1:36:50 PM Disk: 34.18 GB total, 30.08 GB free
12 5/8/2013 1:36:50 PM Local time is UTC -4 hours
13 5/8/2013 1:36:50 PM ATI GPU 0: AMD Radeon HD 6900 series (Cayman) (CAL version 1.4.1741, 2048MB, 2016MB available, 7680 GFLOPS peak)
14 5/8/2013 1:36:50 PM OpenCL: ATI GPU 0: AMD Radeon HD 6900 series (Cayman) (driver version CAL 1.4.1741 (VM), device version OpenCL 1.2 AMD-APP (938.1), 2048MB, 2016MB available)


Note: Catalyst Suite version is 12.6

Running a Solo wu just to make sure it still crunches and...

https://dl.dropboxusercontent.com/u/3595745/Solo_Collatz.jpg

Fogle
05-17-13, 08:07 AM
Just a note to pile on here. I am also getting the same error with my ATI card on solo_collatz 4.0X (opend_ati_100). So I also disabled those WU's, thanks for the tip!! ;)

Fire$torm
05-17-13, 12:11 PM
Just a note to pile on here. I am also getting the same error with my ATI card on solo_collatz 4.0X (opend_ati_100). So I also disabled those WU's, thanks for the tip!! ;)

Yesterday, Slicker released v4.07 Collatz apps for Windows that does work with Cat 13.4 and therefore can run upto x6 faster then previous versions. (Link (http://www.setiusa.us/showthread.php?5090-Collatz-v4-07-Released-for-Windows&p=60713&viewfull=1#post60713))

Slicker
05-17-13, 06:18 PM
The 4.07 app works for most but not all. For those still having problems, see the "optimizing 4.07 applications" thread on the collatz message boards and add the "build_options=-Werror -cl-opt-disable" line. AMD has finally admitted the driver is the problem and their engineers are working on it. Probably will be several driver releases away before it gets fixed though.

Duke of Buckingham
05-17-13, 07:55 PM
The 4.07 app works for most but not all. For those still having problems, see the "optimizing 4.07 applications" thread on the collatz message boards and add the "build_options=-Werror -cl-opt-disable" line. AMD has finally admitted the driver is the problem and their engineers are working on it. Probably will be several driver releases away before it gets fixed though.

8-} They could never release a driver to fix me. :((

NJCaNS
05-18-13, 03:28 AM
8-} They could never release a driver to fix me. :((I don't think we would want them to even if possible. We like you just the way you are. ;;)

Duke of Buckingham
05-18-13, 07:52 AM
I don't think we would want them to even if possible. We like you just the way you are. ;;)

http://people.emich.edu/ssohn2/mysite2/MCj02712000000%5B1%5D.gif

DrPop
05-18-13, 02:41 PM
... AMD has finally admitted the driver is the problem and their engineers are working on it. Probably will be several driver releases away before it gets fixed though.

Just glad you were able to get through to someone over there!
Well, after the Pentathlon is over, I'm going to add a second HD 5870 and do a clean sweep with the drivers, and install the latest ones. Hopefully that will fix the problem for me now with this new app. :)