Error# 132 - Blizz mentioned Innerspace might be cause

Hello,
I used Innerspace for over a year now, and everything was working well and all, love this software, but a few months ago, I have this error 132 and whenever i switched windows, i get this crash, sometimes one window, other times, multiple.

So, I searched, browsed, did all I can. I even replaced my memory modules.
So, I finally posted in battle.net forum, posted the error, and was requested my support to post a dxdiag file.

Here is the original post: http://us.battle.net/wow/en/forum/topic ... 0?page=1#2
Lamanh is what I posted under.
So, they said to update ati drivers, which I did and in the response, they mentioned Innerspace crashes in the log.

I don't believe them. but I really am at lost with this problem. Deleted cache folders in both data file and the regular cache in WoW folder. Uninstalled the game, and reinstalled, opened up my computer and my room's window so there is cooling.

I am at lost, can you help? I don't believe Innerspace is the culpirt as many boxers are using it. But I am seeking help as they mentioned several crashes in the log file as a result of innerspace, I don't know how to read these files....


It keeps saying it is ISboxer:

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Users\Public\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00000000

The instruction at "0x00000000" referenced memory at "0x00000000".
The memory could not be "executed".


WoWBuild: 13329
Realm: Ner'zhul [12.129.254.178:3724]
Local Zone: The Warlord's Garrison, Lost City of the Tol'vir
Local Player: Saraiyee, 0300000004278103, (-10734.5,-1310.54,15.3534)
Last Enemy Target: Oathsworn Tamer, F130B0290003B206, (-10733.6,-1304.12,15.3528)
Total lua memory: 32190KB
Current Addon: ISBoxer
Current Addon function: ConsoleExec
Current Addon object: (null)

I deleted it and re-exported it back and it still crashes...

Thank you for the help.

SaraiE

[RSM72]

See my post here http://www.lavishsoft.com/forum/viewtopic.php?t=4775. I got alot of #132 crashes with dev builds after 5326, dont know if lax is still investigating.

[lax]

#132 is just a general error code that means "unhandled exception". There are many thousands of extremely different things that this can be, so never assume that your "#132 error" is similar in any way to someone else's.

This crash would seem to be related to use of the /console command in an ISBoxer-created macro. I'm amazed that the support staff on that thread have no idea what is going on with WoW Addon related errors. Maybe I shouldn't be.

If you show me your ISBoxer config perhaps I can help identify the one (/console command) that is crashing, but this may also be enough for you to go on to narrow it down through trial and error and I might not be any help in doing that if it doesn't crash me too.

[lax]

You can also try switching to DirectX11, see http://isboxer.com/forum/viewtopic.php?f=22&t=774 for instructions

http://www.privatepaste.com/864442fd35

Thanks Lax! Here is the configuration info.

SaraiE

edit: I switched to DX11, still crashing.

[lax]

It's one of these:

Code:

/console farclip 1250
/console groundEffectDensity 25
/console groundEffectDistance 50
/console environmentDetail 50
/console particleDensity 30
/console shadowMode 0
/console waterDetail 0
/console reflectionMode 0
/console sunShafts 0
/console basemip 0
/console terrainMipLevel 0
/console projectedTextures 0
/console weatherDensity 0
/console componentTextureLevel 1
/console textureFilteringMode 1
/console Sound_EnableAllSound 1
/script SetView(4); SetView(4)

Code:

/console farclip 50
/console groundEffectDensity 0
/console groundEffectDistance 0
/console environmentDetail 0
/console particleDensity 10
/console shadowMode 0
/console waterDetail 0
/console reflectionMode 0
/console sunShafts 0
/console basemip 1
/console terrainMipLevel 1
/console projectedTextures 0
/console weatherDensity 0
/console componentTextureLevel 0
/console textureFilteringMode 0
/console Sound_EnableAllSound 0
/script SetView(4); SetView(4)

Blizzard technicians could probably be more specific about which of those commands is crashing, given your crash log. But I don't suspect you'll get to one that can do it and they might not give you any useful information. So anyway, quickest way to narrow it down is to start ruling out half of them at a time -- remove half of them and see if it stops crashing, if it doesn't crash anymore whatever's left is safe. If I was to venture a guess I'd say it might be basemip and/or terrainMipLevel? But it is just a guess.

[Ualaa]

Odd, my low settings are identical, and my high settings a tad higher... but no SetView.
That was the macro Fef came out with, but his high settings were cranked.

My high settings are:

Code:

/console farclip 1250
/console groundEffectDensity 36
/console groundEffectDistance 260
/console environmentDetail 40
/console particleDensity 75
/console shadowMode 0
/console waterDetail 0
/console reflectionMode 0
/console sunShafts 0
/console basemip 1
/console terrainMipLevel 1
/console projectedTextures 0
/console weatherDensity 0
/console componentTextureLevel 1
/console textureFilteringMode 1
/console Sound_EnableAllSound 1