• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • "Fatal Error" and WoW crashing

    Discussion in 'Honorbuddy Support' started by JJDun799, Sep 21, 2012.

    Thread Status:
    Not open for further replies.
    1. JJDun799

      JJDun799 New Member

      Joined:
      Feb 3, 2012
      Messages:
      17
      Likes Received:
      0
      Trophy Points:
      0
      Every time that I start WoW, and then attempt to start the bot, I get two error windows and the game force-closes on me. I have already?
      -Downloaded both everything from the original download folder and checked my system with the program that...checks your system.
      -Altered the setting to run in 32-bit version
      -Run both programs as admin
      -Read all other posts I could find.
      -Restarted my computer (for the lolz)

      The following two excerpts are the error messages I get, followed by my log. The first one is there in its? entirety, while the second is the first fragment of a long wall of code. Thanks for the help.

      //First window that pops up//

      This application has encountered a critical error:
      ERROR # 132 (0x85100084) Fatal exception!
      Program C:/Program Files (x86)/World of Warcraft/Wow.exe
      ProcessID: 5212
      Exception: 0x0000005 (ACCESS_VIOLATION) at 0023:74201CE5
      The instruction at ?0x74201CE5? referenced memory at ?0x460936F5?.
      The memory could not be ?written?.
      Press OK to terminate the application.

      //Second window that appears//

      World of WarCraft: Retail Build (build 16057)
      Exe: C:\Program Files (x86)\World of Warcraft\WoW.exe
      Time: Sep 20, 2012 11:26:43.527 PM
      User: Jeffrey
      Computer: JEFFREY-PC
      ------------------------------------------------------------------------------
      This application has encountered a critical error:
      ERROR #132 (0x85100084) Fatal exception!
      Program: C:\Program Files (x86)\World of Warcraft\WoW.exe
      ProcessID: 5252
      Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:74201CE5
      The instruction at "0x74201CE5" referenced memory at "0x46123515".
      The memory could not be "written".

      Log File:
      View attachment 4476 2012-09-20 23.26.txt
       
    2. Makkli

      Makkli New Member

      Joined:
      Jun 27, 2012
      Messages:
      481
      Likes Received:
      20
      Trophy Points:
      0
      Are you logged in to a character before starting HB? And are you starting the game with wow.exe and not the launcher? Running WoW in windowed mode?
       
    3. JJDun799

      JJDun799 New Member

      Joined:
      Feb 3, 2012
      Messages:
      17
      Likes Received:
      0
      Trophy Points:
      0
      1. I am entirely logged into WoW before I start HB
      2. I am starting the game through the launcher, but run it as admin and go to the game preference setting to change it to 32 bit when I do
      3. Yes I am running it in windows mode
       
    4. Makkli

      Makkli New Member

      Joined:
      Jun 27, 2012
      Messages:
      481
      Likes Received:
      20
      Trophy Points:
      0
      Use wow.exe to start the game.
       
    5. JJDun799

      JJDun799 New Member

      Joined:
      Feb 3, 2012
      Messages:
      17
      Likes Received:
      0
      Trophy Points:
      0
      I opened it with the .exe version, and the error just happened in the same way

      Correct me if I am wrong, but you go into your WoW folder in your C drive and open the WoW one that has the .exe suffix, correct? I am doing that right I hope...
       
      Last edited: Sep 21, 2012
    6. Makkli

      Makkli New Member

      Joined:
      Jun 27, 2012
      Messages:
      481
      Likes Received:
      20
      Trophy Points:
      0
      Then I'm afraid I'm out of ideas and you'll have to wait for Tony or someone more capable.
       
    7. JJDun799

      JJDun799 New Member

      Joined:
      Feb 3, 2012
      Messages:
      17
      Likes Received:
      0
      Trophy Points:
      0
      Thank you for trying :)
       
    8. JJDun799

      JJDun799 New Member

      Joined:
      Feb 3, 2012
      Messages:
      17
      Likes Received:
      0
      Trophy Points:
      0
      I have solved the problem. Dx11 instead of Dx9 was on. Sorry for any trouble. Permission to lock the thread.
       
    9. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      Great!

      thread closed
       
    Thread Status:
    Not open for further replies.

    Share This Page