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

Bot Keeps crashing

Status
Not open for further replies.
cause your machine might get stressed when using DB

it can be a driver failure as well tho,all your stuff updated?
 
Tony said:
cause your machine might get stressed when using DB

it can be a driver failure as well tho,all your stuff updated?
Click to expand...

I said in the first post that I updated my drivers.
Why would the bot "stress" my pc to crashing yet I can heavily multitask on it just fine? Also to mention running Bot+D3 only uses half my available ram and barely 17% CPU
I got a glimpse of the most recent BSOD, stop code was: 0x0000001e looking into this now but google is all over the place with it..
 
Ran a crash analysis and this came up:
On Thu 12/18/2014 6:32:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121814-23805-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030541E4, 0x0, 0x7FFFFFF0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/18/2014 6:32:29 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sbiedrv.sys (SbieDrv+0xE749)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030541E4, 0x0, 0x7FFFFFF0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Program Files\Sandboxie\SbieDrv.sys
product: Sandboxie
company: tzuk
description: Sandboxie Kernel Mode Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sbiedrv.sys (Sandboxie Kernel Mode Driver, tzuk).
Google query: tzuk KMODE_EXCEPTION_NOT_HANDLED

Looking into solutions now...
 
I uninstalled Sandboxie and the related driver, will run and test bot again. Just to clarify I was NOT botting with sandboxie, and have not used it in years (since D2)
 
Last edited:
Tony said:
game dced?
Click to expand...
Yes the game automatically dc's due to inactivity..
The bot is/was joining games, doing nothing, leaving and remaking, this is my concern not the dc...
View attachment 3452 2014-12-20 04.03.txt
What does this mean:

04:09:06.182 ERROR BotMain Exception during bot tick.
System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.GrabFrame()
at GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
at Zeta.Bot.BotMain.()

Note its the SAME error 4 hours through...

07:56:39.593 ERROR BotMain Exception during bot tick.
System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.GrabFrame()
at GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
at Zeta.Bot.BotMain.()

First and last instance right from log.
 
can you try DB beta build instead plz?
 
Update:
I've noticed that the bot only encounters this issue when I turn off my screens (I dual screen on desktop). Any idea as to why this is the case? It's not linked to a single profile either, just happened in a bounty profile i was running fine for hours, but it messed up right as I turned off my screens.
 
Status
Not open for further replies.
Back
Top