Posts by Lazydude2
log in
1) Message boards : Number crunching : Collatz V4.07 app_info (Message 17507)
Posted 1589 days ago by Lazydude2
check first post in
" Optimizing Collatz 4.07 Applications "
I am using both an 560ti and an 680. You should go "higher" in config due to that if am using higher , work on 560ti is craching.
Here are mine :
app_config.xml
<app_config>
<app>
<name>solo_collatz</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.5</cpu_usage>
</gpu_versions>
</app>

</app_config>
And here are mine solo_collatz_4.07_windows_x86_64__cuda50.config


verbose=1

items_per_kernel=22

kernels_per_reduction=9
threads=8
sleep=1
2) Message boards : Number crunching : Zero Credit Reports (Message 17360)
Posted 1623 days ago by Lazydude2
Some of mine:
http://boinc.thesonntags.com/collatz/result.php?resultid=144421181
http://boinc.thesonntags.com/collatz/result.php?resultid=144421180
http://boinc.thesonntags.com/collatz/result.php?resultid=144402016
http://boinc.thesonntags.com/collatz/result.php?resultid=144389037

3) Message boards : News : CUDA 4.2 Version for Windows Now Available (Message 14415)
Posted 2024 days ago by Lazydude2
Thanks for the update!

With the new package it runs "out of the box".

In my case S=0 less than 1% CPU

From Stock 3.11 to this one my times goes from 80min to 45min.

Big improvment!
Thanks again.
4) Message boards : News : CUDA 4.2 Version for Windows Now Available (Message 14404)
Posted 2024 days ago by Lazydude2

cudart64_40_17.dll is a CUDA 4.0 DLL. The build is for CUDA 4.2.

So.... updating the drivers to v4.2 build 9 (cuda64_42_9.dll) would have worked. On the other hand, this is pretty good news in that using CUDA 4.0 build 17 would also work but requires renaming the 4.2 DLLs so it thinks they are v4.2 DLLs -- which works with the app_info but not very well as a standard app. I guess I should have put the driver version in the readme (e.g. 301.42 or higher).



Yes, but if I understand things correct:
collatz_3.11_windows_x86_64__cuda42.exe calls for cudart64_40_17.dll
I´ll suspect this is "hardcoded" in the build.

If I open collatz_3.11_windows_x86_64__cuda42.exe in NOTEPAD and search for cudart64_4 i find cudart64_40_17.dll not cuda64_42_9.dll

This is On MS Vista64 and a NV 560Ti
//lazy
5) Message boards : News : CUDA 4.2 Version for Windows Now Available (Message 14385)
Posted 2026 days ago by Lazydude2
I found this in my Eventlog:
-------
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-07-07T05:09:05.000Z" />
<EventRecordID>38383</EventRecordID>
<Channel>Application</Channel>
<Computer>ABBY</Computer>
<Security />
</System>
- <EventData>
<Data>collatz_3.11_windows_x86_64__cuda42.exe</Data>
<Data>0.0.0.0</Data>
<Data>4ff322b3</Data>
<Data>cudart64_40_17.dll</Data>
<Data>6.0.6002.18541</Data>
<Data>4ec3e855</Data>
<Data>c0000135</Data>
<Data>00000000000b6fc8</Data>
<Data>d54</Data>
<Data>01cd5bfea14486ab</Data>
</EventData>
</Event>

--------------------------

Solution:
I Changed the Filename cudart64_42_9.dll to cudart64_40_17.dll
and uppdated the app_info.xml with the new filename.

It seems to work for me.






Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.