R6025 - Just a hunch

I've been experiencing the R6025 Pure Virtual Function Call error for a while now and would like to try to provide a bit more insight.

The error has occurred while both performing a specific action AND standing still leading me to believe that the error isn't something that can be recreated by following simple steps or doing anything special. Part of me believes the error occurs when the game is trying to gather player quest data from whatever server keeps track of it and applying it into the game environment. For instance, I have seen the error occur in the following scenarios:

- Login completely and sit idle. While the UI is trying to display the HUD quest tracker and recommended quests. Even when performing no actions, the crash occurs.

- Waiting for a quest NPC to draw onto the screen has also caused the crash.

- The crash has occurred by merely running around in Uldah toward a quest turn in.

- Hitting "J" to open and close the journal in a busy city has caused the crash.

- When running to a part of the city and hitting the "invisible wall". I'm guessing this is due to the game waiting for data from whatever app or server is supposed to inform the GUI what NPC's to draw in and whether or not the player has a quest attached to them. Whenever this happens, I know an R6025 error is coming soon. Always does, too.

- Completing the quest, and then hitting the armory button to check out the shiny quest reward, and then bringing up the quest journal as well, has caused the crash.

- Trying to click on a quest NPC too soon after just completing a turn-in has also caused the crash.

- Walking into an area with very FEW players but LOTS of NPC's that have a turn-in indicator. Sometimes the first turn in works, and then approaching the next turn-in causes the crash.

So in short, it looks like it occurs when the game GUI gets out of sync with whatever quest management app/server you have running. Just something to look at.