ISBoxer and Windows 7 x64

[Lax]

Inner Space and/or the game should have declined to run, and popped up a message box asking you to install it, if the DirectX update was missing. Since you specified that you "installed the dx9c package" I'm unclear on whether you used the DirectX updater (as you linked, which is not actually "directx 9.0c", note that the link says August 2009 and directx 9.0c came out in August 2004), or whether you actually downloaded DirectX 9.0c.

It wouldn't surprise me if running the DirectX updater helped though.

[Xtremepayne]

When I ran the updater which I did try first it said I was up to date and files updated. But then I read his post and ran that link I posted if that helps you in the steps I took.

[Tokae]

Hey All,

I have a WoW user who is running Innerspace and ISBoxer on a Windows 7 pro machine. He has 5 accounts running and periodically it crashes. He gets the memory dump and a 132 error. Is there something perhaps he overlooked when installing it? Im not much of a WoW player and I dont know the inside and outs of this process. I figured his PC was more than adequate spec-wise.. Any help at all would be greatly appreciated!

his pc:

i7 920 @ 2.67 ghz
6 gb mushkin 1333mhz ddr3 ram
nvidia 285 gtx gpu

windows is updated
nvidia drivers are the latest non beta version
even his BIOS is up to date.

Once again any help would be greatly appreciated.. He just wants to play!

[Otlecs]

The most common response to error #132 is to grab a dedicated memory checker (like Memtest86 and run the full suite of tests.

90% of the time it's a slightly flakey chunk of memory, something you'll run into more often with a heavily (memory) loaded system.

In the first instance, run Blizzard's repair utility though. It's in the WoW directory. You don't have to let it reset your macros and bindings - just have it check the consistency of your files.

[Tokae]

The most common response to error #132 is to grab a dedicated memory checker (like Memtest86 and run the full suite of tests.

90% of the time it's a slightly flakey chunk of memory, something you'll run into more often with a heavily (memory) loaded system.

In the first instance, run Blizzard's repair utility though. It's in the WoW directory. You don't have to let it reset your macros and bindings - just have it check the consistency of your files.

Hey Oltecs!

Thanks for the quick response..

I had first thought that he was having memory issues, I downloaded memtest86+ v4 which is a bootable iso for 64 bit systems.. I checked all the sticks individually and found 1 bad stick.. I yanked 3 total (so he has his current 6 gb triple channel setup) and he still is getting the error.. I will get him to run the repair ultility tonight also.. So other than this person's issues, windows 7 64 bit is running this software without any problems?

[Tokae]

Hey guys..

Well I yanked out his old ram and installed 3 new sticks of DDR3 so he has 6 gb in triple channel again.. He went to run the program and it crapped out again, so I am ruling out memory issues... All his software is up to date.. I havent tried the reinstall of directx 9c yet though.. Im just wondering if there is anything else to look at/for?

[moosejaw]

I know this sounds simplistic but I have experienced crashes in wow from having fragmented files. I would first wipe the cache then defrag to fix the issue.
Last week I had a raid drive starting to fail that also caused repeated crashes on just one instance. If running a raid setup check for degredation of any raid volumes.

Edit: I have windows home server that runs nightly backups so I don't lose anything if a Raid0 fails.

[burningforce]

i only get error 132's when I am flying on a flight path an I switch to another character. or I get an error when I log out all at the same time.

so basically I just go afk until i reach my destination on the flight path then switch characters for whatever reason I wanted to.

ran memtest+(10 passes and no errors),defragged, ran wow repair, disbaled addons, checked bios settings and changed a few memory related issues, still nothing seems to work.

[moosejaw]

That sounds like a Directx or video driver issue. I wonder if lowering the graphic settings to the complete minimum on all would have a different result. Maybe try another video card for testing.

Another test would be set them all up on one monitor and see if switching in flight still kills it.

There is the M$ directx link above to make sure it is completely installed.

[burningforce]

That sounds like a Directx or video driver issue. I wonder if lowering the graphic settings to the complete minimum on all would have a different result. Maybe try another video card for testing.

Another test would be set them all up on one monitor and see if switching in flight still kills it.

There is the M$ directx link above to make sure it is completely installed.

thanks i'll check the link and try to put all on 1 monitor and see if I can reproduce the problem