Nobody has the foggiest idea We would be merely speculating ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Ain't we all in the stock markets .. im open to speculations.
|
|
|
Since it has been speculative up until this point, it has been flat due to lack of major news
But why no demand in spite of such a wider base now ? When do you think the next rise/fall might be ?
|
|
|
Of late BTC prices seem to have just been stuck ... why is it not moving up or down like earlier ?
|
|
|
Vcore being a fix value, when the load from the gpu goes down the only thing that can be reduced is amperage. check if gpu load is also lower when the amps go lower.
Will do and update. UPDATE : GPU load remains stable at 99%. What else could be causing the fluctuation in current ? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Hey the above update is not correct. The GPU load is fluctuating after kept it running for a day. Someone please help. I don't want to burn/damage my cards.
|
|
|
Ok now the VDDC voltage seems to be fluctuating !! Is it the power supply ? Should I continue mining ?
|
|
|
Try switching the PCI power connectors of the card and see if the same card that keeps getting his current drop.
Hmm nice suggestion ... will do it the next time I power my rig downn in the morning and update. Meanwhile still looking for any other ideas/suggestion as to why this might be happening.
|
|
|
Vcore being a fix value, when the load from the gpu goes down the only thing that can be reduced is amperage. check if gpu load is also lower when the amps go lower.
Will do and update. UPDATE : GPU load remains stable at 99%. What else could be causing the fluctuation in current ? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
Which PSU are you using and how many cards?
PSU : Silverstone 1200 W Cards : 3
|
|
|
Hi, One of my cards sometimes fluctuates the current level shown in GPU-z
The normal current lievel VDDC Current is 93-94 A (Amps).
However the card sometimes falls to 76-77 A for a few seconds and comes back to the level earlier.
Is this normal ? Or it something wrong perhaps with my PSU ?
PS: I recently had one of my burnt cards replaced so don't want the same situation again.
|
|
|
I have compiled a coin from litecoin source everything went smooth after a lot of troubles now that I have mycoind in src folder when I run it it says mycoind command does not exists.
You mean your creating your own coin or compiling the wallet ?
|
|
|
That is expected behavior - the card lowers the clock speeds when it is not under load to save energy. All of my GPUs do that.
Ok thanks a lot .. I was worried if my card was damaged. Btw all the other cards show the same rating ... hope thats ok.
|
|
|
Hi,
I was mining an scrypt coin and one of my cards got a burnt capacitor. Thankfully my other cards (remainin 2) were saved (or atleast so I think and am asking about the same).
Now the problem is that when I run GPU-z on the cards which were not damaged .. i see a reading of
GPU core - 150 MHz GPU memory - 300 MHz
This is when the cards are not mining.
This rating changes to normal default values when I start mining .. eg when I start mining with my 7950
GPU core - 925 MHz GPU memory - 1250 MHz
However as far as I can remember, I used to see the normal default rating of 925 and 1250 earlier before one of my cards went bust, irrespective of the fact I was mining or not.
Can anybody confirm if GPU-z shows same readings when mining and when not mining ? And if it does show the same reading in both cases then does it mean that my remaining card (for eg the 7950 mentioned above) is faulty for showing lower ratings ?
Please help.
|
|
|
Ok so since I am almost going crazy as to what is happening .. I tried to see if the 7950 card works with mining .. turns out that the "sensors" tab in GPU-z was showing a lesser reading when not mining for GPU core and GPU memory clocks ... when I started mining with the 7950 it showed proper reading of 925 MHz and 1250 Mhz which is default and now after stopping mining it still shows the same.
Is this normal ?
TLDR : Is GPU-z "sensors" value for GPU core and GPU memory same as that specified for the card when the computer starts compared to when its mining ? cause mine is way different
|
|
|
The sparks / fires are usually caused by ripple capacitors for the VRAM exploding on startup :] I've had 2 Gigabyte 7950's do this so far, however, they both still work fine.
It's always the same... the rig shuts down without warning, then when you turn it back on... BOOM...
The good news is I never had an issue (so far) with rigs exploding while running.
I've had it happen on both powered and unpowered risers... usually the issue is just poor PCB layout in that not enough cooling air gets to this part of the board.
I've also destroyed 1 Mobo when this occurred and the other Mobo lost a PCI-E slot so be careful...
Ok one more spark and now I can see that a 280x has a capacitor blown .. I can see the carbon !! Now the problem is that the other 2 cards (one 7950 and one 280x are plugged in ) .. both are showing in GPU-z : GPU Core Clock : 300 MHz GPU Memory Clock : 150 MHz This is clearly not what it was earlier. However the sapphiretrixx shows proper clocks for memory and core clock readings that had come with the cards. Are the cards dead ? Should I still try to mine with the cards ? Why the discrepancy between GPU-z and sapphiretrix ? Or is the PCI-e slot gone ? Now I'm really scared about the cards , don't have the courage to even try mining with the remaining 2 cards .. what should I do ? All cards and mobo are under warranty. Please Please Please help !!
|
|
|
Shutdown this time after 12 hours and did not restart .. now will try without a 280x and see if it shutsdown .. wish there was a better way to diagnose .. this is getting too risky now .. since I do not know even which card it is.
If you too happen to find a solution let me know .. still desperately looking for a solution .. dont want my Mobo to get fried.
|
|
|
I would love to know the fault as well but there's no way I'm trying to plug this back in again, its going back for sure as a full out fire started in the card. There's visible damage on the actual card of where the flames burst out from. Really scary situation and I'm grateful it happened when I was home.
Well it just happened to shutdown and restart again ... don't know if there were flames or not since I wasn't looking towards it this time .. I will leave it running through the night and if I find it has shutdown and restarted again then I will stop all mining I guess or try it with 2 cards at a time. Now its getting more scary than exciting ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
280x will blow out caps sometimes, it will probably still mine fine after (its kinda scary/exciting though)
+1 for scary/exciting ..thats for sure ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) How do I check if the capacitor is blown though ? any idea/simple way ? I'm not that much of a techie.
|
|
|
The fire I had recently happened from off-state to when I turned it on (although it shouldn't have been off, it seemed to have crashed or powered down and not due to a power failure). Just 5 weeks old, definitely no dust and no pets/hair, with open rig and external fan. I'm almost certain its not a dust issue as it was really new. The rig I have was running at 82c and was 2 XFX 7950's Double D's, from what I've read they aren't a good miners card, but they should not be catching fire. I've stopped overclocking and brought the temp down to 79c and will be RMA'ing the one that caught on fire as that thing is not going near my PC ever again!
Even mine is about 5 weeks old or so and cards are sapphire brand, so I am also starting to doubt whether its because of dust balls. About you RMAing it : don't you need to pinpoint some fault in the card as a reason to do it ? I mean is your card actually burnt .. can you see it ? cause I can't see it on mine (I have just seen superficially though and could not see any carbon marks). I want to know how I can pinpoint the fault in the card(s) so that atleast when I take it to the shop to return/replace I should be able to tell them what the fault is. So still no definitive answers yet.
|
|
|
Although your theory seems very plausible and it may very well be because of the dust balls, reason being: the fire has not recurred since I have not overclocked and the rig is running at close to 77 C, i e , 3-5 C less than it was when overclocked. Maybe that might be the critical temperature for dustballs to ignite, who knows lol. Trust me it's more than a theory. I've worked in server rooms most of my life. Seen many fires. They're all caused by idiots overloading cables or poor maintenance (dust build up). I've seen power supplies shooting flames like flame throwers several feet out the fan exhaust! ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) Hmm im not doubting your honesty or intention. I appreciate all your help buddy, thanks for that. But however if it was of dustballs then in that case 2 questions arise : 1) Why did it not happen again without overclocking ? possible reason: it may be that that the dust bulls got burnt in the first 2 instances or flames perhaps. 2) Why did it not happen again without cleaning it ? possible reason : maybe it wasn't because of the dust balls in the first place perhaps. So thats why I am calling it a "theory" for now, until further evidence either way. But sure I got to give it to you - its the most "plausible theory". And to test that I will wait another 24 hours and then clean it with compressed air perhaps, cause I have a feeling it wont give flames. Lets see again thats just my "intuition/theory".
|
|
|
|