It doesn't crash
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 424. (Read 5805983 times)
December 13, 2012, 04:13:12 AM
I like the debug version of cgminer aimed to collect some info on crash.
It doesn't crash
It doesn't crash
December 12, 2012, 11:35:16 PM
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
haha, SOON! once ASICs hit I will be attempting to use my raspberry pi. Death to windows then
December 12, 2012, 11:27:46 PM
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
And I have wished for years they were banned from connecting to the internet...
December 12, 2012, 11:20:04 PM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Yeah I noticed the same. All of mine crashed at the same time upon detection of a new block.
BTW, thanks ckolivas for the debugger. I'll be sure to give that a go in case any of my rigs crash again.
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
December 12, 2012, 11:19:10 PM
I have a bunch of modminers running on ubuntu and on the new version 2.10.0 the display is showing each fpga individually and I can't see all of them. Also the accept share display isn't showing due to the fact that there is to many devices. Is there anyway to fix this. Thanks.
compact mode, or use more remote monitoring with something like miner.phpHow do you run compact mode? I never had to use this option before.
--compact Use compact display without per device statistics
Or from the menu while it's running, press D for display and you'll see it there.
It does get rid of all the device stats tho.
December 12, 2012, 11:11:18 PM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Yeah I noticed the same. All of mine crashed at the same time upon detection of a new block.
BTW, thanks ckolivas for the debugger. I'll be sure to give that a go in case any of my rigs crash again.
December 12, 2012, 10:50:18 PM
I have a bunch of modminers running on ubuntu and on the new version 2.10.0 the display is showing each fpga individually and I can't see all of them. Also the accept share display isn't showing due to the fact that there is to many devices. Is there anyway to fix this. Thanks.
compact mode, or use more remote monitoring with something like miner.phpHow do you run compact mode? I never had to use this option before.
December 12, 2012, 10:46:29 PM
I have a bunch of modminers running on ubuntu and on the new version 2.10.0 the display is showing each fpga individually and I can't see all of them. Also the accept share display isn't showing due to the fact that there is to many devices. Is there anyway to fix this. Thanks.
compact mode, or use more remote monitoring with something like miner.php December 12, 2012, 10:43:30 PM
I have a bunch of modminers running on ubuntu and on the new version 2.10.0 the display is showing each fpga individually and I can't see all of them. Also the accept share display isn't showing due to the fact that there is to many devices. Is there anyway to fix this. Thanks.
December 12, 2012, 08:56:43 PM
I've uploaded some fresh debug builds for windows here for those who want to try and help me get debug information:
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
Nice! I should have been doing this the whole time. I am running it like this now and will let you know if it crashes again. So far it's been going 6 hours and no problems yet.
Yeah, 2.9.7 crashed on me as well this morning. I don't know why, just got a nice Windows error and close program. Trying 2.10.0 now.
Was that 2.9.7 or 2.9.7-1?
December 12, 2012, 08:33:50 PM
could it be a stratum issue?
Well it is 12/12/12. Maybe the end of the world is at hand
December 12, 2012, 08:25:36 PM
could it be a stratum issue?
December 12, 2012, 08:23:07 PM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
December 12, 2012, 07:37:01 PM
Yeah, 2.9.7 crashed on me as well this morning. I don't know why, just got a nice Windows error and close program. Trying 2.10.0 now.
December 12, 2012, 06:21:07 PM
I got my very first crash on 2.9.7 this morning. Win7 32 bit.
I just updated to 2.10. My crashes have been few and far between. So I'm not even sure it's a CGMiner problem or not. I'll keep an eye on it and see if I have any reproducible problems.
Thanks for your effort,
Sam
I just updated to 2.10. My crashes have been few and far between. So I'm not even sure it's a CGMiner problem or not. I'll keep an eye on it and see if I have any reproducible problems.
Thanks for your effort,
Sam
December 12, 2012, 04:55:26 PM
I've uploaded some fresh debug builds for windows here for those who want to try and help me get debug information:
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
December 12, 2012, 04:06:17 PM
Bug report:
Not sure if there is a place I should report bugs or if this bug has been reported but I can't be bothered to find out so I figured reporting it here is better than nothing.
Bug:
MH/s between GPU0 and GPU1 is flipped. Everything else is correctly matching the right GPU but apparently my 6950 is giving me 25MH/s and my 6450 is giving me 369MH/s. I upgraded from version 2.7.5 where this issue didn't exist.
I have not tested just running one of my cards or with more than 2 cards.
6950 appears in the top line and 6450 appears in the bottom line. while the MH/s are reversed.
Setup:
CGminer 2.9.7
Windows 8
GPU0 6950 unlocked xfx xxx
GPU1 6450 gigabyte passive
MSI motherboard with 2x pci-e 16x 8x 6950 in top slot
Not sure if there is a place I should report bugs or if this bug has been reported but I can't be bothered to find out so I figured reporting it here is better than nothing.
Bug:
MH/s between GPU0 and GPU1 is flipped. Everything else is correctly matching the right GPU but apparently my 6950 is giving me 25MH/s and my 6450 is giving me 369MH/s. I upgraded from version 2.7.5 where this issue didn't exist.
I have not tested just running one of my cards or with more than 2 cards.
6950 appears in the top line and 6450 appears in the bottom line. while the MH/s are reversed.
Setup:
CGminer 2.9.7
Windows 8
GPU0 6950 unlocked xfx xxx
GPU1 6450 gigabyte passive
MSI motherboard with 2x pci-e 16x 8x 6950 in top slot
December 12, 2012, 03:13:48 PM
I'm also having a similar issue where CGMiner freezes after a certain amount of time. Sometimes it can go fine for a few days but lately its been crashing more frequently.
I tried a new .conf file, reverting to stock clocks, different video cards, etc. And this has been happening on all of my rigs, not just one.
I tried a new .conf file, reverting to stock clocks, different video cards, etc. And this has been happening on all of my rigs, not just one.
I just had this happen to me on cgminer 2.9.7-1 with 4 BFL singles on it running windows 7 64-bit. It was going strong for 2 days before it crashed.
i had it happen before, but i thought it was because i overclocked my GPU too much, so i put the overclock to a little less and didnt have issues anymore, until just 10 minutes ago, i thought maybe my GPU is too hot or whatever, until i read your post, where you say you only have BFL's and no GPU's... so i don't think it is because i overclocked it too much (it is also on lower settings now) .., the few times it happened I was sitting behind it and doing stuff, so maybe it doesnt like that, gets conflicted or whatever.... but who knows... ,, 2.10.0 here
December 12, 2012, 03:04:25 PM
I'm also having a similar issue where CGMiner freezes after a certain amount of time. Sometimes it can go fine for a few days but lately its been crashing more frequently.
I tried a new .conf file, reverting to stock clocks, different video cards, etc. And this has been happening on all of my rigs, not just one.
I tried a new .conf file, reverting to stock clocks, different video cards, etc. And this has been happening on all of my rigs, not just one.
I just had this happen to me on cgminer 2.9.7-1 with 4 BFL singles on it running windows 7 64-bit. It was going strong for 2 days before it crashed.
Not sure if any of this helps:
Log Name: Application
Source: Application Error
Date: 12/12/2012 1:58:22 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x50c1381c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x746e6563
Faulting process id: 0x114c
Faulting application start time: 0x01cdd7f97143ad35
Faulting application path: C:\Users\~\Desktop\cgminer-2.9.7-1-win32\cgminer.exe
Faulting module path: unknown
Report Id: 479d2843-4496-11e2-b593-bc5ff4351e2e
December 12, 2012, 02:59:27 PM
i'm at 2.9.7-1 on win 7 with 6970's gpu's and my machines are shutting down completely as well.
Jump to: