I really dunno whats going on, cant fix it myself.. Need assistance! ;> Attached log from 3 of my last errors.
Okay, don't really know why you get these errors but you could test it with the newest release. You're using the release before. It should work for now but try the new release.
Wrong. I have got d/cs, lua failures and 132 errors for the past 3 releases of HB. Nothing new. Would ask for a refund but its been to long. Wish it were stable, I can't even AFK for an hour without coming back to errors anymore.
Can you post the wow crash logs as well please. Drewdenman if your having issues create a new thread with the relevant logs attached.
what the guys above said always you must use the latest HB and if you have wow crashes you must post you wow error crash txt
I reported the bug in the Bugtracker website. Didn't know you guys wanted redundant reporting, so I'll put one here as well.
O.O Glad to know I'm not the only one having the "Fatal Error". I hope you get an answer! (because I'm going to steal your answer and use it to solve my problem too >.< and because I feel your pain ofc) HB Log, WoW Crash Log, SS (or it didn't happen! ): View attachment 3-9-2011_12_41 AM 3304 Log.txt // View attachment 2011-03-09 08.04.07 WoW Crash.txt // For those that are freaking out about Access violations, and what they are: 0xC0000005 is the error code designation for an Access Violation... 0x0CB9853D is the arbitrary memory location where the application happened to be running at the time of the crash. AV's can happen for both reading and writing, which is part of the reason that they are so common. Pointers in general are one of the most challenging topics in computer science, which is yet another reason this crash is so commonly seen. In fact, lots of people get wow access violation crashes from things like new hardware, running in emulators like "WINE", and from addons that are buggy. There was one particularly notorious crashing event, that comes to mind when I think of wow AV crashes, where Atlasloot was spiting out more Access Violations than a cranky gumball machine on PCP. So if you're worried about what you might think it's implying in the crash message, don't. Also, disable ALL addons and see if that doesn't solve the problem.
Same thing as the above two! If it matters I am running Windows 7 x86. I already run a memtest86 and my memory is brand new and perfect.
Sorry guys, without WoW crash dumps/reports, we can't really get to the root of the issue. When you post about any form of WoW crash when running HB, make sure you attach a zip with the HB log, the WoW crash text file (.txt) and the .dmp file. (Make sure to replace your character name, realm name, and "GUID" with **** or similar characters. Do not remove the lines entirely!) I'll probably be making a thread within the next hour or so, specifically for users to post their dumps so we have a consolidated place to grab them.
Im glad im not the only one. Mine happens when zoning in or out of bg's. I'll post logs of both later
One thing I found that may have been a potential cause whilst developing my CC, was the CC trying to cast spells whilst the loading screens are in play. I.e zoning into instance whilst in combat, as soon as I put some added checks into my casting procedure the problem disappeared for me.
that sounds promising because I know the few times it crashed while watching it, my bot was still fighting.... Now only if i knew how to add the "checks"
Hey, friend. Try downloading Leatrix Latency Fix : WoW Tools & Utilities : WoWInterface AddOns Worked for me. Report back
