Are these new bounty S&G's by chance?

No just standard turbo HUSNG's

I'm having this same issue and have been for months. It happens to me about once a session on average. Sometimes I'll get lucky and it won't happen for 2-3 days. On 2 different computers with tons of ram and both lots of processing power. I assume it has to be the card catcher doing this. No other programs running except PT4 and CC.

My issue was a little bit different in that I also run TT and don't get a pop up message, but i recently reported a problem 2 times about freezing / crashing client and tables. Before that i reported it a few times last year when i was trying to isolate what was causing the problems. I don't want my tone to come off accusatory, just that this might have been and ongoing issue.

Aside from the visual (I don't get a pop up, everything just freezes) this is EXACTLY what's been happening to me. However, i use HEM2, CC and TT. Either that or it's on Ignition's end. I've heard a lot of people say that they don't use 3rd party software aside from HI and they don't report these issues (that i'm aware of). Just like you this happens 1-2 times per session and sometimes it randomly won't happen for a day or two. This has been happening for me on a windows 7 laptop with 16gb ram, a windows 7 pc with 24gb ram and a new windows 10 pc with 64gb ram. However, this has been occurring since early May of last year.

Yeah been playing tonight and after it happened once tonight I turned off the card catcher and quickly reopened the tables that I was still sitting at and found new ones to sit at.

When I turned CC back on one or 2 of the tables did that white flash flicker thing it does. I realize it only does this when CC is running. Typically that's what happens when the client shuts down. One of the tables flashes white and stays white while the message comes up.

But I have noticed the tables constantly flicker while CC runs.

I've been noticing the white flicker as well.

im not having issues with white flickering but it does freeze/lag for like 5-10 seconds periodically, and i noticed the newest version of the catcher is missing some hands while the somewhat dated version that i was running before updating was working just fine

It's TT related though. TT is injecting into the same space, and if you're running the catcher and TT at the same time, it can cause this issue.

I meant I haven't had any reports of an issue using the catcher and Ignition. We spoke w/ TT owner and talked to him about this. He said he thought it was working ok, and we hadn't had any other reports. This isn't the only forum we're on.

But anytime if you're having a specific issue, then always let us know. We want to take care of anything that's happening that's within our power. We have a lot of people who use the catcher, and I've been doing support long enough to know when there's a coding issue.

If you're running TT and the catcher and still having issues, let me know and I will talk w/ the TT owner again.

It's because you have auto timebank turned on. This doesn't happen on all systems. It depends on your video card. If you're getting it, and it's bothering you just go to settings on the catcher and turn it off.

It doesn't bother me but it seems somehow related to the crashing problem. It's like it flickers occasionally and then one of those times it sticks and one of the tables goes completely white and bam client crashes.

Lag isn't the catcher. The catcher is extremely lean and is just writing a hand. This is either a database issue, or connection issue at ignition. You can isolate this by turning off your database, see how your tables run.

Someone else stated this about missing a hand, but I still don't have any logs or data. We spent several days running 100k+ hands in sims and didn't miss any data. Drivehud runs the same catching process, and no data is missed ever. So I'd love to see this issue, and I think quite possibly something might be happening with the latest update because I have more than one person seeing it, but I need a log from someone. I play, and never see this. I've been looking at my database results and comparing them to what the catcher has logged since someone states this the other week. We've tried to re-produce it countless times.

If you're seeing this, please click on enable advanced logging in settings on the catcher. And if this happens, after your session click on create log and send support that log. I will have a developer look into it.

And just for extra info, are there any 3rd party apps running? There has to be some outlining issue on why no one here can reproduce and typically if there's a consistent problem, we'd hear it from A LOT of people on multiple forums and support. No one wants to miss data, and I hear about every little issue down to fonts on interfaces.

Turn off auto time bank. Your video card doesn't like it. Let me know if you see it anymore after that.

Yeah I'll run today without the time bank and see how that goes.

i just clicked to enable logging and will definitely send you a log the next time i see that it happens. do i just click "create log" once i notice it happen again, and then send it over via support?

i run no other 3rd party software (no TT or otherwise), just HEM 2.0.0.8424 and now ICC v 2.08.0.

Nope tables still flickering white even with Time Bank disabled.

And client just crashed on me an hour in with time bank off. Sigh...

this program works with bodog specifically?
it grabs from bodog and send the hands to my HM2?
the hands will show up in real time in the reports section alongside other hands being played at the same time on sites like stars?
it will then trigger my hm2 hud to display on the tables or is it a unique hud seperate from the hm2 one i use?

**** keeps crashing for me too! FWIW I'm not even running table tamer. I am only running HEM2 latest version (2.0.0.8454), the Ignition Card Catcher, and the Ignition client. This is nuts.

Super tilting when it takes me a while to get my 4 tables up that all have fish and then it crashes and I have to start the process all over again! Also lucky that it hasn't happened while I've been in a big hand.

The link shows only 8.0 "New Ignition Card Catcher update v2.08.0". Nowhere can I see the 8.1 version. But yes I do have that latest 8.0 one as reflected on that link

PS others chiming in on having same issue on the Bovada/Ignition main thread
http://forumserver.twoplustwo.com/28.../index428.html

So just played a session at the micros with no 3rd party software running and it was flawless.

Amazingly today played about 6 hours and only one crash in the very first 5 min.

On a side note I did send in logs to you today Freakdaddy, I am still missing big pots...

Reverted back to version 2.07.6 which had been working just fine for me since it was released all through Jan until I downloaded the latest update. Last Card Catcher version I had was 8.0 which is the latest one listed on the link you provided (http://www.acepokersolutions.com/poker-forum/) and I was experiencing crashes just about every session w/ that one

If I go a couple weeks (10+ sessions, 60+ hours) without a crash now that I reverted back to 2.07.6, I'm almost certain the issue was being caused by the latest update in Card Catcher since I had ~5 crashes in the past ~week since I updated it. If that's the case I will quote this post and update you guys since I think that certainly isolates the issue

Something else is going on w/ your system. The card catcher uses < 30mbs of resources, and has literally nothing to do with screen flashing. It's just writing hands to your hard drive so your database can import them. Try and go back to an earlier version from here. And what other 3rd party tools do you have running?

http://www.acepokersolutions.com/poker-forum/

And just to verify, click on settings in the catcher. Click on create log and send that .zip to support, and we'll be able to see if there's any errors or issues that would cause any kind of crash.

Sure, thanks.

And you're 100% sure you don't have any 3rd party apps running? If I can see your log I'll be able to tell in 10 seconds the cause.

.