Error #134 - EXC_BAD_ACCESS

Support Technical Support
1

ERROR #134 (0x85100086) KERN_INVALID_ADDRESS at 0x0000000000000089
EXC_BAD_ACCESS

OS: Mac OS X 12.2.1

After updating to TBC 2.5.4.42869, I clicked Enter World on the character screen and saw partial load of the Scryer Bank before my game crashed. In an attempt to troubleshoot I did the following and tried entering world after each step:

  1. Disabled all addons
  2. Moved my Cache, Interface, and WTF folders out of the application directory
  3. Used the “Scan and Repair” option in Battle.net
  4. Went into Game Settings and clicked Reset In-Game Options
  5. Loaded the character screen and set all of the Interface settings to the lowest values (1/10, 1152x720)
  6. Uninstalled and reinstalled the Burning Crusade Classic

Crash logs can be found at pasebin rdyktQMR

EDIT: Was able to successfully create a new character on the same server (Faerlina) and load into the game and play. Seems this issue might be only related to existing characters?

EDIT #2: Trying this: https://us.battle.net/support/en/article/23848?utm_source=internal-TechForum&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=solution

2

Exactly the same error for me. I am running on MacOS 12.3.1.
Only my main characters on one server has this issue. I tried some characters in the old server, or creating a new character, they are all good.
I also tried logging in my another account, and the character on it works well. It’s so odd.

3

Check out this comment: Stillhoof error #134 - #7 by Lannyster-benediction

I haven’t verified this myself yet, but I’m going to try it on a Windows machine ASAP.

4

This one is me as well lol. I just didn’t pick the right toon in the forum.

1 Like
5

Just curious did it resolve your problem?

6

IT DID! Sorry, took me a bit to get over to my buddy’s house and test it out. I had to log into each of my characters on his Windows computer AND log out of each. I logged in on my laptop before logging out of my priest and that one didn’t work until I logged back in on his computer and logged out before logging in on my computer.

7

Hey everyone,

It was suspected the Error 134’s going on with Macs may have been related to the Error 132’s going on with Windows. A hotfix just went out for it that so far looks promising. Should someone be affected by the error 134 crashes and still can’t log in, please open a ticket so a Technical Specialist can take a look.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.