OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[mdude77]

I'm experiencing a very odd and blocking problem: was mining with CGMINER 3.1.0 on Radeon HD 5750, never had problem, with SHA256 nor Scrypt, all was fine.
At some point I tried CGMINER 3.2.0 and it crashed at start (could only see one line "Started CGMINER 3.2.0" and then crashed).
The odd thing is that from that point over even all other versions of CGMINER do the same!!! I cannot anymore use CGMINER! I've tried with 3.1.1 (that I'm succesfully using on another PC): crash. 3.1.0 that was working well before: crash. Today I tried even 3.2.1: crash.
I did a Dr. Mingw debug for you, hoping to understand what the hell is happening.

sounds like a task is still running, or you need to reboot?

M

[energywave]

thank you for answering me

sounds like a task is still running, or you need to reboot?

A task is still running? I don't understand, however I've rebooted several times without positive effects. Last try was to install catalyst 13.6 beta2 (I was on 13.5 beta that worked flawlessy, before to try CGMINER 3.2.0)

Did you delete bin files? Reset the drivers to USB/COM?  If nothing works, re-compile and remove all the fpga stuff.

At first try I've copied CGMINER 3.2.0 files inside my old 3.1.0 CGMINER folder to update files (yes, all files + folders). That was the first crash, then I prepared a separate folder for every CGMINER version to be sure that no old file was messing up something. All my tried after first crash are from clean, just extracted folders.
Reset drivers to USB/COM: what is that? I'm mining with just GPU, no FPGA nor ASIC.
Recompile removing FPGA stuff... Uhm... that's will be my last last last resource.... Do you believe something about FPGA/ASIC is involved? If so why even returning to older 3.1.0 that was working is still crashing my system?
For instance Bitminter java client is mining flawlessy.

Damn, what a strange problem...

[Tamis]

Hi guys !

I really hope someone will be able to help me with this problem.

I just added a HD 5870 (ATI) to my computer that already has a gtx-680 (nvidia). Having read that in windows 7 you can install both cards without a problem
I was happy to see instalation was not a problem. The latest beta catalyst drivers (AMD Catalyst™ 13.6 Beta2) instaled without a problem and both card are recognized by windows. I did not install any SDK since it was not necessary with the 13.6 beta2 with my HD 5850 that runs in another computer.

I though I could launch cgminer with default command line and the babies do their work, but I get an error message in cgminer :/

command line to launch cgminer : cgminer.exe -o http://stratum.bitcoin.cz:3333 -u user -p pass


I get the following errors :



and once I press enter :




I searched for an answer on the forum and the web and the only solution I found involves disabling the nvidia card, connecting the screen to the amd card and launching the miner

then enabling the nvidia card and switch the screen again. I have not tested this yet but it is not very practical.

There is also a similar post on this forum but no answer was given :  https://bitcointalk.org/index.php?topic=174091.0


I can do a cgminer -n dump if needed !


I hope someone can help me through this problem.


Tamis

[Zanatos666]

Hi guys !

I really hope someone will be able to help me with this problem.

I just added a HD 5870 (ATI) to my computer that already has a gtx-680 (nvidia). Having read that in windows 7 you can install both cards without a problem
I was happy to see instalation was not a problem. The latest beta catalyst drivers (AMD Catalyst™ 13.6 Beta2) instaled without a problem and both card are recognized by windows. I did not install any SDK since it was not necessary with the 13.6 beta2 with my HD 5850 that runs in another computer.

I though I could launch cgminer with default command line and the babies do their work, but I get an error message in cgminer :/

command line to launch cgminer : cgminer.exe -o http://stratum.bitcoin.cz:3333 -u user -p pass


I get the following errors :



and once I press enter :




I searched for an answer on the forum and the web and the only solution I found involves disabling the nvidia card, connecting the screen to the amd card and launching the miner

then enabling the nvidia card and switch the screen again. I have not tested this yet but it is not very practical.

There is also a similar post on this forum but no answer was given :  https://bitcointalk.org/index.php?topic=174091.0


I can do a cgminer -n dump if needed !


I hope someone can help me through this problem.


Tamis

I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card?  This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.

[energywave]

I would recompile and remove FPGA code, if I were you.

Ok, thank you for the hint, I have to learn what I need to compile CGMINER. That can be instructive so I'll try.
Thank you for poining me at libusb, I didn't note that.

[Tamis]

I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card?  This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.

I should have said that my AMD card has a hdmi to vga adaptater connected. Those work as dummy plug no ?

[Zanatos666]

I dont know if this would work, but what about getting/making a dummy plug for your AMD card, and in your configuration in CGMiner, disabling the GPU number that corresponds to your Nvidia card?  This way CGMiner shouldnt try and use it, and the dummy plug will make your system think your AMD card is plugged into a monitor.

I should have said that my AMD card has a hdmi to vga adaptater connected. Those work as dummy plug no ?

Could not tell you.  I know when I had my 5870 running on Windows before switching to BAMT, I didnt need dummy plugs, the drivers worked just fine with it.  Maybe try scaling back your drivers to something older in the 11.x or 12.x, getting rid of the connect on you 5870 altogether, and seeing what results that yields.

[pirate1]

Ok, I have a noob question.  I am running a BitForce Single (FPGA), and two 6870 graphics cards mining Bitcoins.  I have been using cgminer-2.10.5.  It has been working fine.  However, I am getting ready to receive my new BitForce Single (ASIC) and updating in preparation.  When I try to use cgminer-3.2.1 I get the following message:

[2013-06-10 16:26:47] Started cgminer 3.2.1
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - CMR device 2:1
[2013-06-10 16:26:47] Icarus detect (2:1) failed to initialise (incorrect device?)
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - BAS device 2:1
[2013-06-10 16:26:47] BitForceSC detect (2:1) failed to initialise (incorrect device?)
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - BFL device 2:1
[2013-06-10 16:26:47] BitForce detect (2:1) failed to initialise (incorrect device?)

I can still use cgminer-2.10.5 with no problem.  I don't understand what I need to do or why one version works but not the other.  I do not know where to look for or how to install the drivers.  I have the latest updates.  As I said, a noob question, but I still don't understand what I need to do.  I know it is probably something simple and straightforward but I would appreciate some help.

[Zanatos666]

Ok, I have a noob question.  I am running a BitForce Single (FPGA), and two 6870 graphics cards mining Bitcoins.  I have been using cgminer-2.10.5.  It has been working fine.  However, I am getting ready to receive my new BitForce Single (ASIC) and updating in preparation.  When I try to use cgminer-3.2.1 I get the following message:

[2013-06-10 16:26:47] Started cgminer 3.2.1
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - CMR device 2:1
[2013-06-10 16:26:47] Icarus detect (2:1) failed to initialise (incorrect device?)
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - BAS device 2:1
[2013-06-10 16:26:47] BitForceSC detect (2:1) failed to initialise (incorrect device?)
[2013-06-10 16:26:47] USB init, open device failed, err -12, you need to install
a Windows USB driver for - BFL device 2:1
[2013-06-10 16:26:47] BitForce detect (2:1) failed to initialise (incorrect device?)

I can still use cgminer-2.10.5 with no problem.  I don't understand what I need to do or why one version works but not the other.  I do not know where to look for or how to install the drivers.  I have the latest updates.  As I said, a noob question, but I still don't understand what I need to do.  I know it is probably something simple and straightforward but I would appreciate some help.

Have you tried downloading the USB driver from BFL's website?

[freshzive]

I'm running cgminer3.1.1 with 7 USB Block Erupters (Ubuntu 12.04 x64). I am seeing an abnormally high amount of rejects (~10%), see screenshot. I thought this might be pool specific, but I've tried 3 pools now and it seems consistent across all of them. The rejects come in big chunks, suddenly I'll get a run of 20+. They are generally "stale work" or some other similar error.

Is there something I can do to fix this?

I tried updating to 3.2.1m but it seems my USB3 hub doesn't work well with the new version, so I had to downgrade. I guess I may just have to get a new hub and use the new version?

[atomicchaos]

I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"

I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.

It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!

[-ck]

I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"

I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.

It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!

This is intentional and advantageous for solo miners.

[pirate1]

Zanatos, I did download from the BFL site.  I didn't understand how to install it but I checked versions and it is the same version I have installed.  Cgminer-2.10.5 is working fine so I don't understand why the new one is not working for me.

[-ck]

Zanatos, I did download from the BFL site.  I didn't understand how to install it but I checked versions and it is the same version I have installed.  Cgminer-2.10.5 is working fine so I don't understand why the new one is not working for me.

Read the readme THAT COMES WITH THE VERSION YOU HAVE.

It clearly says when you're starting that it needs a WinUSB driver, but you have the FTDI driver installed.

[atomicchaos]

I am solo mining LTC on my rigs, and have them pointing to a wallet on my LAN. When I added a failover pool (Coinotron), it picks up updates from that pool, and all new blocks come across as: "Stratum from Pool 1 Detected New Block" Instead of the expected solo: "New Block Detected"

I also get "Stratum Connection to Pool 1 Interrupted" and "Pool 1 Difficulty Changed to xxx" messages frequently.

It doesn't appear to impact me as I still find my solo blocks, but I'm wondering if I need to change back to just solo with no failover, so it doesn't keep wandering over to my failover pool to see what is going on there. Is this normal behavior? Does it take away any performance by checking both my local wallet and the pool? Thanks in advance for any advice!

This is intentional and advantageous for solo miners.

Thank you very much for the confirmation. I believe from what I read Stratum is much more dependable and makes sure that you are on the correct block and in sync with the chain. I wanted to make sure that it wasn't degrading anything by watching the pool info at the same time it solo mines. I assume if I removed the Stratum from the failover it would test if there was any degradation, I just didn't experiment. I greatly appreciate you answering my question.

[CommanderVenus]

I think you might already know about this issue but anyway..

I am using the Raspberry Pi and i got cgminer 3.2.1 working perfectly with one Block Erupter on my hub. Giving amazing results even, less than 1% HW issues.

I have been trying to run the same setup but with 4 block erupters and i keep getting issues. The block erupters keep being announced as SICK because they wont start, and if i happen to get all four to start somehow, they are running at a fraction of the hashrate they should be.

Im using the same hub and 4 block erupters but with cgminer 3.1.1 on windows 7 32 bit and they are going to town, hashing with no issues. So my hub and block erupters are playing nicely together.

Has anyone successfully gotten cgminer working with multiple block erupters on their raspberry pi yet?

[GoldBit89]

How do i set up to lower my discarded work due to a new block?

Also is there a way to increase my shares above target and decreasing

my shares below target?

here is a partial log report just completed for about 6 and a half

hours:

[10/06/2013 12:42:28 PM] Share below target
 [10/06/2013 12:42:33 PM] Share below target
 [10/06/2013 12:43:17 PM] Share below target
 [10/06/2013 12:43:24 PM] Share below target
 [10/06/2013 12:43:25 PM] New block: 9c769647a18857de... diff 41.8M
 [10/06/2013 12:43:25 PM] Stratum from pool 0 detected new block
 [10/06/2013 12:43:26 PM] Share below target
 [10/06/2013 12:43:31 PM] Share below target
 [10/06/2013 12:43:41 PM] Share below target
 [10/06/2013 12:43:51 PM] Share below target
 [10/06/2013 12:44:12 PM] Share below target
 [10/06/2013 12:44:25 PM] New block: 168ef66e83963534... diff 41.8M
 [10/06/2013 12:44:25 PM] Stratum from pool 0 detected new block
 [10/06/2013 12:44:27 PM] (120s):4.352K (avg):4.350Kh/s | A:25  R:0 

HW:0  U:0.1/m  WU:4.1/m

 [10/06/2013 01:07:32 PM] Started at [10/06/2013 06:35:54 AM]
 [10/06/2013 01:07:32 PM] Pool: stratum+tcp://ltc.allpoolz.com:8080
 [10/06/2013 01:07:32 PM] Runtime: 6 hrs : 31 mins : 37 secs
 [10/06/2013 01:07:32 PM] Average hashrate: 4.4 Kilohash/s
 [10/06/2013 01:07:32 PM] Solved blocks: 0
 [10/06/2013 01:07:32 PM] Best share difficulty: 6.32K
 [10/06/2013 01:07:32 PM] Share submissions: 25
 [10/06/2013 01:07:32 PM] Accepted shares: 25
 [10/06/2013 01:07:32 PM] Rejected shares: 0
 [10/06/2013 01:07:32 PM] Accepted difficulty shares: 1600
 [10/06/2013 01:07:32 PM] Rejected difficulty shares: 0
 [10/06/2013 01:07:32 PM] Reject ratio: 0.0%
 [10/06/2013 01:07:32 PM] Hardware errors: 0
 [10/06/2013 01:07:32 PM] Utility (accepted shares / min): 0.06/min
 [10/06/2013 01:07:32 PM] Work Utility (diff1 shares solved / min):

4.11/min
                                     920 discarded due to new work

requests
 [10/06/2013 01:07:32 PM] Stale submissions discarded due to new

blocks:

0
 [10/06/2013 01:07:32 PM] Unable to get work from server occasions: 0
 [10/06/2013 01:07:32 PM] Work items generated locally: 1555
 [10/06/2013 01:07:32 PM] Submitting work remotely delay occasions: 0
 [10/06/2013 01:07:32 PM] New blocks detected on network: 142

Current Settings:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

"C:\Users\xxxxx\Desktop\guiminer-

scrypt_win32_binaries_v0.04\cgminer\cgminer-3.1.1-windows

\cgminer.exe" --scrypt -u xxxxx -p xxxxxx -o stratum

+tcp://ltc.allpoolz.com:8080 2>logfile.txt 3>sharesfound.txt --gpu-

platform 0 -d 0 -w 128 -v 1 -I 9 -g 1 -l 1 --shaders 1500 --thread-

concurrency 4064 --lookup-gap 2


as you can see 1600 accepted shares but only 25 of 64 difficulty

along with 920 that were being worked on when a new block was found

and was discarded.Whats even more disturbing is that only 142 new

blocks detected on network but yet 920 possible shares were

discarded.

Any suggestions on how i can improve upon this "Without" new

hardware?

[pirate1]

ckolivas, thank you.  I used the zadig utility and changed the drivers and now the new version is running fine.  I thought it was something simple I was overlooking and it was.  I was missing the obvious and was stuck so I really appreciate the answer you gave.  I expect to be receiving my new ASIC single from BFL this week so I wanted to have the latest version.  Now I do, once again thank you

[HellDiverUK]

I'm experiencing a very odd and blocking problem: was mining with CGMINER 3.1.0 on Radeon HD 5750, never had problem, with SHA256 nor Scrypt, all was fine.
At some point I tried CGMINER 3.2.0 and it crashed at start (could only see one line "Started CGMINER 3.2.0" and then crashed).
The odd thing is that from that point over even all other versions of CGMINER do the same!!! I cannot anymore use CGMINER! I've tried with 3.1.1 (that I'm succesfully using on another PC): crash. 3.1.0 that was working well before: crash. Today I tried even 3.2.1: crash.
I did a Dr. Mingw debug for you, hoping to understand what the hell is happening.

Code:

cgminer.exe caused an Access Violation at location 004312d2 in module cgminer.exe Reading from location 072ff1d3.

Registers:
eax=76709102 ebx=0445fd14 ecx=00000000 edx=00000000 esi=0445fc80 edi=00000000
eip=772de1a4 esp=0445fb58 ebp=0445fcd8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

Call stack:
772DE1A4  ntdll.dll:772DE1A4  ZwWaitForMultipleObjects
76AE6AEB  KERNEL32.DLL:76AE6AEB  WaitForMultipleObjects
0045A362  cgminer.exe:0045A362
0045ACD7  cgminer.exe:0045ACD7
Registers:
eax=00000000 ebx=7fffffff ecx=00000000 edx=00000000 esi=ffffffff edi=0097c6d8
eip=772ddc34 esp=04d5f998 ebp=04d5f9d8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

Call stack:
772DDC34  ntdll.dll:772DDC34  NtWaitForSingleObject
71F78599  mswsock.dll:71F78599  Tcpip4_WSHGetWildcardSockaddr
75140CCF  WS2_32.dll:75140CCF  select
0041C6B8  cgminer.exe:0041C6B8  socket_full  util.c:1057
0041C6FD  cgminer.exe:0041C6FD  sock_full  util.c:1069
0040F6B0  cgminer.exe:0040F6B0  stratum_rthread  cgminer.c:4962
00459F25  cgminer.exe:00459F25
7670906A  msvcrt.dll:7670906A  _ui64tow
76709147  msvcrt.dll:76709147  iswalnum
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain
XXXXXXXXXXXXXXXXXXXXXX
Registers:
eax=072ff1cf ebx=02008668 ecx=ffb8e50d edx=00000008 esi=01ff2e68 edi=02007c6a
eip=004312d2 esp=0028f4e0 ebp=0028f548 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Call stack:
004312D2  cgminer.exe:004312D2  patch_opcodes  ocl.c:178
004333EF  cgminer.exe:004333EF  initCl  ocl.c:738
00430218  cgminer.exe:00430218  opencl_thread_prepare  driver-opencl.c:1332
00419410  cgminer.exe:00419410  main  cgminer.c:7691
004010B9  cgminer.exe:004010B9  __mingw_CRTStartup  crt1.c:244
00401284  cgminer.exe:00401284  WinMainCRTStartup  crt1.c:274
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain
Registers:
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000002 edi=0097afe0
eip=772df6b4 esp=048dfdec ebp=048dff84 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

Call stack:
772DF6B4  ntdll.dll:772DF6B4  ZwWaitForWorkViaWorkerFactory
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain
Registers:
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=0469fe6c edi=00001cb4
eip=772ddc34 esp=0469fe28 ebp=0469fe90 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206

Call stack:
772DDC34  ntdll.dll:772DDC34  NtWaitForSingleObject
753A10B4  KERNELBASE.dll:753A10B4  WaitForSingleObject
0FB90B1B  amdocl.dll:0FB90B1B  clGetSamplerInfo
0FB872A7  amdocl.dll:0FB872A7  clGetSamplerInfo
0FB87456  amdocl.dll:0FB87456  clGetSamplerInfo
0FB84362  amdocl.dll:0FB84362  clGetSamplerInfo
0FB96FD6  amdocl.dll:0FB96FD6  clGetSamplerInfo
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain
Registers:
eax=00000000 ebx=04b1f8a4 ecx=00000000 edx=00000000 esi=04b1f810 edi=00000000
eip=772de1a4 esp=04b1f6e8 ebp=04b1f868 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206

Call stack:
772DE1A4  ntdll.dll:772DE1A4  ZwWaitForMultipleObjects
76AE6AEB  KERNEL32.DLL:76AE6AEB  WaitForMultipleObjects
0045A362  cgminer.exe:0045A362
0045ACD7  cgminer.exe:0045ACD7
753AEE71  KERNELBASE.dll:753AEE71  CreateEventExW
753AEE8C  KERNELBASE.dll:753AEE8C  CreateEventExW
753B3BFE  KERNELBASE.dll:753B3BFE  CreateEventExA
00458630  cgminer.exe:00458630
0041BD00  cgminer.exe:0041BD00  tq_pop  util.c:769
0040F9D0  cgminer.exe:0040F9D0  stratum_sthread  cgminer.c:5053
00459F25  cgminer.exe:00459F25
7670906A  msvcrt.dll:7670906A  _ui64tow
76709147  msvcrt.dll:76709147  iswalnum
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain
Registers:
eax=76709102 ebx=6b619070 ecx=00000000 edx=00000000 esi=029afe90 edi=00000000
eip=772de1a4 esp=029afd68 ebp=029afee8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

Call stack:
772DE1A4  ntdll.dll:772DE1A4  ZwWaitForMultipleObjects
76AE6AEB  KERNEL32.DLL:76AE6AEB  WaitForMultipleObjects
6B608229  libusb-1.0.dll:6B608229  windows_clock_gettime_threaded
76709147  msvcrt.dll:76709147  iswalnum
76AE8543  KERNEL32.DLL:76AE8543  BaseThreadInitThunk
7730BF39  ntdll.dll:7730BF39  RtlInitializeExceptionChain
7730BF0C  ntdll.dll:7730BF0C  RtlInitializeExceptionChain

I hope that someone can lead me to the solution.... I'm now using bitminter java client, but I want a scrypt miner and I like so much CGMINER...!
Thank you in advance to who will reply!

Had the same problem, even with fresh install of Windows.  Fresh install, installed 12.8 drivers, crash.  Another fresh install, 13.4 drivers, crash.  Another fresh install, 12.8 drivers, SDK, crash.  

Seems GPU mining is ignored now, developer is like a bitch in heat over USB mining bollocks.

Gave up with not getting any answers on here, tried latest BFGMiner with 13.4 and it's working no problems.    

[-ck]

Had the same problem, even with fresh install of Windows.  Fresh install, installed 12.8 drivers, crash.  Another fresh install, 13.4 drivers, crash.  Another fresh install, 12.8 drivers, SDK, crash.  

Seems GPU mining is ignored now, developer is like a bitch in heat over USB mining bollocks.

Gave up with not getting any answers on here, tried latest BFGMiner with 13.4 and it's working no problems.    

Thanks.

P.S. Try disabling USB hotplug if you're not using USB devices --hotplug 0