A new day and new errors.. I haven't whined before, but i must say it's getting quite annoying those bugs/errors everyime. What's the problem that you're having?: HB closes like every 5 min. I have HBRelog so it restarts it self but since the annoying authentication check you then have to manually kill the process(not always) if you dont want to spawn the auth server for 5 min. And Wow crashes every 10 min or so. See the error below. Note:I have reinstalled hb. It worked fine yesterday. I have a laptop just for my bot, so i haven't installed or changed anything on this pc that may be the cause of the error. No custom classes used nor in my hb folder. Windows version?: Windows vista home premium What bot are you having problems with? Quest What profile are you running?: Kicks questing profiles You can find my log and wow error attached below.
Hmm, this is interesting. How much RAM does your laptop have? Is your .NET Framework up to date? (1.4 I believe) Have you tried using other profiles? Specifically shorter ones, Kick's are large profiles. Have you restarted your computer? Have you tried a fresh install of HB?
Hi Dark, thanks for replying. I have 3 gb ram on my laptop with an intel core 2 duo. I have always used this laptop for botting so that cannot be the problem. (Yes after mop aswel) I have reinstalled hb(Fresh) and also restarted my computer. I never had this kind of error/bug before. I haven't tried a different profile, since it worked before. I have the following framework version: <32Bit> 2.0.50727.3074 ->C:\Windows\Microsoft.NET\Framework\v2.0.50727 4.0.30319.1 ->C:\Windows\Microsoft.NET\Framework\v4.0.30319 < Installed .NET Frameworks > .NET FW 2.0 SP 2 .NET FW 3.0 .NET FW 4.0 Client I also have downloaded a tool somewhere on the forums that downloaded the latest version or something? it was a small command line prog I could try version 4.5 ?
I'm pretty sure they discourage downloading the latest Framework instead of the one they suggest, but I could be wrong. Are you using DX9 or 11? 32bit or 64 bit Client? Allowing both WoW and Honorbuddy to run as administrator? Aside from that, more advice would be required from a Developer about this issue.
Something like this normally happens when something else is injected in to the wow process I've had this problem myself before but I just restarted wow and HB and it worked
Okay, i wont download 4.5 . I downloaded the version from the HB instal guide, so i can assume that's the right one. I have a 32 bit system and wow runs in DX9 Wow gives an mem address error, and HB writes and reads to/from addresses, so HB must be causing it? I have noting else installed on this pc and i am not using any program or hack. What about HBRelog?
In his second post he said he reinstalled HB and restarted his computer which would have cleared that up.
http://www.thebuddyforum.com/releases/68254-problems-new-install-buddy-product.html this install is pretty useful to have at all times
If your laptop supports DX11, you should use that. Better FPS anyways. HBRelog, if you have the latest version, does not cause this error. This may seem dumb and generic, but is your bot running as administrator? And if you have any Anti-virus try temporarily disabling that, some Anti-virus will force stop injections.
ChuckLee: That was the tool i was talking about in my earlier post, but i'm not sure if that tool was for c++. I downloaded it and hope it will fix the problem. Dark: My laptop doesn't support that version, haha Well a fair question, since allot of people make that mistake, but i'm 100% sure that wow and hb are started as administrator. I dont have an anti virus since my bottop(laptop) only has wow and HB on it.
I downloaded the tool that ChuckLee posted and i restarted my computer once again. I will see if that helped out. If not i'll try out bg buddy. I have to go to the gym now, so i inform you guys after Thanks allot !
Well guys (?_?) ( ?_?)>⌐■-■ (⌐■_■) It seems to work again! Really strange though, that from one day to another it just magically stopped working. Thanks allot!
thats great, sometimes its just an issue where wow gets loaded into memory that can cause weird issues. etherway glad its working for you.
