Blizzard Crash Report

[freshjuice]

I'm not sure if this affects the ban system or not but, thought I'd share what I found since I havent seen it here yet.
If or when d2r.exe/jieguan.exe crashes, It registers as such in the report log.
The only way I found to delete this is to delete the whole d2r folder and reinstall.
I believe this is the file that is sent to the blizzard bug report devs. "dxdiag"
Located in "Program files/Diablo II Resurrected"
Open it and scroll all the way to the bottom.
Looks like:

+++ WER9 +++:
Fault bucket 1225837313996507935, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Jieguan.exe <---Should say D2R
P2: 1.2.4104.0
P3: 6286a048
P4: f689
P5: 134217728
P6:
P7:
P8:
P9:
P10:

If your bug report is on auto send for crashes, may want to adjust.
not sure if this actually plays a part in getting banned but seems like an easy way to get caught.

 

[esyouele]

I'm sure sure if this affects the ban system or not but, thought I'd share what I found since I havent seen it here yet.
If or when d2r.exe/jieguan.exe crashes, It registers as such in the report log.
The only way I found to delete this is to delete the whole d2r folder and reinstall.
I believe this is the file that is sent to the blizzard bug report devs. "dxdiag"
Located in "Program files/Diablo II Resurrected"
Open it and scroll all the way to the bottom.
Looks like:

+++ WER9 +++:
Fault bucket 1225837313996507935, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Jieguan.exe <---Should say D2R
P2: 1.2.4104.0
P3: 6286a048
P4: f689
P5: 134217728
P6:
P7:
P8:
P9:
P10:

If your bug report is on auto send for crashes, may want to adjust.
not sure if this actually plays a part in getting banned but seems like an easy way to get caught.

I uncheck send and click "x" everytime.

Seems like an easy thing for blizzard to scan for

 

[freshjuice]

I uncheck send and click "x" everytime.

Seems like an easy thing for blizzard to scan for

It will still register it on that file if the bot was running at the time of crash.

 

[esyouele]

It will still register it on that file if the bot was running at the time of crash.

I checked but I don't see that .exe there - i'll check the next time I get an error notice

 

[SumDumGoy]

I was watching my bot today run and it would crash every 20 or so runs, but the Crash report box did not popup on screen.

However, i followed your directions above and located the DxDiag.txt file and saw the Jieguan.exe in the last few line entries... Does this mean there was a crash report sent already with all this info??
I was just banned recently, and finally got my character back up and running.. hoping it didnt sent off, again, because the bug report box didnt come up when d2r crashed and restarted..

 

[SumDumGoy]

I'm not sure if this affects the ban system or not but, thought I'd share what I found since I havent seen it here yet.
If or when d2r.exe/jieguan.exe crashes, It registers as such in the report log.
The only way I found to delete this is to delete the whole d2r folder and reinstall.
I believe this is the file that is sent to the blizzard bug report devs. "dxdiag"
Located in "Program files/Diablo II Resurrected"
Open it and scroll all the way to the bottom.
Looks like:

+++ WER9 +++:
Fault bucket 1225837313996507935, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Jieguan.exe <---Should say D2R
P2: 1.2.4104.0
P3: 6286a048
P4: f689
P5: 134217728
P6:
P7:
P8:
P9:
P10:

If your bug report is on auto send for crashes, may want to adjust.
not sure if this actually plays a part in getting banned but seems like an easy way to get caught.

are you talking about this?

 

[SumDumGoy]

I think hes talking about this file.. In the Program Files (x86) folder (for me at least...)

 

[mtr_22]

Official Blizzard account banned will look like this:

 

[esyouele]

Official Blizzard account banned will look like this:

View attachment 184

Gives me PSTD seeing that. Lol.

 

[freshjuice]

I was watching my bot today run and it would crash every 20 or so runs, but the Crash report box did not popup on screen.

However, i followed your directions above and located the DxDiag.txt file and saw the Jieguan.exe in the last few line entries... Does this mean there was a crash report sent already with all this info??
I was just banned recently, and finally got my character back up and running.. hoping it didnt sent off, again, because the bug report box didnt come up when d2r crashed and restarted..

The only way to get rid of it is to completely delete/uninstall d2r and reinstall and keep a clean copy of the game in another folder. You can delete the file but it will regenerate with the same info. As far as it being linked to bans, I do not know. Just thought I was would share with everyone here the potential this permanent log file has.

are you talking about this?

Negative, Referring to "dxdiag"

I noticed the log on my file after a crash. I do not report them either.
I delete the whole install of d2r when this happens and use a fresh install which is the only way I have found that gets rid of it.