I have serious problems with my new card, and after trying to make it work with GPUGrid for a whole day - quite frankly - I've run out of ideas.
Does anybody crunch with this type of card (GV-N780TOC-3GD) for GPUGrid?
I have a standard Gigabyte GTX 780 Ti in this host (beside an ASUS GTX 670 DC2 OC). These cards are doing very well their job. Originally I wanted a Gigabyte GTX 780 Ti OC, so after waiting for this card a couple of weeks it became available, and I've ordered and received one. I've put this card beside its little brother (the non OC Gigabyte GTX 780 Ti), and my problems immediately emerged: the new card failed every task almost immediately.
There is only one task which was run for 2000s, because the card was downclocked to 450MHz, bur after a restart the downclock was gone, and it has failed too.
Since then I've tried the following, none of them helped:
1. uninstall NV driver, restart, install latest NV (331.93 beta) driver
2. install a fresh Win7 x64 on this host, with the latest beta driver
3. Put the failing card in different PCIe slots of the GA-Z87X-OC motherboard, remove the original card, and put the failing card in it's place to be the only card in the system
4. test the card with different applications: Heaven's benchmark, Furmark, Primegrid, GPU memory stress test, G80 memtest - all of them were OK
5. put the card to a different MB (Intel DH87RL), under different OS (Win8.1 x64)
6. Further tests: NVidia human face demo (it's quite stunning actually), 3DMark13, NVidia design garage, NVidia Islands - all of them OK.
7. downclock the card with MSI Afterburner
8. increase the GPU voltage to the maximum of 1212mV with Kepler BIOS tweaker 1.26
9. uninstall the 331.93 driver, restart, download and install the card's original driver (331.60) from Gigabyte
10. decrease the GPU clocks, power limits, boost clocks, etc. to the settings of the working (non-OC) card with Kepler BIOS tweaker 1.26
11. decrease the GPU clocks further down to 800MHz
12. decrease the GPU memory clock to 3.4 GHz
13. decrease the GPU memory clock to 3.3 GHz
14. decrease the GPU memory clock to 3.3 GHZ and the GPU clocks etc. to the settings of the working card.

The really annoying aspect of this is that only the GPUGrid tasks are failing on this card - the tests, benchmarks, and demos are not. I had a faulty GTX 580 some time ago, but that card also showed some heavy artifacts with Heaven's benchmark. I would appreciate if you could recommend any further testing tool which can detect any defect on this card (while it shows no problem on the other GTX 780 Ti), because I'm not convinced that this card is faulty.
Tomorrow I'll try to test this card with folding@home (I couldn't reach Stanford's webpage today).

ok already done on Point 4 sry ^^
____________
DSKAG Austria Research Team: http://www.research.dskag.at

I also doubt the card is defective but if it can't run GPUgrid tasks with the numerous tweaks you've tried then something is wrong somewhere.

I've Googled terms like "GV-N78TOC-3GD problem", "problem GV-N78TOC-3GD", "fubar GV-N78TOC-3GD", "GV-N78TOC-3GD fail", etc. and haven't found any reports or reviews speaking of problems.

Do any of the diagnostic programs you've run test with CUDA or in CUDA mode? I ask because if you can demonstrate that it consistently fails on CUDA but not OpenGL or alternatively fails OpenGL and CUDA but nothing else then you have something definite that you can present to Gigabyte and/or NVIDIA if you want to motivate them to investigate and perhaps issue a driver update or BIOS update.

The point is you've more or less eliminated clock and voltage settings, mobo and drivers as the problem. The only other possible things I can think of to experiment with are:

1) Win XP or Linux versus Win 7/8
2) CUDA vs. OpenGL vs. "game mode" or whatever the correct term is
3) localized over-heating which I explain below

We know there are different ways of measuring/detecting GPU core temperature as was discussed recently in another thread here. Maybe certain portions of the GPU core are not cooling properly due to one or more of the following causes:

1) a curved heat spreader on the GPU
2) a curved surface on the heat sink
3) improper application of thermal grease

Maybe high temps in affected areas are not showing up in temp reports and only GPUgrid tasks are exercising those poorly cooled areas. (Yes, that does require a number of factors to align properly but nothing happens by accident, there is always a cause, you have eliminated most of the causes already and this one is one of the few remaining reasons.)

If you have good vision you can spot badly curved/warped surfaces easily with what I call "the straight edge and light test" which is a very common test. You probably are familiar with how it works but don't rely on it unless you know your vision is good. A much better way of measuring flatness is to use a dial gauge on a pivot as it will easily show defects as small as .005 inches if used properly. A top quality dial gauge and pivot are expensive but there are less expensive models that are accurate enough for the job we're talking about. Or you can take the GPU and heatsink to a machine shop and pay them to check the flatness.

If it turns out one or both of the 2 surfaces are curved then you can correct it by lapping if the mismatch is small or by machining and lapping/polishing if the mismatch is large.

Some people think they can detect curved surface(s) by seeing if they can rock the heatsink side-to-side. That test can reveal a convex-to-flat or convex-to-convex situation but cannot reveal a concave-to-flat or concave-to-concave situation.


____________
BOINC <<--- credit whores, pedants, alien hunters

I am sorry to hear you have problems with you new card Zoltan. I can't help you, as you don't know the answer yourself then I certainly don't know. The only thing I can think of is that these cards are to powerful but that can't be true?
Good luck, I am sure over time you will find the answer.

But I have two questions.
1. The host you are showing has awesome time compared to mine and you have now Win7 installed as well? What have you done then to get these results.
2. I downloaded and installed Kepler BIOS Tweaker as you suggested in the thread I started, but all I see are empty fields and clicking in it does not work, I can not put any values in. What did I do wrong there?
____________
Greetings from TJ

I also doubt the card is defective but if it can't run GPUgrid tasks with the numerous tweaks you've tried then something is wrong somewhere.

I've Googled terms like "GV-N78TOC-3GD problem", "problem GV-N78TOC-3GD", "fubar GV-N78TOC-3GD", "GV-N78TOC-3GD fail", etc. and haven't found any reports or reviews speaking of problems.

Do any of the diagnostic programs you've run test with CUDA or in CUDA mode? I ask because if you can demonstrate that it consistently fails on CUDA but not OpenGL or alternatively fails OpenGL and CUDA but nothing else then you have something definite that you can present to Gigabyte and/or NVIDIA if you want to motivate them to investigate and perhaps issue a driver update or BIOS update.

The point is you've more or less eliminated clock and voltage settings, mobo and drivers as the problem. The only other possible things I can think of to experiment with are:

1) Win XP or Linux versus Win 7/8

2) CUDA vs. OpenGL vs. "game mode" or whatever the correct term is

3) localized over-heating which I explain below

We know there are different ways of measuring/detecting GPU core temperature as was discussed recently in another thread here. Maybe certain portions of the GPU core are not cooling properly due to one or more of the following causes:

1) a curved heat spreader on the GPU
2) a curved surface on the heat sink
3) improper application of thermal grease

Maybe high temps in affected areas are not showing up in temp reports and only GPUgrid tasks are exercising those poorly cooled areas. (Yes, that does require a number of factors to align properly but nothing happens by accident, there is always a cause, you have eliminated most of the causes already and this one is one of the few remaining reasons.)

If you have good vision you can spot badly curved/warped surfaces easily with what I call "the straight edge and light test" which is a very common test. You probably are familiar with how it works but don't rely on it unless you know your vision is good. A much better way of measuring flatness is to use a dial gauge on a pivot as it will easily show defects as small as .005 inches if used properly. A top quality dial gauge and pivot are expensive but there are less expensive models that are accurate enough for the job we're talking about. Or you can take the GPU and heatsink to a machine shop and pay them to check the flatness.

If it turns out one or both of the 2 surfaces are curved then you can correct it by lapping if the mismatch is small or by machining and lapping/polishing if the mismatch is large.

Some people think they can detect curved surface(s) by seeing if they can rock the heatsink side-to-side. That test can reveal a convex-to-flat or convex-to-convex situation but cannot reveal a concave-to-flat or concave-to-concave situation.

I have two questions.
1. The host you are showing has awesome time compared to mine and you have now Win7 installed as well? What have you done then to get these results.

2. I downloaded and installed Kepler BIOS Tweaker as you suggested in the thread I started, but all I see are empty fields and clicking in it does not work, I can not put any values in. What did I do wrong there?

I've flashed the working card's BIOS to the OC card (they have different vendor and PCI subsystem IDs, so I was a little concerned about doing it). The card was working ok, but the GPUGrid client still fails. I'm afraid that I have to sell this beautiful card to a gamer...

From my experience it's much more common error that one or two corners of the heatsink is not fastened well, so it's touching the chip only on one (or two) edge(s), not on its entire surface.

Having just completed a new Haswell build, I have learned that a motherboard that is quite stable with its own internal graphics can go bananas once I insert a GTX 660 and try to run BOINC/GPUGrid. As soon as BOINC starts (barely having time to reach the desktop, if that), I get BSODs. That itself is not so unusual, but like you I had already underclocked/overvolted the card sufficiently that it should have worked fine.

The solution for me lay in the motherboard DDR3 memory; I had manually set the speed to 1600 MHz and 8-8-8-24, which is the rated speed of the Crucial Ballistix 2 GB modules (4 of them). But by returning to the default motherboard value of 1333 MHz and 9-9-9-24 timings (as set by SPD), the problems seem to have disappeared. Maybe you have something similar.

1) a curved heat spreader on the GPU
2) a curved surface on the heat sink
3) improper application of thermal grease

Zoltan, you have already tried a lot, and as you have tried the GPU on different rigs and with different operating systems, my guess is that the card is a dud, most likely GDDR/some capacitor. Alternatively the GPUGrid app/s simply don't work with it due to some obscure oddity in the app/bespoke card (slim chance).
Suggest you check the GPU physically (loose anything, burnt smell, dodgy soldering...), sunk PCIE power connector pins (on the card), does the GPU seat fully?

Some loose/desperate suggestions (possibly already covered):
Try short tasks, if you haven't already.

What was installed with the NVidia drivers; all the 3D and sound crap or just the drivers?

Have you tried lowering the power target (MSI Afterburner...)?

What about System Power settings?

NVidia control panel settings? Prefer max performance,

PhysX pointing where - specific GPU or CPU (not sure that even matters though)?

Have you tried to drop the GPU memory to 3000MHz?

Motherboard Bios upgrade (long shot).

CPU drivers from Intel (might be messing with the bus)?

Chipset update?

Different versions of Boinc (perhaps even completely uninstalling Boinc and then reinstalling.

Tried Linux?

Have you tried to drop the GPU memory to 3000MHz?

I see you have had 2 more successful runs and one failure,

Despite the memory drop that's still around 28% faster than my GTX770.

For each task, the logs show the GPU temps going up to 64C and then the card sometimes stops working for a while. This suggests to me that there is something not right with the cooling. While the GPU is fine, I suspect the GDDR5 is not (or something related to the GDDR). Perhaps a bad module that might not get used by other types of work.

I see you have had 2 more successful runs and one failure,

Yep, the error is still there, despite that now the RAM runs at 2800MHz. Sometimes lowering the frequency makes things worse, and I think that lowering even more the RAM frequency won't solve completely the problem of my card.

I just got my new 780ti OC windforce 3x and have the same problems. My other card is fine but this card fails almost instantly with computation error. I tried on both Ubuntu (319.76 and 331.20 drivers) and Windows with no joy so far.. I haven't tried lowering the clocks yet I am still troubleshooting it :(

Did you ever make any progress on this?

Yes, this card is working fine since I've lowered its memory clock to 2700MHz.
For example:Task 7614006, Task 7612456, Task 7611911
You've answered my unasked question: is this problem by design, or just my card is faulty?
It seems to be some problem with the design of the card.

Yes, this card is working fine since I've lowered its memory clock to 2700MHz.
For example:Task 7614006, Task 7612456, Task 7611911
You've answered my unasked question: is this problem by design, or just my card is faulty?
It seems to be some problem with the design of the card.

You've answered my unasked question: is this problem by design, or just my card is faulty?
It seems to be some problem with the design of the card.

From your perspective it is the design of the card and I agree with your perspective. If you ask the manufacturer and present all the evidence you have uncovered, their response might be like "It's a problem with the application, that card is for gaming applications where a few errors won't be noticed. It's not for data crunching that requires high precision and reliability."

Do you plan to RMA it?

IIUC, you have had to downclock the memory below the frequency used on the standard model (not OC), yes?

hello Retvari Zoltan* thanks for the problem solution. Can run mine at 3100MHz

hello Retvari Zoltan* thanks for the problem solution.

Can run mine at 3100MHz

I finally got around to flashing my card down to 2700 memory and now it works fine under linux. its a little slower than yours (about 1500 seconds) but I am also running worldcommunitygrid on every other thread and the ambient is about 25c here recently.

I am on linux with it.

so thanks for the solution :)

When you had you GPU stripped did you notice what type of GDDR5 your Gigabyte Windforce 3X card was using?
If it uses Hynix GDDR5 is should be R2C, but there are other types it might be; R0C, T2C, or T0C.

Have you checked Gigabyte's website for an errata sheet and/or correction sheet dealing with this issue? I suspect many hundreds of their customers are having the same issue for exactly the same reason (wrong component or failed component such as a cap or resistor) and I would think by now Gigabyte is aware of the problem. If not then the more people who report it and the workaround (downclocking the memory) the sooner they will become aware they have a big problem and a potential big blow to their reputation and move on the issue.

____________
BOINC <<--- credit whores, pedants, alien hunters

How is possible to have crunching time like you Zoltan (about 16.000 sec.) on the last WU? I have 4 GPU like you, GTX780ti, and my crunching time is 24.000 sec. Why?
____________
Member of Boinc Italy.

How is possible to have crunching time like you Zoltan (about 16.000 sec.) on the last WU? I have 4 GPU like you, GTX780ti, and my crunching time is 24.000 sec. Why?

48 CPU threads vs 8threads - less resource conflict, HT doesn't scale really well for some CPU/GPU project combinations.

48 CPU threads vs 8threads - less resource conflict, HT doesn't scale really well for some CPU/GPU project combinations.

I gasped when I saw 48 too but it turns out his CPU has 12 real cores (24 virtual) and I suspect he might have 2 CPUs. Also, that's a socket 2011 CPU with 40 PCIe lanes so I doubt there is congestion on the PCIe bus unless his mobo is lane restricted.

BTW, I saw ads for that CPU... $2,500 US!!!

Gattorantolo... get with the penguin :-)

Your GTX780Ti temperatures look very cool - too cool. If you are not using water cooling, your GPU's may be downclocking.

As an aside, Linux scales VERY well, which is why it's used in data centers, including Microsoft's.

So I was able to complete this one task-gluilex2x33-NOELIA_DIPEPT1-0-2-RND9057_2
GPU [GeForce GTX 780 Ti] Platform [Windows] Rev [3203M] VERSION [55]
# SWAN Device 0 :
# Name : GeForce GTX 780 Ti
# ECC : Disabled
# Global mem : 3072MB
# Capability : 3.5
# PCI ID : 0000:01:00.0
# Device clock : 1084MHz
# Memory clock : 3500MHz
# Memory width : 384bit
# Driver version : r331_82 : 33221
# GPU 0 : 52C
# GPU 0 : 53C
# GPU 0 : 54C
# GPU 0 : 55C
# GPU 0 : 56C
# GPU 0 : 57C
# GPU 0 : 58C
# GPU 0 : 59C
# GPU 0 : 60C
# GPU 0 : 61C
# GPU 0 : 62C
# Time per step (avg over 12500000 steps): 1.657 ms
# Approximate elapsed time for entire WU: 20717.930 s
18:44:22 (7780): called boinc_finish

unfortunately unfinished right behind this successful
970x-SANTI_MAR420cap310-0-32-RND2207_1
<core_client_version>7.2.33</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -97 (0xffffff9f)
</message>
<stderr_txt>
# GPU [GeForce GTX 780 Ti] Platform [Windows] Rev [3203M] VERSION [55]
# SWAN Device 0 :
# Name : GeForce GTX 780 Ti
# ECC : Disabled
# Global mem : 3072MB
# Capability : 3.5
# PCI ID : 0000:01:00.0
# Device clock : 1084MHz
# Memory clock : 3500MHz
# Memory width : 384bit
# Driver version : r331_82 : 33221
# GPU 0 : 52C
# The simulation has become unstable. Terminating to avoid lock-up (1)

220x-SANTI_MAR423cap310-0-84-RND2313_1
(unknown error) - exit code -97 (0xffffff9f)

201x-SANTI_MARwtcap310-6-32-RND4585_0
(unknown error) - exit code -97 (0xffffff9f)

883x-SANTI_MARwtcap310-2-32-RND9284_0
same sh**

I can not download and try other tasks .. GPUGRID it blocked my client
Why this one task goes no problems ...??

Just for information, I went to the Gigabyte site and they are now selling a card called GV-N78TOC-3GD (Rev. 1.0). Is it the same as the one you described having problems? Other question, does this problem occur also with the similar GV-N78TGHZ-3GD?

GV-N78TOC-3GD (Rev. 1.0) is the same card as I got in Thailand which has the problems. It works ok now with the memory downclocked but runs at the same speed as my 780 oc'd which is disappointing (which is also the same speed as my titan which is sitting unused :/)

GV-N78TOC-3GD (Rev. 1.0) is the same card as I got in Thailand which has the problems. It works ok now with the memory downclocked but runs at the same speed as my 780 oc'd which is disappointing (which is also the same speed as my titan which is sitting unused :/)

Just for information, I went to the Gigabyte site and they are now selling a card called GV-N78TOC-3GD (Rev. 1.0). Is it the same as the one you described having problems?

Other question, does this problem occur also with the similar GV-N78TGHZ-3GD?

Gigabyte has released a new frimware (ver F3) for this card in april.
Its description begins with this: "Release for HYNIX Memory", so I thought that it could fix my memory clock issue.
I haven't had the time and motivation back then to upgrade - and forgot about this -, but today I did upgrade the card's BIOS to F3.
The good news is that the card is crunching fine for about 15 minutes now (at RAM clock 3500MHz, GPU clock 1137MHz).
I'll report the card's crunching status when I'll have something important to report :)

No luck at 3500MHz - The task I've referred in my previous post has failed after 5168 sec.
Two consecutive NOELIA tasks failed almost instantly at start.
Tried 3400MHz - it was worse than @ 3500MHz.
Now at 3300MHz a NOELIA_BI is running for 15 minutes without "simulation became unstable" message.

Thanks for the update! Oh well :/

Forgive me, as I'm late to this thread, but... have you tried setting the GPU fans manually, via Precision-X or MSI Afterburner, to the maximum fan % allowed for that GPU, just to see if keeping the GPU cooler will have an effect? Set it to maximum for 2 days, to test, maybe?

I sympathize with you Retvari, having problems with a new, shiny piece of kit is a frustrating experience... I'm in a similar situation with you, having a 750Ti acting in a psychotic manner.

I am refusing to RMA it just yet and am trying to make it work (with mixed results), but it won't be long now, if it keeps getting many errors I will go ahead and return it.

I feel you should do the same, especially with an expensive card like yours. Seriously, if something (anything) is wrong in the hardware, how feasible is it to repair it yourself? Maybe it would be realistic 15-20 years ago, when many things were soldered by hand, but today's PCBs are multi-layered and full of tiny components soldered by robot hands to amazing precision. It's far more possible that you will break something if you try to fix it and void your warranty along the way, injury and insult at the same time! I say, just RMA it and keep your peace of mind!

On the other hand, you may be very experienced with such labor, in which case I wish the best of luck to you!
____________

Forgive me, as I'm late to this thread, but... have you tried setting the GPU fans manually, via Precision-X or MSI Afterburner, to the maximum fan % allowed for that GPU, just to see if keeping the GPU cooler will have an effect? Set it to maximum for 2 days, to test, maybe?

There was a successful I770-SANTI_p53final at 3300MHz, but a e2s948_e1s373f83-SANTI_marsalWTbound2, and a 2x118-NOELIA_TRPS1S4 has failed.
I've set the GPU RAM to 3200MHz, but this I1072-SANTI_p53final had some "Simulation unstable" messages, so now the card is down at 3100MHz, and processing this 15x30-NOELIA_BI_3.

My Gigabyte GTX 780Ti OC is crunching fine (i.e. without "Simulation unstable" messages) at 3100MHz RAM clock for more than 1 day now.
The source of the original problem could be a memory voltage / timing (latency) problem, which was addressed by the new BIOS release (F3), but wasn't solved completely. With the new BIOS I could achieve 400MHz higher clock speed, while it's still 400MHz lower than the nominal.
Is there any tool to tweak a Kepler GPU's memory settings beside the clock? (Voltage, latency etc.)

I wrote to Gigabyte support, they replied that I should try my card the way I did back in December.
(Which I'm sure will end with the same results - so I didn't redo my tests yet.)
I'll dismount the cooler once again and check the type of every RAM chip individually, I'll also try to measure the operating voltage on the buffering capacitors.

H5GQ2H24AFA R2C or,
H5GQ2H24AFR R2C ?

Assuming H5GQ2H24AFR R2C, these require 1.6V to support 3.5GHz.

Excluding the possibility of bad GDDR5 and bad circuitry (which we can do nothing about anyway), my guess is that the card isn't supplying the necessary 1.6V, and is either supplying 1.5V or 1.35V - possibly 1.5V for some people and 1.35V for others; with 1.35V perhaps being sufficient for 2.7GHz and 1.5V sufficient for 3.1GHz. This ties in with what has been reported here and suggests a firmware, driver or OS issue.
This might be related to the performance levels of the GPU (0, 1, 2, 3, 4) which might behave differently for GK110 than GK104.

There's a new BIOS version (F4) for this card on Gigabyte's website.
I've flashed it to my card, but a task immediately failed on default clocks (3.5GHz GDDR5).
I have to reiterate the right GDDR5 frequency with this new BIOS.
Now it's down by 100MHz (at 3.4GHz).

The task running on this card got a couple of "Simulation became unstable" messages in the stderr.txt file, so I took down the GDDR5 clock by another 100MHz (now it runs at 3.3GHz).

There were "Simulation became unstable" messages, and a failed WU at 3.3GHz.
Now I'm testing the card at 3.2GHz.

Have you considered running Heaven, to determine how far you may need to downclock? If you can get Heaven to run at max settings overnight with no issues, then I'd consider it stable.

Have you considered running Heaven, to determine how far you may need to downclock? If you can get Heaven to run at max settings overnight with no issues, then I'd consider it stable.

I apologize - although I did read most of the thread, I did miss the part where you said you tested with Heaven.

Nevertheless... did you just run a single benchmark with it? That's often not enough. Usually, it takes several hours to confirm stability.

I'd be curious to see if you can get through an *overnight* test, running at [DirectX 11, Ultra, Extreme, x8 AA, Full Screen, 1920x1080]... with:
- no application crashes
- no TDRs (as evidenced by dmp files in C:\Windows\LiveKernelReports\WATCHDOG
- no strange display glitching (which would indicate memory corruption possibly due to memory being clocked too high)

Sorry if you've done this, or you feel this is an inappropriate test. But I do recommend that you try it, if you haven't already. Just trying to help.

How can one read these dmp files Jacob?
____________
Greetings from TJ

I don't know. I think, if you have the Windows SDK and development tools installed, and have Windows symbols available, you might be able to step through them. But that's all beyond my ability.

The short story is: If you have a .dmp file in your C:\Windows\LiveKernelReports\WATCHDOG directory, it means your GPU had a TDR... and either an application was faulty, or the GPU was faulty, or (the most common case) you are pushing your GPU too hard in terms of Core Clock or Memory Clock.

I still fully recommend Heaven 4.0, on the maximum settings I described a couple posts up, running overnight, to confirm stability. Once I did that for my 2 GTX 660 Ti's, and found that I had to decrease the clock on one and could increase the clock on the other, and since then I have had 0 problems with GPUGrid and with iRacing.

Not trying to spam this thread. Retvari, I hope you can get your issue figured out, and if my suggestion doesn't help you, then I apologize.

How can one read these dmp files Jacob?

Have you considered running Heaven, to determine how far you may need to downclock? If you can get Heaven to run at max settings overnight with no issues, then I'd consider it stable.

When I first tested the card, I did. The only application failed is GPUGrid's.
See the first post of this thread.
BTW the card seems to be stable at 3.2GHz, but different workunit batches could use different parts of the GPU.
I suspect that something messed up with the GDDR5 voltage, or the PSU of the memory subsystem on this card series.

Thanks for your help eXaPower, but I have tried notepad, wordpad but no normal reading is possible.
I did not game but have a few dmp files, perhaps when a drives crashed with GPUGRID? And now I am interested in what is in those files.
____________
Greetings from TJ

Thanks for your help eXaPower, but I have tried notepad, wordpad but no normal reading is possible.
I did not game but have a few dmp files, perhaps when a drives crashed with GPUGRID? And now I am interested in what is in those files.

I see this card runs ~80C.

Do you know Voltage control temps on card?

Do you know temps for DDR memory? These temps run really hot on certain GTX780ti's

I see this card runs ~80C.

No. This card (GPU1) runs at 65-70°C.
The other card (GPU0) - which is a standard NVidia design - runs fine on 3.5GHz at 80°C.

Do you know Voltage control temps on card?

I don't know voltage control temps, but I think it should be lower than the other card's, as this card has more phase on that VR, and this card has better cooling.

Do you know temps for DDR memory? These temps run really hot on certain GTX780ti's

I don't know that either, but the same reasoning applies to the RAM chips as for the VRM chips.

How can one read these dmp files Jacob?

I had another failed workunit on this card, so I took another 100MHz off, it's now running at 3.1GHz GDDR5 clock.

Thanks JugNut I will try it over the weekend.
____________
Greetings from TJ

Hello,

Wanted to try GPUGRID today, but UNFORTUNATELY, still ONLY ERRORS within 15 seconds :/

Tried 1 GPU only (0 and then 1) but same result.

Temp 65°

What's happening ?

What can we do ?

EDIT : Have decreased the Power target down to 60 % + short WU's, but same problem. All tasks = errors.

388-NOELIA_20MGK36I-2-5-RND2053_0 10116890 160926 27 Sep 2014 | 9:40:02 UTC 27 Sep 2014 | 9:50:20 UTC Erreur en cours de calculs 8.27 2.54 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
14-NOELIA_20MGK36I-2-5-RND3099_0 10116873 160926 27 Sep 2014 | 9:33:35 UTC 27 Sep 2014 | 9:41:41 UTC Erreur en cours de calculs 67.69 12.40 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
522-NOELIA_20MGWT-2-5-RND4515_0 10116837 160926 27 Sep 2014 | 9:33:35 UTC 27 Sep 2014 | 9:50:20 UTC Erreur en cours de calculs 2.40 0.00 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
249-NOELIA_20MGK36I-2-5-RND5686_0 10116835 160926 27 Sep 2014 | 9:33:35 UTC 27 Sep 2014 | 9:41:41 UTC Erreur en cours de calculs 10.39 2.96 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
747-NOELIA_20MGK36I-2-5-RND8713_0 10116750 160926 27 Sep 2014 | 9:41:42 UTC 27 Sep 2014 | 9:58:09 UTC Erreur en cours de calculs 7.78 2.95 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
232-NOELIA_20MGK36I-2-5-RND3755_0 10116603 160926 27 Sep 2014 | 9:33:35 UTC 27 Sep 2014 | 9:40:02 UTC Erreur en cours de calculs 7.30 2.34 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)
406-NOELIA_20MGWT-2-5-RND6078_0 10116559 160926 27 Sep 2014 | 9:41:42 UTC 27 Sep 2014 | 9:58:09 UTC Erreur en cours de calculs 4.18 2.22 --- Long runs (8-12 hours on fastest card) v8.41 (cuda60)

Best Regards

Philippe

Your 3.1GHz ties in well with what I thought the situation might be,

Assuming H5GQ2H24AFR R2C, these require 1.6V to support 3.5GHz.

Excluding the possibility of bad GDDR5 and bad circuitry (which we can do nothing about anyway), my guess is that the card isn't supplying the necessary 1.6V, and is either supplying 1.5V or 1.35V - possibly 1.5V for some people and 1.35V for others; with 1.35V perhaps being sufficient for 2.7GHz and 1.5V sufficient for 3.1GHz. This ties in with what has been reported here and suggests a firmware, driver or OS issue.

My solution would be to stick with it at 3.1GHz, if it proves to be stable, or sell the card and get an equivalent second hand card that does run at 3.5GHz.

288larsson who posted in this thread also has a Gigabyte GTX 780 Ti OC (Windforce 3x) GPU.

Alas I don't know how to change the GDDR5 voltage.

Hello !

How comes these 780Ti are doing OK on all other projects but GPUGRID ?

If it was a hardware issue, one should have problems on all projects I guess ?

Thank You

Hello Zoltan,

Thank you for your message.

the 2 * GTX780Ti = Gigabyte Windforce GV-N78TWF3 - 3GD

http://www.gigabyte.fr/products/product-page.aspx?pid=4912#sp

The PSU is a brand new CORSAIR RM1000 / 1000W 80+ Gold

MB = ASUS Z87PRO / CPU i7-4770K / WC AIO NEPTON 140 XL / RAM DDR3 Corsair vengeance 2 x 8 go 1600 Mhz CL10 LP

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


NB Should one allow 1 CPU core / WU or is 0.5 still OK ?

I see that your CPU time = GPU time, and on the only WU I finished, the CPU use is about 25 % of GPU time ? http://www.gpugrid.net/result.php?resultid=13111203

I have finished only 1 WU since I plugged in these cards last week ...

Thank You very much for your help !

Best Regards

Philippe

EDIT : Have modified app_config to 1 CPU / 1 GPU + Have decrased the "MEM CLOCK" from 3500 down to 3100, and it looks like the WU won't crash. At least, no error during the 6 first minutes.

Should one keep this 3100 Mhz as standard for GPUGRID or can I increase it step by step up to ???

Is this method extending the time it takes to complete the WU's ?

All WU's crashing / errors =>

Collatz (GPU use = 99 % thanks to a .config ad hoc file) until PrimeGrid recovers.

Hope to be able to run GPUGRID one day without any problem, as I bought these cards having in mind to increase my participation in this BIO project.

Thank You

Best,

Philippe

I see this card runs ~80C.

No. This card (GPU1) runs at 65-70°C.
The other card (GPU0) - which is a standard NVidia design - runs fine on 3.5GHz at 80°C.

Do you know Voltage control temps on card?

I don't know voltage control temps, but I think it should be lower than the other card's, as this card has more phase on that VR, and this card has better cooling.

Do you know temps for DDR memory? These temps run really hot on certain GTX780ti's

I don't know that either, but the same reasoning applies to the RAM chips as for the VRM chips.

Hello !

Thank you for your message.

These Gigabyte 780Ti are in an open case, with 3 extra fans helping cooling.

Or supposed to help cooling.

They don't exceed (GPU) 65° C, but no idea about the VRM temp ...

Have decreased the MEM CLOCK, unsuccessfully :/


On the other hand, they run just fine on Collatz, with an extra .config file
that utilizes the card at 99 %.

verbose=1
items_per_kernel=22
kernels_per_reduction=9
threads=9
sleep=1

The GPU temp is monitored using EVGA Precision X, and the fan speed (in %) = Temp + 10 => the 3 "Windforce" fans are running already very fast + the 3 external fans are helping with heat dispersal ...

Do you think the origin of the problem could be heat ?

NB : http://www.gpugrid.net/forum_thread.php?id=2507&nowrap=true#21073


This WU crashed after 1 hour only, GPU Temp about 62 ° ... :
http://www.gpugrid.net/result.php?resultid=13143650

Thank you for your message !

I am currently tryng to run short WU's

Have decreased the MEM CLOCQ by 300 Mhz

The volatge shown on EVGA Precision X is 1.2 for card 0 and 1.175 for card 1

Have added extra external fans, (= 4 external fans) in order to cool the back of the cards +
have now the PSU outside the case (it's a real mess ;) )

Will see if it works.

Thank You

Philippe

Would GPU WaterCooling be the ideal solution ?

Or better to change for 970/980 ?

Thank You

EDIT : It seems that today not only 780Ti have problems :/

EDIT 2 : I give up. All WU's crashing.

Hello !

Currently running other tests.

MB = ASUS Z87 Pro / PSU CORSAIR RM 1000

When GPUGRID runs on both GPU, the GPU Load =

94 % on card 0

65 % on card 1

?

=> WU on card 0 crashes first, and after a few seconds only.

This afternoon, I will try to run GPUGRID on card 1 (looks to be slow but TBC)
while running Collatz on card 0 (GPU Load = 99 %)

NB : The cards are 100 % stable running Collatz with high temp + GPU Load 99 %, even when both GPU @ work.


Do you think that GPU Watercooling might help ?

NB2 : 2 small external fans directed on the GPU's back ...

Thank You