I actually turn swap off on all of my primary machines, for a number of reasons, primarily for security, though. Having worked it data forensics for awhile, you'd be horrified to see what kind of cruft is left over in your swap file in Windows that can be easily recovered with the right tools. Even if you delete your swap file regularly, chances are large portions of previous swap files are still floating around on your disk, not yet written over by the OS.
First thing I do is turn it off... in this case, this machine has 24 GB of RAM, so if it's swapping, it's got other issues that are far more pressing than running out of memory for what I use it for. I went back to a previous version of CGMiner that I know worked and it had the same problem, so it's definitely not any changes made to CGminer that are causing it.
I will try X'ing out of CGMiner instead of Q'ing out to see what happens there, but I don't hold out a lot of hope for that.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 572. (Read 5806088 times)
May 14, 2012, 10:25:08 AM
May 14, 2012, 09:21:28 AM
And totally off topic:
At work, our analysis server's storage array just got upgraded to 20 250GB Enterprise grade SSD. Utterly mindblowing performance on complex simulations. The coolest part is the array chassis is only 2U and has hotswap bays for 32 2.5" drives.
It is only a matter of time before SSD replace everything (except maybe nearline storage). The only con is cost and that is falling by about 50% every year (faster than Moore's law).
Everyone needs to experience a huge array of enterprise SSDs at least once in their life. At work, our analysis server's storage array just got upgraded to 20 250GB Enterprise grade SSD. Utterly mindblowing performance on complex simulations. The coolest part is the array chassis is only 2U and has hotswap bays for 32 2.5" drives.
It is only a matter of time before SSD replace everything (except maybe nearline storage). The only con is cost and that is falling by about 50% every year (faster than Moore's law). It is very impressive. And, I doubt you can make your throughput graphs dip when you shout at the array, like you can with regular drives. 
EDIT: http://www.youtube.com/watch?v=tDacjrSCeq4
May 14, 2012, 09:10:18 AM
Is your swap file and temp directory set to the SSD? If so I would put a regular spinning hard drive in the system just for that purpose. It's supposedly bad to continuously re-write data to SSD's.
True to a point. Still in any properly configured system the amount of writing done to swap and temp file shouldn't materially contribute to wear leveling. All SSD have a finite amount of writes, but wear leveling, and overbuilding (480GB SSD likely has 500GB to 550GB of actual flash) mean they should work just fine for years.
Some back of napkin math:
480GB SSD (w/ 500GB actual flash) and 500K avg writes per cell. Swap file wites per day 1TB (very unlikely).
Gross write throughput = 500 GB * 500K = 250 PB (1PB = 1000TB).
In 10 years swap file writes ~= 4 PB. Roughly 2% of drive's rated write capacity. It is unlikely someone swap file usage aproaches anywhere near 1 TB per day unless they randomly open and close applications on a near continual basis. When drives were much smaller, had low write ratings, and system memory was more expensive (greater % of paging) it was more of an issue.
And totally off topic:
At work, our analysis server's storage array just got upgraded to 20 250GB Enterprise grade SSD. Utterly mindblowing performance on complex simulations. It provided more of a performance boost then increasing the RAM from 32GB to 64GB and cost less. The coolest part is the chassis for the external array is only 2U and has 32 2.5" hotswap bays.
It is only a matter of time before SSD replaces everything (except maybe nearline storage). The only con is cost and that is falling by about 50% every year (faster than Moore's law). May 14, 2012, 09:04:28 AM
If I type in --temp-cutoff 60
would this mean that if a gpu core reaches 60c then CGminer turns off?
would this mean that if a gpu core reaches 60c then CGminer turns off?
Yes. Technically cgminer never shutdown it simply turns the GPU threads to disabled and idles them. Remember even idle the GPU are going to dump ~30W ea into the loop (less for 7000 series). Also see the notes of hyseresis below (by default cutoff wouldn't occur until 63).
Quote
Right now my GPU core never goes above 52c, the VRM however reached 65c.
So unless pump fails I will never reach more then 52c if that makes sense.
edit---> I found this in my cgminer.cfg
"temp-cutoff" : "95", This I put 65
"temp-overheat" : "85", This I put 64
"temp-target" : "75", This I put 64
^^^^^^^ There is no fans controlled by GPU, it's radiator with fans.
temp-target & overheat should be set but it won't have much effect.
when temp > temp-target + hysteresis then cgminer will either lower the clock OR raise the fan*
when temp > temp-overheat + hysteresis then cgminer will drop clock to lowest value AND set fan @ 100%.
when temp > temp-cutoff + hysteresis then cgminer will disable GPU thread (forced idle)
A couple of other notes:
You must have "auto-gpu" : true in your config file or cgminer will ignore all the above values.
If you set a gpu clock range (gpu-engine: 750-850) then cgminer will start @ highest clock and lower it as temp > temp-target.
If you set no gpu range (gpu-engine: 850) then cgminer will create a range from default to specified value (i.e. 725-850 for a 5970).
For watercooling the temp-target & temp-overheat values will not have much effect. It will cause cgminer to lower clocks but watercooling is so good at keeping temps in line any jump in temp likely means lowering the clocks won't be sufficient to keep system from going over the cutoff value.
Keep in mind the effect of the hysteresis value (default is 3?). It is how far the temp has to move above or below the specified value for an effect to take place. So if your cutoff is 60 and hysteresis is 3 then your GPU won't idle until 63. Make sure to consider that when setting your values.
May 14, 2012, 08:09:33 AM
Does it do the same when you just force-close it by hitting the "x" vs Q? What's the benefit of using Q?
May 14, 2012, 07:46:05 AM
It's a 480 GB SSD, I don't think Spinrite will help
The box is a fairly recent reload, I'm not keen on doing it again. I was hoping someone might have a magic bullet.
Ah, no I don't think it would be good to run any hard drive utility on an SSD.
Is your swap file and temp directory set to the SSD? If so I would put a regular spinning hard drive in the system just for that purpose. It's supposedly bad to continuously re-write data to SSD's.
Sam
May 13, 2012, 01:56:32 PM
Ok, so I'm at stumped, maybe someone has an idea:
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work. I've uninstalled and reinstalled several different drivers versions, including 11.2 which I know worked with v2.4, v2.5 and v2.6 of the SDK. Nothing changes the behavior.
I realize it's not directly a CGMiner problem and something is wrong somewhere in the system, but bugger all if I can figure out what it is. Does anyone have any ideas? I've tried Driver Sweeper and reinstalled the drivers from scratch, but nothing works.
The system operates fine, I can play games, etc... and CGMiner mines fine. The only time there is a problem is when I quit CGMiner, otherwise zero problems at all. I'm completely stumped.
PS - this is mining with a pair of 6990's.
Anyone?
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work. I've uninstalled and reinstalled several different drivers versions, including 11.2 which I know worked with v2.4, v2.5 and v2.6 of the SDK. Nothing changes the behavior.
I realize it's not directly a CGMiner problem and something is wrong somewhere in the system, but bugger all if I can figure out what it is. Does anyone have any ideas? I've tried Driver Sweeper and reinstalled the drivers from scratch, but nothing works.
The system operates fine, I can play games, etc... and CGMiner mines fine. The only time there is a problem is when I quit CGMiner, otherwise zero problems at all. I'm completely stumped.
PS - this is mining with a pair of 6990's.
Anyone?
Maybe some other things in your BIOS/drivers are interfering with ATI.
Did you try a clean machine (formatted re-install of OS) with 12.2 and SDK 2.6? 12.2 or 12.3 has been the most stable in my experience.
May 13, 2012, 11:09:09 PM
Ok, so I'm at stumped, maybe someone has an idea:
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work.
Anyone?
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work.
Anyone?
Did you find this article?
http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949%28v=vs.85%29.aspx
I would run Spinrite on the drive.
Sam
It's a 480 GB SSD, I don't think Spinrite will help
The box is a fairly recent reload, I'm not keen on doing it again. I was hoping someone might have a magic bullet.
May 13, 2012, 09:50:27 PM
I know that there is a built in function to stop mining incase of temperature too high.
Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
If you enable the --auto-gpu option, it turns on the auto-disable feature using the default values (95). It will also re-enable them if the temperature falls below the target temperature (75) unless you add the --no-restart option.Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
If I type in --temp-cutoff 60
would this mean that if a gpu core reaches 60c then CGminer turns off?
Right now my GPU core never goes above 52c, the VRM however reached 65c.
So unless pump fails I will never reach more then 52c if that makes sense.
edit---> I found this in my cgminer.cfg
"temp-cutoff" : "95", This I put 65
"temp-overheat" : "85", This I put 64
"temp-target" : "75", This I put 64
^^^^^^^ There is no fans controlled by GPU, it's radiator with fans.
May 13, 2012, 09:47:07 PM
I got this :
Situation: Running Z68 board + 2x 5850s + Windows7. Using IntelHD for display, AMD GPUs are not connected to any monitors. AMD GPUs driver is installed and recognized by windows. I want to use IntelGPU for desktop as its a workstation, and mining the AMD GPUs
What should i be looking at?
Code:
ADL found less devices than opencl!
There is possibly more than one display attached to a GPU
...
Failed to initiate GPU thread 0, diabling device 0
Failed to initiate GPU thread 1, diabling device 0
Failed to initiate GPU thread 2, diabling device 1
Failed to initiate GPU thread 3, diabling device 1
Situation: Running Z68 board + 2x 5850s + Windows7. Using IntelHD for display, AMD GPUs are not connected to any monitors. AMD GPUs driver is installed and recognized by windows. I want to use IntelGPU for desktop as its a workstation, and mining the AMD GPUs
What should i be looking at?
May 13, 2012, 07:22:56 PM
I know that there is a built in function to stop mining incase of temperature too high.
Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
If you enable the --auto-gpu option, it turns on the auto-disable feature using the default values (95). It will also re-enable them if the temperature falls below the target temperature (75) unless you add the --no-restart option. Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
May 13, 2012, 07:17:32 PM
I know that there is a built in function to stop mining incase of temperature too high.
But is there a option to turn off PC?
...
No.But is there a option to turn off PC?
...
The API will of course allow you to identify a whole lot of info about the state of your miner.
May 13, 2012, 07:07:25 PM
I know that there is a built in function to stop mining incase of temperature too high.
But is there a option to turn off PC?
I have waterpump and incase pump failure, so if temperatures reach 60c I want to force PC shutdown.
Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
But is there a option to turn off PC?
I have waterpump and incase pump failure, so if temperatures reach 60c I want to force PC shutdown.
Edit---> For disabling CGminer do I need to put in a value or it the default 95c activated?
So if GPU reaches 95c will the CGminer disable or would I need to add it into config file?
I'm on windows 7 64bit.
May 13, 2012, 05:28:34 PM
Question: Is there a way to mine on multiple pools at the same time with CGMiner? In other words, if I have 2 BFL miners, and want to point one to one pool, and another to another pool, how would I go about setting that up?
The --load-balance flag will basically do that for you. 
May 13, 2012, 05:24:58 PM
Question: Is there a way to mine on multiple pools at the same time with CGMiner? In other words, if I have 2 BFL miners, and want to point one to one pool, and another to another pool, how would I go about setting that up?
May 13, 2012, 03:10:18 PM
I'm seeing some odd behavior if I use load-balance for the pool strategy under 2.4.1.
I'm mining on EMC and Ozcoin. If I use the default failover pool management strategy, I get a rejection rate of 0.4% or lower with either EMC or Ozcoin as the primary. If I use load-balance, my rejection rate goes up to around 4 or 5%.
I'm mining on EMC and Ozcoin. If I use the default failover pool management strategy, I get a rejection rate of 0.4% or lower with either EMC or Ozcoin as the primary. If I use load-balance, my rejection rate goes up to around 4 or 5%.
I believe this, at least partially, because of Merged Mining. You get allot of Namecoin Long Poll's. On Ozco you can disable NMC LP's, don't know about EMC but I would check and see if disabling NMC LP's helps.
Sam
May 13, 2012, 03:00:48 PM
I'm seeing some odd behavior if I use load-balance for the pool strategy under 2.4.1.
I'm mining on EMC and Ozcoin. If I use the default failover pool management strategy, I get a rejection rate of 0.4% or lower with either EMC or Ozcoin as the primary. If I use load-balance, my rejection rate goes up to around 4 or 5%. I can see in the logs that, when a longpoll indicates a new block, cgminer will submit 1 or 2 rejected/stale shares for pool 0, and then subsequent pool 0 shares are accepted. For pool 1, however, cgminer continues to submit stale shares for a couple minutes. I'm not sure if this is new behavior or not, as I haven't tried to use load-balance prior to 2.4.1.
I'm mining on EMC and Ozcoin. If I use the default failover pool management strategy, I get a rejection rate of 0.4% or lower with either EMC or Ozcoin as the primary. If I use load-balance, my rejection rate goes up to around 4 or 5%. I can see in the logs that, when a longpoll indicates a new block, cgminer will submit 1 or 2 rejected/stale shares for pool 0, and then subsequent pool 0 shares are accepted. For pool 1, however, cgminer continues to submit stale shares for a couple minutes. I'm not sure if this is new behavior or not, as I haven't tried to use load-balance prior to 2.4.1.
May 13, 2012, 02:14:27 PM
Ok, so I'm at stumped, maybe someone has an idea:
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work.
Anyone?
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work.
Anyone?
Did you find this article?
http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949%28v=vs.85%29.aspx
I would run Spinrite on the drive.
Sam
May 13, 2012, 01:06:17 PM
...
I'm having the same issue. Did you ever figure out a fix?
https://bitcointalksearch.org/topic/m.886474 I'm having the same issue. Did you ever figure out a fix?
May 13, 2012, 01:02:12 PM
Ok, so I'm at stumped, maybe someone has an idea:
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work. I've uninstalled and reinstalled several different drivers versions, including 11.2 which I know worked with v2.4, v2.5 and v2.6 of the SDK. Nothing changes the behavior.
I realize it's not directly a CGMiner problem and something is wrong somewhere in the system, but bugger all if I can figure out what it is. Does anyone have any ideas? I've tried Driver Sweeper and reinstalled the drivers from scratch, but nothing works.
The system operates fine, I can play games, etc... and CGMiner mines fine. The only time there is a problem is when I quit CGMiner, otherwise zero problems at all. I'm completely stumped.
PS - this is mining with a pair of 6990's.
Anyone?
I have a W7 x64 box that I reloaded recently. I loaded the ATI drivers and the SDK... firing up CGMiner, it mines just fine. However, when I q out of CGminer, W7 will BSOD with a SYSTEM_SERVICE_EXCEPTION in atikmdag.sys. I've Googled the hell out of it and tried all the suggestions and nothing seems to work. I've uninstalled and reinstalled several different drivers versions, including 11.2 which I know worked with v2.4, v2.5 and v2.6 of the SDK. Nothing changes the behavior.
I realize it's not directly a CGMiner problem and something is wrong somewhere in the system, but bugger all if I can figure out what it is. Does anyone have any ideas? I've tried Driver Sweeper and reinstalled the drivers from scratch, but nothing works.
The system operates fine, I can play games, etc... and CGMiner mines fine. The only time there is a problem is when I quit CGMiner, otherwise zero problems at all. I'm completely stumped.
PS - this is mining with a pair of 6990's.
Anyone?
Jump to: