What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Sending blizzard an error code upon D3 crashing.

Status
Not open for further replies.
J

james000

New Member
Joined
Feb 13, 2013
Messages
26
Reaction score
0
Iya. Woke up this morning to a d3 error screen in my face. An error report screen in my face with only 2 options on it. "Re-open" or "Close". The re-open button reloads D3. I'll take a SS next time but I'm guessing most of you have seen these before. In the same popup there is an error code that has been generated, i'm guessing it has botting information within it which helped cause the crash that will be send to blizzard. Does clicking close send the report? As there is no "send" button.

Bit concerned!

james
 
I had it before....


I always close it of course, but in all opinion I don't think it will have any botting info in it, as by law there not allowed to scan your PC so... either way i think nothing will happen, but I always close it anyway.
 
had that error box a few times on honour and demon all ok so far.
 
Josh buddy, sorry to be such a noob but would really appreciate if you would share a quick method to execute the above

James
 
Ctrl+Alt+Delete
Then go to Task Manager.
Under processes you will see something called agent32 or something like that.
Click on it and end it. That's Blizzard's error reporting service.

If your game crashes it will simply freeze instead of that error report popping up!
Whenever you load DB and D3 make sure you do this. YAR will do it automatically but I can't run YAR with my PC so I do it manually.
 
Start task manager and agent.exe is probably the first process listed, it sends info back to blizzard. Open file location and open one of those files in the folder so you can get the correct path, it'll be something like C:\ProgramData\Battle.net\Agent\Agent.1637\Agent.exe

Go to your firewall and add an "outbound rule" to the path above that will block agent.exe from sending the information.
 
Paddy said:
Start task manager and agent.exe is probably the first process listed, it sends info back to blizzard. Open file location and open one of those files in the folder so you can get the correct path, it'll be something like C:\ProgramData\Battle.net\Agent\Agent.1637\Agent.exe

Go to your firewall and add an "outbound rule" to the path above that will block agent.exe from sending the information.
Click to expand...

Oh shit dawwwg you just made my life a little easier!!

Both of these suggestions are correct James!
 
Cheers guys, quick info there really appreciate it. Was thinking of getting YAR but was put off by the talk about reloggers contributing to bans.

Again nice one

James
 
Mmm I can see there are some misconceptions on this thread.

Agent.exe is a blizzard updater. Botters have always worried it could send some other information, but nothing was proved. Btw, even if you add an outbound rule for agent.exe, it will create a firewall exception so it can go through. You can check that yourselves, go to program data/agent/"lastagentnumber" and check the Logs folder. Open the agent file with notepad and you'll see the firewall exception created by yourselves.

Blizzarderror.exe and errorreporter.exe are the executables that have to do with sending the crash info to blizz. You can firewall them, they are in 1)your diablo 3 path on the inspector reporter folder, 2) C:\ProgramData\Battle.net\Agent folder.
 
pimpampum said:
Mmm I can see there are some misconceptions on this thread.

Agent.exe is a blizzard updater. Botters have always worried it could send some other information, but nothing was proved. Btw, even if you add an outbound rule for agent.exe, it will create a firewall exception so it can go through. You can check that yourselves, go to program data/agent/"lastagentnumber" and check the Logs folder. Open the agent file with notepad and you'll see the firewall exception created by yourselves.

Blizzarderror.exe and errorreporter.exe are the executables that have to do with sending the crash info to blizz. You can firewall them, they are in 1)your diablo 3 path on the inspector reporter folder, 2) C:\ProgramData\Battle.net\Agent folder.
Click to expand...

Well, the fact that before I started doing this, I could go into the D3 bug/error folder and see every time my game crashed and that report popped up. Now that I end the agent process, that folder has not been updated and nothing about what's running on my pc is going to Blizzard.
 
JoshYoJoshYo said:
Well, the fact that before I started doing this, I could go into the D3 bug/error folder and see every time my game crashed and that report popped up. Now that I end the agent process, that folder has not been updated and nothing about what's running on my pc is going to Blizzard.
Click to expand...

That doesn't make a lot of sense Josh; probably you haven't crashed since. Why? The error report is created no matter that you close agent.exe or not, what firewalling these files would do is avoid that info being sent to Blizz.
 
pimpampum said:
That doesn't make a lot of sense Josh; probably you haven't crashed since. Why? The error report is created no matter that you close agent.exe or not, what firewalling these files would do is avoid that info being sent to Blizz.
Click to expand...

First off, I'm happy to see someone in these threads with a little common sense! :)

Secondly, you are almost completely correct. I have only had the game crash 1 time since the latest DB update. I checked my files and there has not been an update in the error logs. The game froze and the error report system did not open (I believe it is because I end the agent process every D3 startup and that is the only thing I have done differently). I may be incorrect with my assumptions, but with no updates in my error log I am led to believe the agent.exe was the culprit.
 
JoshYoJoshYo said:
The game froze and the error report system did not open (I believe it is because I end the agent process every D3 startup and that is the only thing I have done differently). I may be incorrect with my assumptions, but with no updates in my error log I am led to believe the agent.exe was the culprit.
Click to expand...

I stopped agent.exe to check that out, and I was "lucky" enough to have a crash in less than 5 minutes. The error report showed as usual in its folder, so I think the d3 freezing had to do with the error report not firing up, and it had nothing to do with agent.
 
pimpampum said:
I stopped agent.exe to check that out, and I was "lucky" enough to have a crash in less than 5 minutes. The error report showed as usual in its folder, so I think the d3 freezing had to do with the error report not firing up, and it had nothing to do with agent.
Click to expand...

That makes sense to me. Maybe I'm just lucky? Lol.

Thanks for your input, I'll send you a pm with details if I get a crash again!
 
Please do not worry about this, I have a 5 month old bot that had not taken precautions on crashing profiles / db / etc.

These inspector reports seem to be of no issue.
 
pimpampum said:
Mmm I can see there are some misconceptions on this thread.

Agent.exe is a blizzard updater. Botters have always worried it could send some other information, but nothing was proved. Btw, even if you add an outbound rule for agent.exe, it will create a firewall exception so it can go through. You can check that yourselves, go to program data/agent/"lastagentnumber" and check the Logs folder. Open the agent file with notepad and you'll see the firewall exception created by yourselves.

Blizzarderror.exe and errorreporter.exe are the executables that have to do with sending the crash info to blizz. You can firewall them, they are in 1)your diablo 3 path on the inspector reporter folder, 2) C:\ProgramData\Battle.net\Agent folder.
Click to expand...

Or delete them. I've deleted errorreport folder in all my D3 copies. No problems yet!
 
Status
Not open for further replies.
Back
Top