Posts by Helsionium

1) Message boards : Number crunching : Please help me with a new machine build (Message 1861216)
Posted 13 Apr 2017 by Profile Helsionium
Post:
Thank you all for your answers. Based on your answers, I chose the following options:

MB, CPU, GPU as posted intially
The € 35 CPU fan (designed for up to 140W TDP)
16 GB of DDR4-2400 RAM. If I need more, I can upgrade to 24 or 32 GB later.
2) Message boards : Number crunching : Please help me with a new machine build (Message 1860792)
Posted 10 Apr 2017 by Profile Helsionium
Post:
When it comes to crunching, 5% becomes 'substantial over time. A more modern mobo with 2x PCIe x16 slots wouldn't mean all that much $$$ in the greater scheme of your build, imho.

True, but in the end I don't expect my GTX 680 to last very long anyway, and I won't replace it when it finally fails. However, it has proven remarkably reliable - it has outlived 4 (!) GTX 560 Tis and now also my GTX 660.
3) Message boards : Number crunching : Please help me with a new machine build (Message 1860787)
Posted 10 Apr 2017 by Profile Helsionium
Post:
As far as I can see, the motherboard has only one 1x PCIE-slot that runs at x16 ?

Yes, and another one at x4. According to a graph in this article, there is no substantial downside to running a GTX 680 in a PCIe 3.0 x4 slot:
http://www.tomshardware.co.uk/forum/386054-33-would-pcie-slot-bottleneck
4) Message boards : Number crunching : Please help me with a new machine build (Message 1860780)
Posted 10 Apr 2017 by Profile Helsionium
Post:
He could do 2 sticks of 8GB and if he finds in the future your processing for work needs more he can add 2 more sticks of 8 GB later


After reading through all your replies, I think that's what I'll do. If I really need it, I can add more RAM at any time.
5) Message boards : Number crunching : Please help me with a new machine build (Message 1860766)
Posted 10 Apr 2017 by Profile Helsionium
Post:
OK, so I did a little research on dual channel RAM and it seems that one way to get a viable 24 GB solution would be:

2 of these: (2 x 8 GB)
https://playit.de/crucial-ballistix-sport-lt-udimm-8gb-ddr4-2400-cl16.html

and this dual channel kit (2 x 4 GB):
https://www.cyberport.at/form/?DEEP=2410-16U&APID=294&STOREID=7

If installed correctly (12 GB in one channel and 12 GB in the other), this should give full speed across all of the 24 GB, right?
6) Message boards : Number crunching : Please help me with a new machine build (Message 1860757)
Posted 10 Apr 2017 by Profile Helsionium
Post:
U´ll be need a 2xx chipset mainboard , because there is a need of flashing the newest bios to a 1xx chipset mainboard, caused by choosing Kaby Lake CPU.
I guess the company assembling the machine will do this for me in that case - they probably couldn't even test whether it works otherwise?

Unless he really does need the 32 GB for the video encoding he says he will use the computer for also. I have no knowledge of whether that is true since I don't do any video editing or encoding. Anyone with direct experience with video editing or encoding want to chime in and educate me?
32 GB is definetely overkill, but 16 GB might just be barely enough for some of my needs. That's why I thought of 24 GB instead, but I don't know whether using 3 RAM modules instead of 2 or 4 is a good idea.
7) Message boards : Number crunching : Please help me with a new machine build (Message 1860741)
Posted 10 Apr 2017 by Profile Helsionium
Post:
Hi guys!

After almost 4 years of continuous service, my GTX 660 died, and as a result I'm now going to replace my almost 6 years old main machine. Problem is, I haven't been following the hardware business for years - so I thought I might as well ask some experts.

I have already decided on the key features:

- MB: Gigabyte GA-Z170-HD3P
- CPU: i7-7700K CPU @ 4 x 4,20 GHz
- GPU: Manli GeForce GTX 1080, 8GB GDDR5
- RAM: 24 or 32 GB
- OS: Windows 10 Pro x64
- The machine will be used for crunching, programming and occasional HD or even 4K video editing.
- My old GTX 680, which is still working, should be used in the new machine as well.
- I don't intend to do try any overclocking this time around.

However, I slightly overran the budget I'm willing to spend, so I need your help with some adjustments:

First, RAM:
The shop allows me to decide between these three options:
4x Crucial DIMM 8GB, DDR4-2133, CL15 (€ 240)
4x Crucial Ballistix Sport LT UDIMM 8GB, DDR4-2400, CL16 (€ 276)
4x 8GB Kingston HyperX Fury, DDR4-2400, CL15-15-15 (€ 300)

Is the difference between DDR4-2133 and DDR4-2400 big enough to warrant a 15%/25% price increase, especially for my intended uses?

24 GB (3 x 8 GB) of RAM would be enough for me. Is there any downside to using an "odd" number of RAM modules (or a total RAM size that's not a power of 2)?

Second, CPU cooler:
The shop I want to buy from provides a "default cooler" at no additional cost, but unfortunately doesn't specify what the default cooler is. Apart from that, the shop gives me several options to choose from:
LC-Power Cosmo Cool LC-CC-95 (€ 20)
Scythe Katana 4 (€ 30)
Alpenföhn Ben Nevis (€ 35)
be quiet! Pure Rock (€ 40)
Water cooling solution Enermax Liqmax II 120 incl. assembly (€ 95)

Do I really need a cooler different from the "default cooler"?

Thank you in advance!
8) Message boards : Number crunching : "Your app_info.xml doesn't have a usable version...." and "Can't link app version file" errors (Message 1387505)
Posted 4 Jul 2013 by Profile Helsionium
Post:
Yes, now, after a second uninstall/reinstall, everything seems to work fine again. Thank you.
9) Message boards : Number crunching : "Your app_info.xml doesn't have a usable version...." and "Can't link app version file" errors (Message 1387400)
Posted 3 Jul 2013 by Profile Helsionium
Post:
Here's my app_info.xml file, generated by the Lunatics installer. I only changed the <count> values.
http://files.helsionium.eu/app_info.txt
10) Message boards : Number crunching : "Your app_info.xml doesn't have a usable version...." and "Can't link app version file" errors (Message 1387387)
Posted 3 Jul 2013 by Profile Helsionium
Post:
I don't really understand what's going on, I got this error once, but the subsequent requests succeeded. I didn't do a thing between these requests.

So for now it's working fine again, but I'm interested what could cause that behaviour? Shouldn't this error be persistent?

Here's the log of the last BOINC client session:

03.07.2013 21:45:13 | | No config file found - using defaults
03.07.2013 21:45:13 | | Starting BOINC client version 7.0.64 for windows_x86_64
03.07.2013 21:45:13 | | log flags: file_xfer, sched_ops, task
03.07.2013 21:45:13 | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
03.07.2013 21:45:13 | | Data directory: Z:\BOINC\Data
03.07.2013 21:45:13 | | Running under account Helsionium
03.07.2013 21:45:13 | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz [Family 6 Model 42 Stepping 7]
03.07.2013 21:45:13 | | 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 sse4_1 sse4_2 popcnt aes syscall nx lm vmx tm2 pbe
03.07.2013 21:45:13 | | OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
03.07.2013 21:45:13 | | Memory: 7.97 GB physical, 11.97 GB virtual
03.07.2013 21:45:13 | | Disk: 10.00 GB total, 6.94 GB free
03.07.2013 21:45:13 | | Local time is UTC +2 hours
03.07.2013 21:45:13 | | CUDA: NVIDIA GPU 0: GeForce GTX 680 (driver version 320.49, CUDA version 5.50, compute capability 3.0, 2048MB, 1775MB available, 3252 GFLOPS peak)
03.07.2013 21:45:13 | | CUDA: NVIDIA GPU 1: GeForce GTX 660 (driver version 320.49, CUDA version 5.50, compute capability 3.0, 2048MB, 1968MB available, 2107 GFLOPS peak)
03.07.2013 21:45:13 | | OpenCL: NVIDIA GPU 0: GeForce GTX 680 (driver version 320.49, device version OpenCL 1.1 CUDA, 2048MB, 1775MB available, 3252 GFLOPS peak)
03.07.2013 21:45:13 | | OpenCL: NVIDIA GPU 1: GeForce GTX 660 (driver version 320.49, device version OpenCL 1.1 CUDA, 2048MB, 1968MB available, 2107 GFLOPS peak)
03.07.2013 21:45:13 | SETI@home | Found app_info.xml; using anonymous platform
03.07.2013 21:45:13 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 6141926; resource share 100
03.07.2013 21:45:13 | | Preferences:
03.07.2013 21:45:13 | | max memory usage when active: 6119.88MB
03.07.2013 21:45:13 | | max memory usage when idle: 7343.86MB
03.07.2013 21:45:13 | | max disk usage: 6.65GB
03.07.2013 21:45:13 | | (to change preferences, visit a project web site or select Preferences in the Manager)
03.07.2013 21:45:13 | | Not using a proxy
03.07.2013 21:45:13 | SETI@home | Restarting task 11au09ab.30979.20522.15.12.230_0 using setiathome_v7 version 700 in slot 1
03.07.2013 21:45:13 | SETI@home | Restarting task 31mr08aa.27263.21340.15.12.224_2 using setiathome_v7 version 700 (cuda50) in slot 10
03.07.2013 21:45:13 | SETI@home | Restarting task 26fe08ab.3046.280581.9.12.195_1 using setiathome_v7 version 700 (cuda50) in slot 11
03.07.2013 21:48:57 | SETI@home | update requested by user
03.07.2013 21:48:58 | SETI@home | Sending scheduler request: Requested by user.
03.07.2013 21:48:58 | SETI@home | Requesting new tasks for CPU and NVIDIA
03.07.2013 21:49:01 | SETI@home | Scheduler request completed: got 0 new tasks
03.07.2013 21:49:01 | SETI@home | No tasks sent
03.07.2013 21:49:01 | SETI@home | No tasks are available for SETI@home Enhanced
03.07.2013 21:49:01 | SETI@home | No tasks are available for SETI@home v7
03.07.2013 21:49:01 | SETI@home | No tasks are available for AstroPulse v6
03.07.2013 21:49:01 | SETI@home | Nachricht vom Server: Ihre app_info.xml Datei enthält keine nutzbare Version von SETI@home v7.
03.07.2013 21:49:01 | SETI@home | This computer has finished a daily quota of 3 tasks
03.07.2013 21:54:28 | SETI@home | Computation for task 31mr08aa.27263.21340.15.12.224_2 finished
03.07.2013 21:54:28 | SETI@home | Restarting task 19fe09ai.32489.19527.12.12.226_0 using setiathome_v7 version 700 (cuda50) in slot 0
03.07.2013 21:54:31 | SETI@home | Started upload of 31mr08aa.27263.21340.15.12.224_2_0
03.07.2013 21:54:35 | SETI@home | Finished upload of 31mr08aa.27263.21340.15.12.224_2_0
03.07.2013 21:54:37 | SETI@home | Sending scheduler request: To fetch work.
03.07.2013 21:54:37 | SETI@home | Reporting 1 completed tasks
03.07.2013 21:54:37 | SETI@home | Requesting new tasks for NVIDIA
03.07.2013 21:54:40 | SETI@home | Scheduler request completed: got 2 new tasks
03.07.2013 21:54:42 | SETI@home | Started download of 26fe08ab.3046.284671.9.12.69
03.07.2013 21:54:42 | SETI@home | Started download of 06fe09ad.4649.142522.3.12.60
03.07.2013 21:54:46 | SETI@home | Finished download of 26fe08ab.3046.284671.9.12.69
03.07.2013 21:54:46 | SETI@home | Finished download of 06fe09ad.4649.142522.3.12.60
03.07.2013 21:55:51 | SETI@home | Computation for task 26fe08ab.3046.280581.9.12.195_1 finished
03.07.2013 21:55:51 | SETI@home | Restarting task 19fe09ai.32489.19527.12.12.221_0 using setiathome_v7 version 700 (cuda50) in slot 2
03.07.2013 21:55:53 | SETI@home | Started upload of 26fe08ab.3046.280581.9.12.195_1_0
03.07.2013 21:55:57 | SETI@home | Finished upload of 26fe08ab.3046.280581.9.12.195_1_0
03.07.2013 21:59:45 | SETI@home | Sending scheduler request: To fetch work.
03.07.2013 21:59:45 | SETI@home | Reporting 1 completed tasks
03.07.2013 21:59:45 | SETI@home | Requesting new tasks for NVIDIA
03.07.2013 21:59:48 | SETI@home | Scheduler request completed: got 1 new tasks
03.07.2013 21:59:50 | SETI@home | Started download of 19dc08ad.12584.1299.11.12.169
03.07.2013 21:59:54 | SETI@home | Finished download of 19dc08ad.12584.1299.11.12.169
03.07.2013 22:02:12 | SETI@home | Computation for task 19fe09ai.32489.19527.12.12.221_0 finished
03.07.2013 22:02:12 | SETI@home | Starting task 24au08ad.9227.19706.11.12.164_0 using setiathome_v7 version 700 (cuda50) in slot 2
03.07.2013 22:02:14 | SETI@home | Started upload of 19fe09ai.32489.19527.12.12.221_0_0
03.07.2013 22:02:18 | SETI@home | Finished upload of 19fe09ai.32489.19527.12.12.221_0_0
03.07.2013 22:03:08 | SETI@home | Computation for task 19fe09ai.32489.19527.12.12.226_0 finished
03.07.2013 22:03:08 | SETI@home | Starting task 26fe08ab.3046.280581.9.12.237_0 using setiathome_v7 version 700 (cuda50) in slot 0
03.07.2013 22:03:10 | SETI@home | Started upload of 19fe09ai.32489.19527.12.12.226_0_0
03.07.2013 22:03:13 | SETI@home | Finished upload of 19fe09ai.32489.19527.12.12.226_0_0
03.07.2013 22:04:53 | SETI@home | Sending scheduler request: To fetch work.
03.07.2013 22:04:53 | SETI@home | Reporting 2 completed tasks
03.07.2013 22:04:53 | SETI@home | Requesting new tasks for CPU and NVIDIA
03.07.2013 22:04:56 | SETI@home | Scheduler request completed: got 10 new tasks
...
11) Message boards : Number crunching : "Your app_info.xml doesn't have a usable version...." and "Can't link app version file" errors (Message 1387325)
Posted 3 Jul 2013 by Profile Helsionium
Post:
Hello,

a short time ago (few hours maybe) I started to experience errors I din't have before.
All of a sudden, I get "Your app_info.xml doesn't have a usable version of Seti@home v7" - I have installed the latest Lunatics optimized apps, already tried uninstall/reinstall and detach/reattach. The app_info.xml looks normal, it's the same as it was before (working fine ever since v7 was released).
At the same time I noticed all GPU WUs had errored out, with the error message "Can't link app version file".

Today, I installed a new GPU (GTX 660 in addition to the 680 I already had) and updated to the latest stable drivers, but I doubt it's related, as it worked fine for a few hours after that.

If you need more info, just state what you need.

Your help is very much appreciated.
12) Message boards : Number crunching : GTX660/Ti Owners, just a quick question. (Message 1347201)
Posted 16 Mar 2013 by Profile Helsionium
Post:
I'm using x41zc_cuda50 and the AP nVidia OpenCL application on my only machine (GTX 560 Ti + GTX 660) so my results aren't entirely comparable with your situation, but here's what I found out:

- Running 3 WUs is possible, but it's not worth it. The GPUs are maxed out with just 2 WUs anyway. With 3 WUs, there was somewhat higher power usage and temperature and occasional slowdowns. There was no noticeable positive effect on processsing throughput.

- With 2 WUs some moderately GPU-intensive programs still work without major problems (e.g. Google Earth, HD video), but with 3 WUs they wouldn't, even if there was still enough VRAM free.

- If any CPU-intensive task runs at the same or higher priority than the GPU tasks, this can cause massive slowdown. So I run the GPU tasks in high priority AND make sure no other CPU-intesive tasks run in high priority.

But keep in mind that this (except that last point) might be different when using x41g.
13) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1343195)
Posted 5 Mar 2013 by Profile Helsionium
Post:
Sorry for resurrecting this old thread, but I want to note that the problem has finally been solved.

My card, the "Zotac Geforce GTX 660 Ti AMP! Edition" is factory-OC'ed to 1150 MHz core and 1650 MHz memory clock - voltage already maxed.
The solution was to reduce the memory clock to 1500 MHz. It's running fine for days now (at core frequency 1200 MHz). Any higher value, particularly 1530 MHz and up, caused the driver to occasionally crash (with x41zc_cuda50; the previous x41g only caused the "zero status..." problem but no driver crashes) and whenever the driver crashed, the clock frequencies would be reset to factory and constant crashes (every 20 seconds or so) would happen from that point on.

I didn't notice this solution earlier because I never thought I had to decrease memory speed by that much. Anyway, it's fine now.
Thank you, jason_gee, for all your help.

Kind regards,
Helsionium
14) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313597)
Posted 10 Dec 2012 by Profile Helsionium
Post:
Unfortunately I corrupted my BIOS due tue a very badly designed BIOS update procedure. Since I probably will not find a way to recover, I must wait a few days for a replacement motherboard. I'm thankful for all your ideas and will continue with your suggestions as soon as possible.
15) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313537)
Posted 10 Dec 2012 by Profile Helsionium
Post:
OK, just to be sure, since I don't have any experience with the GTX 660 - the current core voltage is 1.175 V, core clock 1163 MHz, memory clock 1652 MHz, temperature 58-60°C. Is it safe to increase the voltage and what amount would you suggest?
16) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313465)
Posted 10 Dec 2012 by Profile Helsionium
Post:
So, some new observations:

- Enabling hyperthreading didn't fix or reduce the errors, I still left it on anyways.
- The error rate seems to be lower with x41g so I reverted back. Might be a coincidence, but at the very least, x41zb is certainly not better in that regard.
- Number of tasks per card doesn't matter. I ran only one task per card over the whole night as opposed to my standard two, but the error rate was not reduced.
- I swapped the cards, the error still only affects the 660.
- A temperature issue can now definitely be ruled out, after swapping the cards, the 660 runs at a temperature of 58-61°C.

Also, I didn't find the SLI option to disable it. I didn't connect the cards with an SLI bridge, so it shouldn't be available, right?
17) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313292)
Posted 9 Dec 2012 by Profile Helsionium
Post:
Thank you all for your opinions.

I used an old version of MSI Afterburner that couldn't make use of all the functions. With the new one I can indeed adjust the voltage (but can still not turn the fan speed of my 660 above 74% which is strange). But if, as you say, this is already a rather high temperature I'd rather not fiddle with the voltage control unless necessary. However, according to several internet sources, the temperature is pretty much the expected temperature of my card - the Zotac GTX 660 Amp! Edition - under maximum load, maybe a few degrees higher, but that's expected too (multi-GPU system, very demanding CUDA load instead of the game-based benchmarks)

I never enabled SLI to begin with, and also switched to "single display performance mode", but that too didn't help. I've set the process priority to high via the mbcuda.cfg file.

I'm out of time now, but tomorrow I will try switching the cards around and find out if hyperthreading affects the problem or not. The good thing is that the error is relatively benign and that all of the affected tasks I followed eventually successfully validated.
18) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313134)
Posted 9 Dec 2012 by Profile Helsionium
Post:
The problem persists even after I did this:

- reduce CPU speed from 4.3 GHz to 4.0 GHz
- reduce RAM frequency from 1600 to 1333
- disabled XMP
- installed x41zb
- tested GPU with OCCT, no errors, no artifacts

I can't change the GPU core voltage on the 660, the software doesn't allow that. I didn't find any options to adjust Vdd in the BIOS. The 660 isn't overclocked (past its factory-overclocking) and the software doesn't allow me to go lower than the default clock rates, so I can't do this. The error is probably not related to temperature, though. There was one instance of the error shortly after reboot, when temperatures were still much lower.

Just shortly before the installation of the new 660, I disabled hyperthreading because it was recommended by some in this forum. Could that be related?
19) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1313022)
Posted 9 Dec 2012 by Profile Helsionium
Post:
Alright, I checked:

- Hard drive integrity: OK (and no processes interfering with BOINC or SAH)
- DPC latency: OK, consistently below 500 microseconds, sometimes slightly above 500 if BOINC is active.
- Command rate: OK, set to T2.

About the temperature: is 70°C already too hot? Both GPUs and the CPU typically run at 68-74 degrees under full load. According to the information I had, this is well within their specifications.

About RAM Vdd: I can't really check this now, as I want to avoid restarting the machine unless absolutely necessary. Can this be a problem with RAM? Why would that affect only the tasks running on the 660 GPU and not the older, but almost equally fast 560 Ti?

The power supply should be OK as well. The system ran just fine with two overclocked 560 Tis which used more power.
20) Message boards : Number crunching : CUDA problems (Lunatics) / zero status but no finished file (Message 1312721)
Posted 8 Dec 2012 by Profile Helsionium
Post:
Hello there,

ever since I replaced one of my two 560Ti GPUs with a GTX 660, a relatively large amount of tasks (I guess 20-30%) restart at least once (exited with zero status but no 'finished' file) after encountering this error:

Error on call (cudaMemcpy(PowerSpectrumSumMax, dev_PowerSpectrumSumMax, (cudaAcc_NumDataPoints / fftlen) * sizeof(*dev_PowerSpectrumSumMax), cudaMemcpyDeviceToHost)), file c:/[Projects]/X_CudaMB/client/cuda/cudaAcc_summax.cu, line 239: unknown error

Here is a stderr output from one task that restarted five times:
http://files.helsionium.eu/stderr-2739587852.txt

It seems this problem only affects tasks that run on the new 660. What could be causing it? The same system ran fine with the two 560 Tis before. This problem isn't particularly grave - all of the affected workunits eventually complete and validate but I guess it's still having an impact on overall crunching performance, aside from being a major nuisance.

I'm using BOINC 7.0.28 on Windows 7 64-bit, the Lunatics x41g optimized app and the beta driver 310.70 (same problem with the latest WHQL driver, though).

Thank you in advance,
Helsionium


Next 20


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.