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

D3 crashing in Festering Woods

devious21

devious21

New Member
Joined
Jul 29, 2012
Messages
970
Reaction score
12
D3 crashing due to new DB

Running the new version of DB, Diablo 3 now crashes 100% of the time in festering woods when attempting to use the champion farm profile.

Profile: http://www.thebuddyforum.com/demonb.../act-1/62658-a1-inferno-champion-hunting.html
Plugins:
Giles Stash/Loot replacer - http://www.thebuddyforum.com/demonb...23-plugin-giles-stash-loot-rule-replacer.html
Giles Item Stats - http://www.thebuddyforum.com/demonbuddy-forum/plugins/62419-plugin-giles-item-pickup-stats.html
Giles World Object Handler - http://www.thebuddyforum.com/demonbuddy-forum/plugins/61551-plugin-giles-world-object-handler.html
Giles Monster Priority Changer - http://www.thebuddyforum.com/demonb...50-plugin-giles-monster-priority-changer.html
Ticks Per Second - http://www.thebuddyforum.com/demonbuddy-forum/plugins/63318-ticks-per-second.html (I probably should have disabled this one now that it's an option in DB)

Combat Routine: Belphagor

Log:
View attachment DBlog.txt

There are numerous others complaining of this same issue in the champion farm thread. This error is making it impossible to AFK with the bot, which is highly problematic.
Edit* On my 4th run, it managed to get through festering woods, but then proceeded to crash slightly past sarkoths cellar
 
Last edited:
disable your plugins and try again plz
 
Yes, Diablo 3 simply exits out at a certain point in Festering Woods, even with 0 plugins. Something in there is Diablo 3 itself - but ONLY with the latest DemonBuddy - reverting back to .185, and it works fine again. There doesn't seem to be anything in DemonBuddy log to help - D3 simply quits instantly (no crash on screen, it doesn't stay open and need task-killing - it just closes), and DemonBuddy log simply states that Diablo 3 has exited and so DB exited too.
 
GilesSmith said:
Yes, Diablo 3 simply exits out at a certain point in Festering Woods, even with 0 plugins. Something in there is Diablo 3 itself - but ONLY with the latest DemonBuddy - reverting back to .185, and it works fine again. There doesn't seem to be anything in DemonBuddy log to help - D3 simply quits instantly (no crash on screen, it doesn't stay open and need task-killing - it just closes), and DemonBuddy log simply states that Diablo 3 has exited and so DB exited too.
Click to expand...

I actually made it through festering woods a few times after I made my initial post, but D3 still crashed in the next zone.. (old ruins i think it is?). The furthest I've managed to get in like 6 tries is right past Sarkoths cellar, where D3 proceeded to crash, again.
 
Having the same problem. Haven't made it past festering woods in about 4 runs.
 
ditto....im just hoping that with this many people having issues, it will be looked at, is it possibly a particular "call" from the profile....that is causing the issue, its just almost hard to catch as it isn't 100% reproducible in the SAMe spot...
 
Diablo 3 log (note that this does not happen with previous version of DemonBuddy - and there has been no update to Diablo client) - DemonBuddy is making D3 crash.

Code: 
<ERROR-0>
<no message>
</ERROR-0>

2012.08.03 01:25:18.919041400	UnhandledExceptionFilter
2012.08.03 01:25:18.987911100	Saved dump file to 'C:\Games\Diablo III-3\App-0.dmp'
----------------------------------------------

***** UNHANDLED EXCEPTION: NONCONTINUABLE_EXCEPTION (c0000025)

<STACK-0>
------------
Stack Crawl:
------------
DBG-ADDR<00F18372>("Diablo III.exe")
DBG-ADDR<00F09A28>("Diablo III.exe")
DBG-ADDR<00F0A000>("Diablo III.exe")
DBG-ADDR<008A63EE>("Diablo III.exe")
DBG-ADDR<008A6882>("Diablo III.exe")
DBG-ADDR<008A6F93>("Diablo III.exe")
DBG-ADDR<008A72A9>("Diablo III.exe")
DBG-ADDR<008A7578>("Diablo III.exe")
DBG-ADDR<00923C7A>("Diablo III.exe")
DBG-ADDR<0094FF46>("Diablo III.exe")
DBG-ADDR<00950738>("Diablo III.exe")
DBG-ADDR<00818341>("Diablo III.exe")
DBG-ADDR<0080D9A4>("Diablo III.exe")
13 frames dumped

</STACK-0>
<MODULES-0>

There isn't really anything useful in the log at all :(

It must be something in festering that DemonBuddy is trying to read/interact with/do something with, that the latest DB is doing wrong - some invalid memory pointer? No idea atm.
 
GilesSmith said:
It must be something in festering that DemonBuddy is trying to read/interact with/do something with, that the latest DB is doing wrong - some invalid memory pointer? No idea atm.
Click to expand...

The interesting thing is it isn't only festering... I managed to make it (to my surprise) past festering, check log3 I posted as well as the zipped log. Managed to make it the old ruins before D3 exploded. Not sure what's causing this but i can confirm it's ONLY in the new DB, as i've reverted to .185 and im running with 0 crashes again.
 
devious21 said:
The interesting thing is it isn't only festering... I managed to make it (to my surprise) past festering, check log3 I posted as well as the zipped log. Managed to make it the old ruins before D3 exploded. Not sure what's causing this but i can confirm it's ONLY in the new DB, as i've reverted to .185 and im running with 0 crashes again.
Click to expand...

If you got the new db, how do you get the old one back?
 
I tried to edit the topic title to be more broad (since it's possible to crash in other places than Festering woods), but it didnt work :(.
Oh well, festering woods is still a major crash spot!
 
The problem is likely NOT with festering woods.

I'm using my own custom profile and I have no such error in festering wood whatsoever. Are you guys all using the public champion farming profile? If so I would advise you to revert back to old version of DB/edit festering woods out temporary.

Thousand of bots crashing on the same map, maybe at the same spot is just asking to get flagged... especially if they read this thread.
 
thx for reporting,we will check it asap
 
Can anyone post the whole d3debug.txt from a crash and the .dmp file?
 
And please also upload the .dmp file created by Diablo.
 
You must log in or register to reply here.
Back
Top