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

Crashing Demonbuddy Error Log from Windows provided.

yogiz

Member
Joined
Jun 11, 2012
Messages
140
Reaction score
0
Hello,

I got the following errors in my Windows logs when Diablo 3 crashs.

Goes Gray Screen. DB is still runing but will not allow me to stop just have to force close both app's


I got these errors all the time.

Running:

AGB tried all different versions same error
3 bots at once

Any other info please ask.

______________________________________________________________
Log Name: Application
Source: .NET Runtime
Date: 7/3/2012 7:47:02 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Mike-PC
Description:
Application: Demonbuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr, Int32, Boolean)
at Zeta.MemoryManagement.ExternalProcessReader.[[Zeta.Internals.Service.BnetService+, Demonbuddy, Version=1.0.648.160, Culture=neutral, PublicKeyToken=null]](IntPtr, Boolean)
at Zeta.Internals.Service.BnetService.()
at Zeta.Internals.Service.BnetService.get_CurrentHero()
at Zeta.CommonBot.Settings.CharacterSettings.Save()
at Zeta.Common.Xml.XmlSettings.Finalize()

Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='.NET Runtime'/><EventID Qualifiers='0'>1026</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2012-07-03T23:47:02.000000000Z'/><EventRecordID>18424</EventRecordID><Channel>Application</Channel><Computer>Mike-PC</Computer><Security/></System><EventData><Data>Application: Demonbuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr, Int32, Boolean)
at Zeta.MemoryManagement.ExternalProcessReader.[[Zeta.Internals.Service.BnetService+, Demonbuddy, Version=1.0.648.160, Culture=neutral, PublicKeyToken=null]](IntPtr, Boolean)
at Zeta.Internals.Service.BnetService.()
at Zeta.Internals.Service.BnetService.get_CurrentHero()
at Zeta.CommonBot.Settings.CharacterSettings.Save()
at Zeta.Common.Xml.XmlSettings.Finalize()
</Data></EventData></Event>
___________________________________________________________________

2nd one:

____________________________________________________________________
Log Name: Application
Source: Application Error
Date: 7/3/2012 7:47:02 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Mike-PC
Description:
Faulting application name: Demonbuddy.exe, version: 1.0.648.160, time stamp: 0x4fec928e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x6f0
Faulting application start time: 0x01cd5966f407679c
Faulting application path: H:\Sexytime\Demonbuddy.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 62a9dc2a-c569-11e1-bd3b-1c6f65d92e71
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-07-03T23:47:02.000000000Z" />
<EventRecordID>18425</EventRecordID>
<Channel>Application</Channel>
<Computer>Mike-PC</Computer>
<Security />
</System>
<EventData>
<Data>Demonbuddy.exe</Data>
<Data>1.0.648.160</Data>
<Data>4fec928e</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17651</Data>
<Data>4e211319</Data>
<Data>e0434352</Data>
<Data>0000b9bc</Data>
<Data>6f0</Data>
<Data>01cd5966f407679c</Data>
<Data>H:\Sexytime\Demonbuddy.exe</Data>
<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
<Data>62a9dc2a-c569-11e1-bd3b-1c6f65d92e71</Data>
</EventData>
</Event>
 
Last edited:
I also used Carguys and Core profiles same issue Tony.
 
update your DB


Thanks for your help Tony,

But I have updated i have used all versions and i always get the same crash in my windows logs.

I have tested different profiles.
No plugin just let the bot to queen over and over still would crash after a few hours with same error in my event logs.

Only thing i have not tried is running the bot off my C:Drive as currently as best practice i have always ran a bot from a USB drive.

Something else must be going on that is either base off my computer or based from the BOT.

There is a lot of others who are reporting same issue in The IRC chat as well on the forms and we have 0 answers on how or why this is.

One answer we did get in IRC was that the way .net is handled has issues and Apoc is had a work around but it still giving issues?

I am just tried of the game crashing and it only happens when i'm AFK, if i watch for 6 hours it does not crash :(.


I have updated .net/Drivers/BIOS/windows/ i have not other ides left other then wipe my SSD and reinstall.
 
Today it has gotten so bad.

Every 15-20 mins i either get a full Diablo 3 crash with error report, or just a gray screen all frozen.
 
[19:11:42.022 N] Demonbuddy v1.0.607.146 started

thats an old version


gimme a fresh log
 
I got Game delay set to 3000 now, with AGB safe Exit and still crashing.

Is this just my issue or others as well now?

Is it hardware on my computer? is it the profile? the bot? drivers? what else can it be?
 
dont use any plugins and also make sure you are on the latest version
 
You still have AGB running as per the logs. the devs will deny support again with any plugin running.

Just for testing, grab a core of arreat profile and run it on a fresh DB 160 folder. Do not run any plugin and let it run for a while. baby sit it for a while to avoid stuck issues and then test if the crash occurs. if it does, attach the log for that run here.
 
Hope that helps, Its hard to tell what logs are what when running 3 bots from the same bot folder.

Some times its only one bot, but usally it makes a chain and go bot down, then another one. But really this is only when im not at home it is so weird.
 
You still have AGB running as per the logs. the devs will deny support again with any plugin running.

Just for testing, grab a core of arreat profile and run it on a fresh DB 160 folder. Do not run any plugin and let it run for a while. baby sit it for a while to avoid stuck issues and then test if the crash occurs. if it does, attach the log for that run here.

Thanks but like i said its the same thing does not matter if its AGB or Carguy or any other profile.

I have posted many different logs for different profiles ranging from Carguys to AGB.

I am about to go spend more money buy a new SSD take out all hardware but GPU/CPU reload that new hard drive and test cuz i think it's either the bot its self not the profile/plugins. or its my hardware.
 
I am more concerned with the Windows Error Log reports then anything else, that shows me somthign might be bad in my windows install and .net
 
I think carguy's profile uses a plugin as well. All sarkoth profiles have to use a plugin for runs.
Core of arreat profiles can run without any plugin.. so if you want to get your issue addressed by the devs, you should test it out with a clean install of DB 160 with a core of arreats profile WITHOUT any plugin enabled/available.
If it crashes in that run post the logs here. That log will actually be helpful for the devs to help you out with your crash issue.

If you feel that a reinstall of Windows and .NET will help then go for it. :)
 
I think carguy's profile uses a plugin as well. All sarkoth profiles have to use a plugin for runs.
Core of arreat profiles can run without any plugin.. so if you want to get your issue addressed by the devs, you should test it out with a clean install of DB 160 with a core of arreats profile WITHOUT any plugin enabled/available.
If it crashes in that run post the logs here. That log will actually be helpful for the devs to help you out with your crash issue.

If you feel that a reinstall of Windows and .NET will help then go for it. :)

I don't think it is the profile at all.

It's one of the following:

1) Running DB from an older USB stick and using the same folder for all three bot's
2) .net issue and coding in DB
3) Windows .dll issues caused by DB
4) I just have bad luck
 
Back
Top