|
1)
Message boards :
Number crunching :
Not getting new work
(Message 47528)
Posted 2482 days ago by  Misfit
If this is your only GPU project you can attach to a second GPU project and set its resource share to zero. That way it'll only run when this project is out of work. |
|
2)
Message boards :
News :
Happy holiday season
(Message 39209)
Posted 3409 days ago by Misfit
Merry Christmas! Enjoy your holiday. |
|
3)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 38141)
Posted 3490 days ago by Misfit
Cuda60 has been churning good, and I've ditched the MSI app for the one from EVGA. Thanks for the help. |
|
4)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37937)
Posted 3501 days ago by Misfit
I would envision that those files wouldn't matter. They are symbol files that are downloaded, I think, whenever a BOINC debug version crashes or is debugged. True - but I can't help but wonder maybe some file (the cuda60 exe) got borked. I've turned in 4 straight valid WUs since the wipe and clean install. Well at least now I know more about my card than I ever thought I would need. I know where the stable point is. And the problem appears to be fixed. Overnight I'll return the card to its default values and see if the instability churns up any errors. At least that way I can determine if the card contributed to the problem. |
|
5)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37927)
Posted 3503 days ago by Misfit
It makes sense. Thanks Jacob. Here is something interesting. I did a boot scan (Avast) and that turned up a couple of corrupted BOINC files. ProgramData\boinc\symbols\Kernelbase.pdb ProgramData\boinc\symbols\ole32.pdb So I completely uninstalled boinc, wiped it off the drive and out of the registry, and reinstalled. Right now it's crunching away a cuda60 where normally it would've crashed. I'm hoping I'll get lucky and this would have been the cause of the problem although I have no idea what these files do and why they would only effected gpugrid cuda60. |
|
6)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37909)
Posted 3504 days ago by Misfit
Heaven ran overnight at -65 with no crashes and no watchdog dmps. However even at 80% fan speed it was holding at 71C. With the noise at that speed I pretty much have a hair dryer at arm's length; which I can't have since this is my gaming rig and not a cruncher in the garage. Max temp under Heaven has never reached 80C even when it was 80F inside the house and the fan speed set to auto - sometimes will hit 60% which is audible but not bothersome. I can live with the card throttling down a step. (And my max setting will be somewhere between -65 and -53.) The link is more for my benefit since I lost it once, but it could have been written by you. I see no harm in asking. Thanks for the Precision link. I have it now and will see how it compares to Afterburner - although too much noise is still too much. |
|
7)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37903)
Posted 3505 days ago by Misfit
I've tried to DL your Precision-X however it's currently unavailable. Some sort of copyright controversy with it. MSI has just released v4 of it's Afterburner so I've upgraded. I've also upgraded back to the 340.52 nvidia drivers. Source is by experience. Are you SeanPoe? Are you saying your GPU doesn't increment like that? Can you confirm with exact steps? Conditionally yes and no. When I was adjusting the GPU speed I wasn't under a full load. Many times when I've adjusted with gpu grid running it crashed the WU. When I was running Heaven fullscreen there was also no way of adjusting speed without, at a minimum, exiting the window which would instantly change what was shown in GPU-Z. So going from your last post and the guide in the link my max kepler boost before things start getting dropped by temperature is 7 offset steps (91mhz). Running the GPU-Z render test does confirm the 13 drop when I manually drop it by 1 as shown in your example. |
|
8)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37871)
Posted 3510 days ago by Misfit
Per GPU-Z it showed a 1mhz boost change per 1mhz clock change. So the boost is staying constant at 78 mhz above. |
|
9)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37860)
Posted 3510 days ago by Misfit
Back to a full night test of Heaven, going by the 13 interval at -39 it ran for 9 hours before the uningine stopped responding. Interesting enough at the next interval -52 the uningine stopped responding 7 hours in. Now they both pass the 5 hour mark but I don't know if technically it's supposed to go on like the Energizer bunny. I believe you can use Afterburner, as it functions nearly identically to Precision-X. You are looking to control the "GPU Clock" to ensure maximum stability, and Kepler GPUs ramp up and down in 13 Mhz intervals. The Core Clock slider changes the base speed which is then boosted. However the boost always seems to be 78 MHZ and always seem to be on if the card is running 3D apps. What was your source of the 13 mhz interval? |
|
10)
Message boards :
Graphics cards (GPUs) :
nVidia driver 340.52
(Message 37794)
Posted 3516 days ago by Misfit
I don't have (evga) Precision-X. Should I dump (msi) Afterburner for it? |
Next 10
