4075 wow crash
- Thread starter Roflcake
- Start date
I got the same problem using the Horde Leveling Quest Profile (the one thats a sticky for lvl 1 - 60). It happened about lvl 11 or 12. I changed to a grinding/pvp setup and worked fine. Then a few levels later switched back and it worked fine. So its something to do with the profile/behaviors and HB somewhere. I would have posted the log but ya.. stupid me went to copy it. and hit delete (have no clue how but..). And with the security i have, i don't have a recycle bin so.
But there is a conflict somewhere with HB and WoW when using that particular Profile/Quest Behavior files. But it could be just my comp config. I am running 2 other bots along side with no problems, running a variety of bot type mix's (testing out here and there).
Edit: Found the files, was looking in the wrong Logs directory (different HB instance). Here are the 4 logs from when WoW Crashed each time when running the particular HB Build/Profile setup around lvl 12.
But there is a conflict somewhere with HB and WoW when using that particular Profile/Quest Behavior files. But it could be just my comp config. I am running 2 other bots along side with no problems, running a variety of bot type mix's (testing out here and there).
Edit: Found the files, was looking in the wrong Logs directory (different HB instance). Here are the 4 logs from when WoW Crashed each time when running the particular HB Build/Profile setup around lvl 12.
Last edited:
saven
Member
- Joined
- Sep 24, 2010
- Messages
- 275
- Reaction score
- 2
I've done research king..on youtube for Wow #132 crash's, and oh my..there are alot of so called "fix's". The one I thought that was working the longest for me perhapes was the 'Change compaditbility mode to windows SP2' option in the propertys of wow.exe. Plus i've ran my wow in lower settings if that would help. Still testing this puppy out tho.
Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,830
- Reaction score
- 571
[18:24:07:223] [Instancebuddy v3.0.1.220]:No entrance point assigned in dungeon script. Please report to Instancebuddy thread.
saven
Member
- Joined
- Sep 24, 2010
- Messages
- 275
- Reaction score
- 2
It's just odd Tony, that my rogue will most of the time now due to the fix I applyed via change of compatibility mode to win sp 2. I dunno how that helps but I got some good results out of it. Short but sweet question..is it really HB making wow crash? HB? CC's? I would like some expert knoweledge here Tony. Thanks! I know your busy or maybe not but hey - its all good.
Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,830
- Reaction score
- 571
all crashes are not the same
but as an example if you have this line on your log
[11:04:09 PM:489] FS_EMPTY FormatException UNK PRFX @ 0x{0:X}
its Hb that crashing your wow
but this will be fixed on next release
Doesnt seem like its hb that crashes my wow, though i wake up every morning to my wow being crashed/dc'd and its really getting on my nerves =(
Hb doesnt stop, and no error. Just ends with "Not in game.". What could be wrong?
Hb doesnt stop, and no error. Just ends with "Not in game.". What could be wrong?
Is there any workaround or just wait for the next release? I just bought this a few days ago and haven't been able to use it very much yet.
Edit: To be clear I am experiencing crashes immediately upon starting HB and I am seeing that line above in my logs.
I looked into this after reading your post about it a few up and that is deff. not the prob that I am having. I am also getting the #132 error but i am also running a 1000watt power supply in a coolmaster case with 8G of DDR 3 ram. So I am pretty sure its not a cause of the case over heating, There is plenty of memory, and this error isnt showing up when I just play the game and pvp.
I know this is really of no help... and I am glad the SP2 worked for you, just didnt for me QQ