[BGBuddy] Crashing WoW - Error #132 (085100084) Fatal Exception! OK, so...this has been consistently crashing for the last week or so. Whenever I do see it crash it's always after a Battleground has ended and as the bot tries to "Leave Battleground". What is very odd is that I run 5 accounts at the same time, all of them Druids, all of them Singular CC, and only 1 of them crashes...it's always the same one. I have no problems with the other accounts it's just that one account that keeps crashing every time. Incredibly annoying and I am clueless as to why it happens. It makes no sense for only one of them to crash. I'll attach the log if it's of any help. I run 0 addons and while it is not HonorBuddy software that crashes, it is without a doubt causing it. ------------------------------------------------------------------------------ World of WarCraft: Retail Build (build 15595) Exe: C:\Users\Public\Games\World of Warcraft\Wow.exe Time: Jun 5, 2012 12:26:41.079 AM User: <<--------->> Computer: SILVER ------------------------------------------------------------------------------ This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: C:\Users\Public\Games\World of Warcraft\Wow.exe ProcessID: 4116 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00000002 The instruction at "0x00000002" referenced memory at "0x00000002". The memory could not be "executed". ------------------------------------------------------------------------------ I'm unsure if it's always the same error but this is the last one I got.
Run repair.exe from your WoW directory. If that doesn't work, switch the positions of your RAM. If that doesn't work, try some old/different RAM sticks.
No addons, Tony. I was running with TSM the first few times I noticed it and disabled every addon. That was the 2nd day it started crashing and it has crashed easily over 20 times since then. @ Sidalol I ran the repair and it did not fix it :S. I hesitate to open up my laptop and move RAM sticks because I'm not sure the fail is within my hardware since I can and do run other WoW clients at the same time with the same machine and have zero problems...it is only one character in one account that fails and ONLY if I run it with BGBuddy. And secondly: I wouldn't want to get it wrong lol. I will hold on to your suggestion regardless and will try it if I cannot find another solution.
I actually have been getting the same problem. But mine varies on when it crashes. It can vary between playing 2 to 3 games, or crashing when loading into the first BG. I first assumed it was because the loading screen; but today I got one during a battle of IOQ. I do use quite a few addons; so I will give it a shot with all them disabled tonight/this morning and report back to the thread before work tomorrow afternoon. On a side note I have been getting the same access violation on loading screens with GB2 running also. But doing a fresh install seemed to fix that (I hope). Since it hasn't crashed yet. This was my most recent one as of this morning -- ============================================================================== World of WarCraft: Retail Build (build 15595) Exe: D:\World of Warcraft\Wow.exe Time: Jun 22, 2012 5:30:58.293 PM User: r----- Computer: G____-PC ------------------------------------------------------------------------------ This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: D:\World of Warcraft\Wow.exe ProcessID: 4804 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00000000 The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "executed". I have tried running them both in admin; I have all the UAC Disabled also. It would be nice to figure the problem out. Thanks --
About to test that right now Tony, I would stay up and watch it. But I need a little nap. :3 I will post a full log even if it doesn't crash to see if that may shed some light for ya. -- Thanks for the update also. -- Update -- Worked w/o any hiccups.. Must be some problem with addons I use or on Honorbuddy (Probably a WoW Addon). I will try again tonight with all wow Addons disabled. Id like to find out what may be causing it. Thanks for the help Tony.