The error isn't a file on your D drive. Rather, it's indicating one of World of Warcraft's source code files. Any time a WoW crash box comes up it's going to provide debugging information to help the WoW developers identify the cause. So "D:\buildserver\wow\5\work\wow-code\branches\wow-patch-3_3_5-bnet\engine\source\blizzardcore\blizzardcore\sourc e\system\memory\MemoryStorm.cpp" is just the path and filename of one of the source code files, on the computer they use to generate official WoW client builds -- the filename is hardcoded (automatically) right into WoW.exe or related files when they build it.

If you're not out of RAM, this error is probably due to memory corruption. It's probably due to some changes they made to the code in the 3.3.5 patch (which is why it would happen now and not the day before the patch). There's no way for you or I to determine what the cause is.

A quick google for wow 3.3.5 memory error turns up some threads on the official WoW forums:
Technical Support forum, thread started by a Blizzard poster: http://forums.worldofwarcraft.com/th...sid=1&pageNo=1
A workaround might be here according to someone: http://forums.worldofwarcraft.com/th...sid=1&pageNo=1
A thread on the EU forums: http://forums.wow-europe.com/thread....46567792&sid=1

... so yeah I don't think this is in any way related to Jamba or ISBoxer