There should be older crash reports you could check too, that one doesn't appear to be caused by an api function (but I guess it isn't necessarily going to always have it).
Here's an example I caused by just running the bad function using a slash command:
Code:
==============================================================================
World of WarCraft: Retail Build (build 15354)
Exe: O:\World of Warcraft\Wow.exe
Time: Apr 4, 2012 3:47:46.686 AM
User: Semlar
Computer: HAL
------------------------------------------------------------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: O:\World of Warcraft\Wow.exe
ProcessID: 10956
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00E18261
The instruction at "0x00E18261" referenced memory at "0x00000004".
The memory could not be "read".
WoWBuild: 15354
Version: 4.3.3
Type: WoW
Platform: X86
Realm: Emerald Dream (206.18.149.14:3724)
Local Zone: Orgrimmar
Local Player: Thoughtfull, 0480000004E73EB5, (1771.83,-4490.29,45.6413)
Total lua memory: 77977KB
Current Addon:
Current Addon function: GetTrainerServiceCost
Current Addon object: (null)
I'm guessing at this point that your issue probably isn't this particular function. Perhaps it's being caused by an infinite loop or something, although I've only ever locked up the client that way before, never a memory access violation.
If your issue is the same as Lombra's and it's one of the addons he's provided a list of, Examiner and Mapster would be at the top of my list for having the potential to break something.