Close
Showing results 1 to 8 of 8
  1. #1

    Default More than 2 instances of Wow

    I have tried searching the forum's to no avail, maybe I'm just in overload mode. Anyways I am trying to get 5 box's 1 pc up and running and can't seem to get past the first two. I will be the first to admit that my pc is outdated however before I upgrade the pc and buy 4 more copies of wow I wanted to go the trial route first. My question is am I required to have multiple copies of wow directories/exe's? I ask because I crash on the third copy while logging into the game, I even went out and bought a updated video card hoping it was jsut my old 7800gt. I would imagine I should be able to run 5 copies of wow albeit slowly on a computer that is less than 5 years old especially since I have no slowdown at all at 2 copies.

    My current specs:

    Winxp Pro 32:
    2.0ghz x2 processor
    4gig ram
    9800gtx
    Rest doesnt really matter its old, built it myself.

    Thank you for your time,
    -Ryan

    p.s. everything I've been reading leads me to believe my system is just junk for anything more than 2 boxing
    Last edited by Friedpickles : 10-16-2009 at 07:15 PM

  2. #2

    Default

    Quote Originally Posted by Friedpickles View Post
    I have tried searching the forum's to no avail, maybe I'm just in overload mode. Anyways I am trying to get 5 box's 1 pc up and running and can't seem to get past the first two. I will be the first to admit that my pc is outdated however before I upgrade the pc and buy 4 more copies of wow I wanted to go the trial route first. My question is am I required to have multiple copies of wow directories/exe's? I ask because I crash on the third copy while logging into the game, I even went out and bought a updated video card hoping it was jsut my old 7800gt. I would imagine I should be able to run 5 copies of wow albeit slowly on a computer that is less than 5 years old especially since I have no slowdown at all at 2 copies.

    My current specs:

    Winxp Pro 32:
    2.0ghz x2 processor
    4gig ram
    9800gtx
    Rest doesnt really matter its old, built it myself.

    Thank you for your time,
    -Ryan
    You should be able to open up 5 copies of WoW without issue, or at least without error messages. Try to open them up without logging in on any of them, because logging into the same account on more than one instance of WoW will kick the first instance offline. See if all 5 actual open just by running wow.exe 5 times.

    If so, cool, you'll be able to do it. Try it with trial accounts then, setup 4 trials, login on the first WoW with your actual account, then the 4 trials on the 4 other WoW's. Go from there!

    If you're getting an actual error message, let us know what it says and if it's actually generated in-game, or if it's a Windows error with the "Send" and "Don't Send" buttons and such.

    Cheers
    Elune (Alliance, 80 Druids): Forestoe, Foresty, Forestay, Forestae, Forestao
    Dethecus (Horde): Lightwield, Grounder, Pyric, Flay, Grown

  3. #3

    Default

    Quote Originally Posted by Psych View Post
    You should be able to open up 5 copies of WoW without issue, or at least without error messages. Try to open them up without logging in on any of them, because logging into the same account on more than one instance of WoW will kick the first instance offline. See if all 5 actual open just by running wow.exe 5 times.

    If so, cool, you'll be able to do it. Try it with trial accounts then, setup 4 trials, login on the first WoW with your actual account, then the 4 trials on the 4 other WoW's. Go from there!

    If you're getting an actual error message, let us know what it says and if it's actually generated in-game, or if it's a Windows error with the "Send" and "Don't Send" buttons and such.

    Cheers
    ERROR #132 (0x85100084) Fatal Exception
    Program: C:\Program Files\World of Warcraft\WoW.exe
    Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:007D03C8

    The instruction at "0x007D03C8" referenced memory at "0x00000004".
    The memory could not be "read".

    ----
    Yea i have the trials set up so now i feel like im on a deadline or something lol. I have the RAF setup I just cant login more than 2 toons at the same time. I can for example get all 5 logged into their character screens but more than 2 instances of the actual worldserver up and running and it crashes.

    Last edited by Friedpickles : 10-16-2009 at 07:28 PM

  4. #4

    Default

    Quote Originally Posted by Friedpickles View Post
    ERROR #132 (0x85100084) Fatal Exception
    Program: C:\Program Files\World of Warcraft\WoW.exe
    Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:007D03C8

    The instruction at "0x007D03C8" referenced memory at "0x00000004".
    The memory could not be "read".

    ----
    Yea i have the trials set up so now i feel like im on a deadline or something lol. I have the RAF setup I just cant login more than 2 toons at the same time. I can for example get all 5 logged into their character screens but more than 2 instances of the actual worldserver up and running and it crashes.

    I've had error 132 before on two different machines, and it had two different causes. On one machine, it was heat related (and crappy motherboard related), something on my motherboard was heating up too much and I'd get a full crash and that error. The other one, more recently, was on my wife's computer. She had a stick of RAM go bad on her, and would consistently but randomly get this error.

    So if there's two causes, there's probably more...ugh...

    To rule out heat and overtaxing of things, try closing off all your WoW's, logging in one session and go into the options. Turn evvvvvvverything down to minimum. Like lowest graphics quality, no sound, no AA, low low low. Save that, quit the game fully to ensure the config.wtf is created with the new settings. Then try firing up two WoW's, logging both in, if all is well, try a third. Go baby steps.

    If that works then perhaps it's just a load issue or heat or something, it probably is less likely to be bad memory at least. If it happens then too, perhaps running a memory checker is in order.
    Elune (Alliance, 80 Druids): Forestoe, Foresty, Forestay, Forestae, Forestao
    Dethecus (Horde): Lightwield, Grounder, Pyric, Flay, Grown

  5. #5

    Default

    Quote Originally Posted by Psych View Post
    I've had error 132 before on two different machines, and it had two different causes. On one machine, it was heat related (and crappy motherboard related), something on my motherboard was heating up too much and I'd get a full crash and that error. The other one, more recently, was on my wife's computer. She had a stick of RAM go bad on her, and would consistently but randomly get this error.

    So if there's two causes, there's probably more...ugh...

    To rule out heat and overtaxing of things, try closing off all your WoW's, logging in one session and go into the options. Turn evvvvvvverything down to minimum. Like lowest graphics quality, no sound, no AA, low low low. Save that, quit the game fully to ensure the config.wtf is created with the new settings. Then try firing up two WoW's, logging both in, if all is well, try a third. Go baby steps.

    If that works then perhaps it's just a load issue or heat or something, it probably is less likely to be bad memory at least. If it happens then too, perhaps running a memory checker is in order.
    Thank you for the advice, I'm willing to bet it might be heat/mobo related but will run a memory checker at a later point. Worse case scenario newegg.com has plenty to sell me I guess :-)

  6. #6

    Default

    Quote Originally Posted by Friedpickles View Post
    Thank you for the advice, I'm willing to bet it might be heat/mobo related but will run a memory checker at a later point. Worse case scenario newegg.com has plenty to sell me I guess :-)
    Sometimes you just need these little pushes to get on the upgrade bandwagon
    Elune (Alliance, 80 Druids): Forestoe, Foresty, Forestay, Forestae, Forestao
    Dethecus (Horde): Lightwield, Grounder, Pyric, Flay, Grown

  7. #7

    Default

    Maybe yer comp is harboring lots of dust bunnies? clear em out :P

    barring bad memory another thing that'll help is to disable as many system services as you can this will free up some cpu cycles.

    another thing is to go start-controll panel- system and click advanced tab click on setting for performance and set it to "adjust for best performance" makes the gui look ugly but it'll help some.

  8. #8
    Member
    Join Date
    Jan 2008
    Location
    Southen California
    Posts
    329

    Default

    I had this error once as well and called up Blizzard. They recommended repairing the install. Check the wow directory for the "Repair" application.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •