Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 712. (Read 3426922 times)

Hey if nvidia want to send you adverts I'm fine to have them ;-) support Christian through nvidia ads!

What's the reason for needing this Chrome trick? Card thinking it should enter 2d state?

so far I do not know how to achieve the same effect. Should I open a DirectX window and render a little spinning cube or what

Ah, now I know: I will have to integrate flash based advertising!

And get them to try and fix the need for chrome lmao

That works just fine but using DDU (display driver uninstaller, google it) is simpler and more convenient. :p

Christian, demand Nvidia to make a 4gb equipped GTX 750 Ti please, thank you

This may already be in the thread somewhere, but there is a procedure for completely removing your previous nvidia driver install without using any third-party uninstallers, that I have used for a while now, and I haven't had any problems since using it. From Overclock.net: http://www.overclock.net/t/1150443/how-to-remove-your-nvidia-gpu-drivers/0_50

The program you recommended trying did not work, as I am apparently missing the language file. What apparently did work was restarting the computer in safe mode, as it does work now, oddly enough.

Or try delete old driver with this utility in safe mode http://www.guru3d.com/files_details/display_driver_uninstaller_download.html

I would try reinstalling the driver once more with the "clean" install method (that's an optional checkbox to check during driver installation)

Christian

Hello, I just installed the new 335.23 driver on my windforce 3X GTX 770, and now Cudaminer is giving the following message:
'[2014-03-11 08:58:15] Unable to query CUDA driver version! Is an nVidia driver installed?'
I use the newest version of Cudaminer given, in combination with CUDA manager (version 1.2.1). If I try to run the miner outside of manager, it starts and then rapidly disappears. My set-up is as following:

Corsair Vengeance 16 GB : 2 x 8 GB
Toshiba DT01ACA100 1 TB
Kingston SSDNow V300 120 GB
Thermalright Macho Rev.A
Intel Core i7 4770K / 3.5 GHz
Asus B85-PLUS
Gigabyte GTX 770 OC Windforce 3X
Windows 7 (completely up to date)

Edit: When I use the rollback function to get back to my previous driver, the error keeps persisting.

Edit 2: Performing a clean install as we speak.

Edit 3: The clean install did not resolve the issue, I did it twice to be sure, but the problems still persists.

Stratum for blake256 was fixed. Happy hashing with the github version! Strangely my hashing speed
won't currently exceed 570 kHash/s on my GTX 780, and changing the setting from 80% TDP to 106% TDP doesn't
help either. HUH?

The Google Chrome trick seems essential here: Boosts hashes on my desktop PC from 770 kHash
to 1150 kHash/s (this is for four GPUs combined)

I will now merge in some GPU temp / fan monitoring code, but I will keep this extra output optional.

Note that you can go to T1000x32 with the blake256 method (other hashing algos limit you to x24 with the T kernels)

Christian

I will raise this issue with nVidia engineers. Thank you for bringing it to my attention.

I am also not running an X server on my mining rig equipped with three GTX 780 Ti. The mainboard has onboard graphics (Intel) and I prefer to use it as it induces no lag while mining. So the NV-CONTROL X extension can't work in this setting.

Christian

250 kHash/s with OC is what I've heard...

Christian

I use EVGA GeForce GTX 750 Ti which is small and have only one fan.

How do the non-Ti 750s perform compared to the Ti's? The reason I'm asking is that Amazon managed to send me regular 750s instead of the Ti's I had ordered and I'm considering my options. I'm not too keen on the idea of sending the cards back and waiting forever to get correct cards instead..

i do not see any noticable improvement for keccak with these drivers and 750Ti

oh my...
i use the EVGA FTW cards, and even with factory OC those cards do not go over 55°C while mining

I assume you are using -H 1 for this result?

I dug into this a bit tonight.  The 'nvidia-settings' app uses a different mechanism to talk to the NVIDIA driver than nvidia-smi does, and so the availability and range of information it provides is different in several cases.  NVIDIA has open-sourced the code for nvidia-settings, and as a result the API for communicating with the driver via an X server extension is also available as open source.  In comparing what I can query from that API vs. what I can query through the more CUDA-oriented NVML interfaces, the lineage of the two interfaces becomes obvious.  There are a few nice bits of information that currently don't appear to be available via NVML such as the utilization percentage for the hardware video encoder/decoder on the Kepler chips, additional temperature sensors, fan RPMs, and other PCIe and utilization information that NVML currently reports only for Tesla GPUs (or at least so it would seem).   The one thing I don't like about using the nvidia-settings methods for querying data from the X server is that there are plenty of cases where you'd rather not run an X server if you don't need it, and the NVML library and nvidia-smi work great in such a case while nvidia-settings and it's own NV-CONTROL X extension are not usable in that scenario.  It is possible that NVIDIA might be convinced to add some of the key missing data from nvidia-settings into nvidia-smi, but we'll have to see.  In the short-term I may see if I can make my code additionally talk to the X server when one is running.  We'll see how it goes.

His hashrate sucks for that high of an overclock. Getting stable 330kh with a +125 +600 overclock.