Main errors and exits game

Here's my config file:
http://www.privatepaste.com/2625146cbf
I hope I did it right this time
http://www.privatepaste.com/2625146cbf
Or this
I've noticed lately that, after playing a while, sometimes only minutes, i'll get an error window from windows and a submittal window from blizzard, describing an 'error 132', i believe, an attempt was made to access memory at location 0X0...020 and the memory at that location cannot be read. The rest of the players are not affected, and i just have to logon the main and continue til it does it again.
I have noticed that right before the error, on my 2 hunter team, '2hunts', when i target and attack, interact with target and press a button (1-9), the second hunter just stands there, but his pet attacks. That is when the error occurs. When i play either toon normally (without isboxer) the error doesn't happen.
My pc configuration is: Windows 7 PRO, AMD FX 8150 8 core processor, 4GB Corsair Dominator RAM (ran memtest), MSI GTX 560 Ti 448 Core video card, the CPU is liquid cooled and overclocked, the video is stock.
Since I don't know what's calling the memory read that's causing the error, I don't know what to check or change to stop it, addon, windows, isboxer, or the wow.exe program. Since this forum is experienced in dealing with all of them, I thought it was a good place to start. I just started incorporating video FX into my teams too, so that may be causing a problem, if I didn't set it up right.

[lax]

Ge me a full paste of the #132 error and I'll see what I can find out for you

WOW!! I learned something new:
http://www.privatepaste.com/download/3fd7c191f1


http://www.privatepaste.com/download/426cbacd61

that wasn't too hard after i figured out how to do it, here are both, the windows error and the wow error
And, once again, i could tell when it was gonna happen because my second hunter stopped attacking and just stood there.

[lax]

Okay, technically you got me only part of the #132 error, the big wow error box has a really long thing that I wanted you to copy and paste to me. However, you showed me enough of it to tell you for certain what the problem is.

There is currently a bug in World of Warcraft, where if you have no target and you press Interact with Target, the game may crash due to having no Target. The same problem happens without ISBoxer, but is less common. In order to get this problem fixed, it needs to be reported to Blizzard. It's possible they already have it fixed in the next WoW build, but it's equally possible that the bug report has not made its way to the right person inside Blizzard.

Related thread on dual-boxing.com: http://www.dual-boxing.com/threads/48232-Interact-With-Target-and-ISBoxer-Crashing-in-WoW

That would seem to explain it, but last night when I was trying to duplicate the crash, I noticed the 2nd hunter and his pet were attacking the target of number 1 without pushing IWT button, as in, ' target enemy, spam button 7 (arcane shot)', and both hunters and pets attacked the target. Then, i noticed number 2 hunter wasn't attacking (pet still was attacking), just standing there. Then I started using the IWT button with no resulting change in the 2nd hunter, except the 1st hunter crashed. And i have to disagree with Rootz analogy that it only happens when you have no target, my target was still showing in the number 1 hunters window before windows shut it down, and he was also in melee range because only 1 hunter was attacking him, so he was definately not out of either hunters range. But, the wow error that happens when a toon tries to interact with target and there's no target to complete the command, could posssibly be caused by something in isboxer causing the 2nd hunter to lose focus on the 1st hunters target. That would explain why the 2nd hunter just stood there doing nothing, and then the error happens when IWT fails. I'm gonna try playing it again, when the servers come back up, and not use the IWT button at all when attacking, and if i see number two kicking rocks when he should be attacking, i'm going to physically switch to his window, click on number 1 and type '/focus' or '/focustarget', i'm gonna look that up to see which is correct, then go back and continue, and see if the crash occurs anyway.

UPDATE:
The latest patch notes say the problem 'some' players were experiencing with IWT has been fixed, hopefully that makes this thread unneccessary.