You're crashing in the AMD driver, which is almost always the problem. Experiment with different driver versions...

Try the newer release, and try disabling hotplug if your keyboard is having issues too (--hotplug 0)

Don't set worksize, the default is better. Don't go above intensity 9. Try a different driver. But ultimately, as I said, every card is different.  Make sure you're using --auto-fan to ensure it stays cool enough too.

New version: 3.1.1 (for workgroups), 11th May 2013

3.1.0 was quite solid despite having the totally new driver for the BFL SC hardware. This is an incremental bug fix and improvement on it.


Human readable changelog:

- The stratum code has been rewritten by hand using raw socket code to NOT use libcurl. This should fix the random crashes that I cannot debug due to libcurl failing in random ways during network or pool outages. In the process, the ability to mine stratum via a proxy has been lost, but theoretically at least, ipv6 should be working now. Hopefully it should also be faster and more reliable at picking up pool outages as well.
- Scrypt mining now has a slightly larger buffer which may lead to less hardware errors on very fast GPUs.
- Scrypt solo mining will now show a meaningful WU rate by internally testing some lower diff shares even if they're not submitted.
- Scrypt solo mining will no longer try to submit any share >64k diff, instead submitting them only if they should solve the block.
- Decreased scantime by default with scrypt should lead to less stale shares submitted.
- There's a fix for setting up the tty for serial usb on Icarus type hardware.
- Fixes for writing configuration files when --device and --remove-disabled are specified.
- Logging fixes.
- Full data for 4 module Avalon devices.


Full changelog:

- Use a discrete device target for scrypt that dynamically changes to ensure we
still report a work utility even if no shares are submitted such as in solo
mining.
- Make set_work_target a function to set a specified char as target for use
elsewhere.
- Further consolidate the hash regeneration between sha and scrypt doing it only
once and always checking the share diff for both before submission.
- Regenerate the hash before checking the share diff in hashtest().
- Minor typo.
- Use a scantime of 30 seconds for scrypt if none is specified.
- Support more shares to be returned for scrypt mining.
- Update the write config to properly record device entries and remove disabled
option.
- Show a different warning and loglevel for failure to resolve a URL on first or
subsequent testing of stratum pool URLs.
- Fix the problem of seting up termio of ttyUSB0 for icarus. the CSIZE  is the
mask of CS2/4/8 From: navyxliu <navy.xliu@gmail.com>
- Set all stratum sockets to nonblocking to avoid trying to use MSG_DONTWAIT on
windows.
- Fix warnings on win32 build.
- Only use MSG_NOSIGNAL for !win32 since it doesn't exist on windows.
- Use MSG_NOSIGNAL on stratum send()
- Set TCP_NODELAY for !linux for raw sockets.
- Use TCP_NODELAY with raw sockets if !opt_delaynet
- Make raw sockets compile on windows
- Recheck select succeeds on EWOULDBLOCK for stratum.
- usbutils/mmq fixed size usb_read default to wait for all data
- usbutils optional (disabled by default) dev debug
- Add an ftdi usb read macro without newline
- Avalon usb interface should be 0.
- Add more debug for failure to USB init.
- Recv() should all be non-blocking for raw sockets in stratum.
- Change verbosity and error for getaddrinfo warnings in setup stratum socket.
- Free servinfo after p is checked in setup stratum socket.
- Use raw sockets without curl for stratum communications.
- Sacrifice curl handle memory on stratum disconnects on all versions of libcurl
to avoid curl corruption.
- Don't use TCP_NODELAY if opt_delaynet is enabled with stratum.
- Fix warnings in avalon driver.
- Make FULLNONCE an ULL to fix a warning on 32 bit.
- ztx correct applog typing
- ocl correct applog typing
- util correct applog typing
- api correct applog typing
- cgminer correct applog typing
- scrypt correct applog typing
- bfl correct applog typing
- ica correct applog typing
- mmq correct applog typing
- adl fix trailing %
- usbutils correct applog typing
- applog - force type checking
- Simplify the many lines passed as API data in the avalon driver now that the
API does not need persistent storage for the name.
- Duplicate the name string always in api_add_data_full to not need persistent
storage for names passed to it.
- Add extra matching work count data in API for Avalon with 4 modules.

Every card's different in how much overclock it can take. You're simply pushing yours too far.

Looks like you got moved yet again based on the original title of this thread that was in Khash, but you've since changed it...

Stats are shown whenever you report threads for one reason or another, and reports help keep the forum in order.

I have >100 reported posts so far with close to 100% accuracy.

Anyone else?

Told you it was everywhere! 70 posts reported so far just from mining/...

Yeah maybe. I'll look into it.

Muhahah...

EDIT: Thanks, and nice quick action on your part too 

That would be half the mining topics these days. Are you sure you want us to start doing that?

edit: Not that I object to that idea...

Since mining altcoins has proven profitable, there is endless discussion about it everywhere in the forum now, especially in the bitcoin/mining subsection. The signal to noise ratio for people interested primarily in bitcoin is dropping rapidly.

Should 1. The topics be moderated/moved to not include any altcoin discussion, 2. More subsections created for altcoin discussion (such as mining), or 3. Pretend altcoins are part of bitcoin?

not on linux

There are a very small number of integrated GPUs in newer Intel CPUs that can mine, but only on windows with the latest intel opencl.

However in terms of performance, they suck even bigger dicks than Nvidia GPUs do, so they're no better than CPU mining. Now go and read a billion other forum threads on why it's not worth it.

Could be unrelated. Was there any other message? It would tell you if the data was corrupted which is more likely if they all had it then... and wtf is <1MHash? Cgminer doesn't run on any hardware that slow.

Perhaps it hadn't disconnected but you were sending lots of shares and cgminer was simply waiting for the response to all of them and btcguild wasn't delivering. cgminer needs to keep a record of shares submitted until it gets a response. I've been meaning to find some useful way to throttle how many records it stores to prevent this from happening.

Nope. It can only happen when it runs out of some kind of resource. It doesn't mean the machine itself ran out of ram, but the OS refused to give it any more.

That sort of error (not specifically that, but it's one possibility) would happen when you run out of ram... the question is why are you running out of ram.

cgminer can mine any double sha256 coin with the ASICs it supports (i.e. not scrypt coins like litecoin) and avalons have been used to terrorise some of those altcoins already.

It's just not complete yet for ming which I assume you're compiling for.