What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

WoW.exe crash dumps responsible for banwave??

S

skuld

New Member
Joined
Apr 24, 2011
Messages
21
When Wow.exe crashed, it brings up the a dialog that asks if you want to close the client or re-open the client. Recently I've noticed the tiny little checkbox at the bottom left of the dialog that says something like "Send Data to Blizzard". The checkbox is checked by DEFAULT, so you need to un-check this checkbox before clicking on any buttons. Otherwise I assume that Blizzard gets your crash dump which includes data showing that HB was hooked into at the time of the crash.

I have my theories regarding the banwave, and one of those is that Blizzard was LEGALLY collecting data about HB from various sources in order to flag accounts before the banwave. Collecting crash dumps and flagging accounts that had HB hooked would definitely be a legal way of doing things because the user is opting to send the data to Blizzard by simply not un-checking that little checkbox. It would also be 100% indisputable, hard evidence that you were using HB. Also, from the various threads I've read, one GM also let slip something to the effect that "If HB didn't throw so many errors, they wouldn't have gotten detected." This theory would fit in with what the GM said.

So the question is, how many of you actually had Wow.exe crash and did NOT uncheck the little checkbox? How many of you even noticed it was there at all? I have a feeling that at least once I may not have unchecked that checkbox before closing the dialog, resulting in me sending the crash dump to Blizzard and getting my account flagged.

After HB came back online using HB 788, Wow.exe has crashed a few times. I have been VERY careful to uncheck that checkbox before closing the Wow.exe client. Maybe even safer would be to just terminate the Wow.exe process from the Process Manager just to be safe it doesn't send any data out. So far I have not gotten banned (fingers crossed).
 
skuld said:
When Wow.exe crashed, it brings up the a dialog that asks if you want to close the client or re-open the client. Recently I've noticed the tiny little checkbox at the bottom left of the dialog that says something like "Send Data to Blizzard". The checkbox is checked by DEFAULT, so you need to un-check this checkbox before clicking on any buttons. Otherwise I assume that Blizzard gets your crash dump which includes data showing that HB was hooked into at the time of the crash.

I have my theories regarding the banwave, and one of those is that Blizzard was LEGALLY collecting data about HB from various sources in order to flag accounts before the banwave. Collecting crash dumps and flagging accounts that had HB hooked would definitely be a legal way of doing things because the user is opting to send the data to Blizzard by simply not un-checking that little checkbox. It would also be 100% indisputable, hard evidence that you were using HB. Also, from the various threads I've read, one GM also let slip something to the effect that "If HB didn't throw so many errors, they wouldn't have gotten detected." This theory would fit in with what the GM said.

So the question is, how many of you actually had Wow.exe crash and did NOT uncheck the little checkbox? How many of you even noticed it was there at all? I have a feeling that at least once I may not have unchecked that checkbox before closing the dialog, resulting in me sending the crash dump to Blizzard and getting my account flagged.

After HB came back online using HB 788, Wow.exe has crashed a few times. I have been VERY careful to uncheck that checkbox before closing the Wow.exe client. Maybe even safer would be to just terminate the Wow.exe process from the Process Manager just to be safe it doesn't send any data out. So far I have not gotten banned (fingers crossed).
Click to expand...


How would I go about unchecking that? I botted 6 hours last night grinding dungeons and didnt get banned, although i've never botted before and it was a battlechest account that was played legit on for a bit. I'm doing recruit a friend with my main account, and at night I have it grind dungeons then I grant myself the levels when I wake up.
 
when you get the error report, look in the lower lefthand corner. Untick the radial box.
 
skuld said:
When Wow.exe crashed, it brings up the a dialog that asks if you want to close the client or re-open the client. Recently I've noticed the tiny little checkbox at the bottom left of the dialog that says something like "Send Data to Blizzard". The checkbox is checked by DEFAULT, so you need to un-check this checkbox before clicking on any buttons. Otherwise I assume that Blizzard gets your crash dump which includes data showing that HB was hooked into at the time of the crash..
Click to expand...

It is very unlikely that the bot is present in the dump file itself, as it is a different process than WoW and hence not part of the crash image. However, it might send along a list of running processes and DLL files on your system, but I'm sure you can rule this out as the reason for the majority of users being suspended. Unless you're a beta tester of some program, you should never ever allow sending crash data to any vendor due to privacy reasons.
 
So since i stopped botting I no longer have random disconnects. I wonder if reconnecting to the server gave them info on whether the bot was running.
 
This is very possible. Now that you mention it. I've gotten those errors as well and I don't think I ever unchecked the box.
 
Not only do I untick that box, I also delete the error logs after every session, just in case lol.
 
Most certainly, you want to UNCHECK the "Send to Bliz" box.

It *always* defaults to checked, and we've found no way to make it default to 'unchecked'. Be careful with this.

Leaving the box checked can certainly cause you to be banned for "Unauthorized third-party software" if your account is investigated. However, it is NOT the cause of the recent banwave.

cheers,
chinajade
 
Last edited:
Mario27 said:
where can you find this send to bliz box option ingame ?
Click to expand...

You can't. It's a checkbox that occurs in the dialog box asking you if you want to send crash data to Blizzard if the WoW client crashes.
As being said, you'd never want to do that, not just for WoW but in general. You have no control of what your computer memory holds of other stuff you previously did on your computer.
 
I can delete blizzarderror.exe??

When i delete BlizzardError.exe I dont receive anymore that option of send crash imfo...
 
Last edited:
Hardcore15 said:
I can delete blizzarderror.exe??
When i delete BlizzardError.exe I dont receive anymore that option of send crash imfo...
Click to expand...

Immediately after they were introduced, I systematically blocked all internet traffic on programs like blizzarderror.exe, wowbrowserproxy.exe, systemsurvey.exe etc (scan your system, you will find many copies of them).
And then deleted them.

I still got a ban ...
 
Aetheric said:
Immediately after they were introduced, I systematically blocked all internet traffic on programs like blizzarderror.exe, wowbrowserproxy.exe, systemsurvey.exe etc (scan your system, you will find many copies of them).
And then deleted them.

I still got a ban ...
Click to expand...
Of course you did, seriously, think about it for a minute...

Why would ANY game development studio introduce protection into an application or module that does not require to run for the actual game client to run?

Thats the dumbest thing you could do, as you did you would just block them, done deal, no detection. Start using your brains a little, it does not matter one bit that you block all this crap, the detection is either serverside or in the game client, neither of which you can control.
 
Xarian said:
Of course you did, seriously, think about it for a minute...

Why would ANY game development studio introduce protection into an application or module that does not require to run for the actual game client to run?

Thats the dumbest thing you could do, as you did you would just block them, done deal, no detection. Start using your brains a little, it does not matter one bit that you block all this crap, the detection is either serverside or in the game client, neither of which you can control.
Click to expand...

Well, that was exactly what I was trying to convey ..
For every botter, the ban hammer will come eventually, so I didn't do this to avoid anything, I wanted to rule out certain possibilities and for me that experiment has been very successful.
 
You must log in or register to reply here.
Back
Top