Runtime Error

[OffbeatShinigami]

Bumpity bump.

[Ubermann]

Up and up...

[Yoseph]

Found this at MS:

Description of the R6025 run-time error in Visual C++

Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.

One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.

Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.

>>>>>end<<<<<<<
this is a programming error

SE is the only one that can fix it

[KingofDunkshire]

Found this at MS:

Description of the R6025 run-time error in Visual C++

Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.

One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.

Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.

>>>>>end<<<<<<<
this is a programming error

SE is the only one that can fix it

What is sad is SE probably won't fix it or at least continue to believe it's something on our end since their ego is so absurd the past few years. I've been saying this since I first got it (last day of open beta) that this error is on SE end and that it's a program error on their part.

[Kittra]

I keep saying this, but if it was a programing error on SE's part then everyone should be experiencing it.
I have yet to get a runtime error, and hopefully it stays that way.

[KingofDunkshire]

I keep saying this, but if it was a programing error on SE's part then everyone should be experiencing it.
I have yet to get a runtime error, and hopefully it stays that way.

To bad it is a programming error, anyone who's remotely into that field will tell you exactly what the R6025 run-time error is. Just cause you haven't been effected by it doesn't mean it's not SE fault, just means you haven't got to that error in the programming yet.

People have already reported having this error after

-Re installing FF14 ARR
-Re installing MS updates
-Removing or re installing microsoft visual c++
-People with new rigs still get this error (so a possible corrupt update is pretty much impossible)
-Updating/rolling back graphic drivers

It's happened to a lot of people with different rigs, the only thing that connects the issue is how this error happens and that's when you're ether teleporting or in a severe laggy area when npcs,mobs or other players don't appear for awhile (cities/areas that are packed with fate farming) which causes the runtime error.

I've actually been R6025 error free for about 6 days tell today, which I've gotten the error twice already, both times was in Dragonshead.

[HeroSamson]

It's a application error.

I have messed with my pc for 2 weeks.

I believe I may have come to a solution I do not know if this will help everyone but its worth a shot.

I have downloaded http://www.microsoft.com/en-us/downl....aspx?id=39328

I zoned from place to place to test so far so good no crashing, I am crossing my fingers.

I also have C++ 2008 redistrubable x64 9.0.30729.6161
C++ 2008 redistrubable x86 9.0.30729.6161


Hope this helps out.

[Belali]

33 pages of postings about this problem and I didn't see a response from se? wow I hope this gets fixed

[Ubermann]

This is certainly an issue on SE's end.... We've had the problem for 1.5 months now, not even an acknowledgement. WTF

[Yoseph]

I keep saying this, but if it was a programing error on SE's part then everyone should be experiencing it.
I have yet to get a runtime error, and hopefully it stays that way.

Wrong.

It just got past the dev team because it only happens at run time, when specific conditions occur, or when its code "meets the road and the road takes priority" because the code did not approach the freeway the right way.

If you have received the message that reads "Runtime error R6025 Pure Virtual Function Call," then the program you are using has been corrupted in some way and will need to be deleted and then re-installed. This does not solve the problem though, you can reinstall SE 50 times and it still happens. Even reinstalling the OS will not cure the problem. It is in the Code.