Bumpity bump.
Printable View
Bumpity bump.
Up and up...
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.
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.
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.
33 pages of postings about this problem and I didn't see a response from se? wow I hope this gets fixed
This is certainly an issue on SE's end.... We've had the problem for 1.5 months now, not even an acknowledgement. WTF
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.
This game is full with gamebreaking bugs (unavoidable special attacks due the brutally poor netcode) virtual call, falling out from the world into a maze of invisible walls (and stay in the world partially) It`s a really good beta, but far away to be released.
Solution: get a few decent programmer, coder, the current staff, management or whoever made the decision of be released, failed miserably. Imho...
ps all the above mentioned problems happened with me and I`m sure I have not seen/experienced everything.....
Update on what I said.
It lasted for 1 day without fail till today runtime error X86-
Phase 3 I had zero issues with this, Phase 4 nothing.
Full game release was nothing till they did the first update.
RunTime Error happens when I, Zone, touch a teleport crystal, teleport to another zone, running sometimes I run into a invisible wall that isn't even there, I back up move forward and crash, run past zone blue dotted line crash, ive uninstalled game 3 times, even regedit out all c++ files, framework and ffxiv, I ran repair disc for windows 7, I updated drivers, ive disabled programs and enabled to pin point problems.
Ive had this since the 1st update and have been trying to figure it out myself with no luck, everytime I think I have it fixed its not and im sick of it, just because others don't have it, you are ignoring the problem bad for bis SE.
Bumpitty bump. Keeping this where it can be seen.
I am getting this error AT LEAST 3 times an hour. WHEN WILL THIS BE FIXED? I have to cancel my account until this is fixed because it is unplayable currently. I tried every solution under the sun I could think of, or read to do. Has ANYONE found a way to fix this?
Sadly that has happened to me as well
The falling through terrain
http://i202.photobucket.com/albums/a...ps8cdf3200.png
(fyi that image was taken before I got my race change)
The R6025 error of death
Just started to get the computer restart/crash
I don't even want to do H Primals cause of the issues with lag
I really doubt it's issues with my rig (it's showing age but it's not terrible)
Geforce GTX 550 Ti
AMD Athlon(tm) II x2 255 processor
4gb memory
Windows 7 64 bit
I have over 100 games/MMO's on my computer and steam, NONE of them have issues like FF14 ARR does
Still happening to me, along with a fun combo of 90000 and 3102
I, too, am having this problem.
The first two weeks the game was live, I was on Windows XP 32bit with 2 gigs of ram. I upgraded to 6 gigs of ram (all were tested and are working properly) and reformatted to Windows 7 64bit and I have had this error ever since. I have uninstalled and re-installed the game, updated drivers and tried older versions, and have all Windows updates, yet this error comes and goes for me. I've gone 3 days without having it (after a fresh re-install of the game), only to get hit with it 8 times in one day. There's really no pattern to replicate it. I've had it pop up while zoning, while standing still (once while I wasn't even at the computer), while running to a fate or quest, and immediately upon entering the game. It really sucks and I'm anxiously waiting (hoping..) for a fix. :( I play a lot of games and haven't encountered this issue in any of them.
So I tried something new.
I decided for a Second time to re-installed windows 7 and drivers.
Clean slate-
I installed all updates first Minus my video card.
I decided not to download firefox yet, I used IE to download the FFXIV client.
I right clicked the install and put it on administrator something new happened direct9x popped up and installed.
After that was done, I right clicked the FFXIV desktop icon and also put that in run administrator which downloaded the update.
After I installed my video card using my cd with my first update-
The game runs actually better than before and I haven't crashed, so far so good, I know a lot of you might not wanna do this but I was at me wits end and decided to just do it had windows old to gain back all my old stuff so if you don't wanna rely on SE try that.
I saw this thread through Google and thought id post a link directly to the Microsoft support page which specifically addresses this problem as i myself suffer from it multiple times a day so it limits me basically to crafting/gathering all day in 1 zone
http://support.microsoft.com/kb/125749
Long story short this is only fixable by SE and we as the users can not correct the problem
So after googling around a bit the other day I saw this steam forum discussion about changing your screen resolution and how it fixed this dudes r6025 issue. basically you load up a game that you know works and auto adjusts your resolution, see what its set at and apply it to the game that gave you the r6025 error. I have done this and despite the normal lag and the long load times for npc's and such, which have been now faster, I haven't yet gotten the error. /knockonwood.
here is the link. http://forums.steampowered.com/forum....php?t=2471777
anyway I'm gonna keep my fingers crossed and see if I cant make it a whole week without the error.
I'll post here if get it again or not. good luck all
I take it back. Got my first C++ error in about a month. After several weeks of constant C++ runtime errors built a new computer and they stopped. Today, just sitting there around in Aleport, doing NOTHING and C++ runtime error. I don't know why I'm ever typing this. Have yet to see a single tech support guy respond to any threads in this forum, but wanted to make sure even someone that STOPPED having the issue, got one today.
Never mind.
Everything runs smooth but- it didn't work, it happens when NPC or The Blue dotted line don't load up on screen.
If you pass a crystal or NPC who's name is green but not showing the names at all and Teleport you get the runtime error.
I tested this out Sprinting through zones in gridania because they are close together.
Notice the land has a hard time keeping up and then the blue dotted line is not visible when you're zoning you will get runtime error, if you run passed the NPC and their name doesn't show you'll hit a invisible wall, then sometimes even falling into a hole that didn't load the ground. I didn't fix my issue but I am thinking it might be too much on the screen to load.
After playing for like 6 hours today without any problems. I logged out for awhile only to get this error again!
It happened to me as I was loading into Titan HM from Uldah O.o Luckily my party waited the minute it took me to reconnect, but boy does this error suuuuck
BUMP :mad:
The sad thing is it's a corrupted file issue that has to be corrected by a programmer, there's really nothing on our end that can fix this issue and the fact that SE hasn't done anything to fix or help just looks like they are ignoring the issue cause let's face it, they are in some deep water when it comes down to delivering to their fans the past 13 years to the point they are losing money every quarter.
that is incorrect, not everyone is getting this issue because not everyone has the same hardware/drivers, it is happening mostly to people with AMD and Nvidia Video chipsets. but not all. if it were corrupted files you would be able to fix it with a reinstall but that doesn't work because it's not, it's bad code calls used in the visual C++ library.
if you look up the error there are all sorts of fixes, some work some do not, but none work for this game. not one. I tried reinstalling. didn't work game crashed within 5 minutes of logging in. tried some of the other fixes like reinstalling all Visual C++ libraries also didn't work. tried a fresh install of windows with no visual C++ libraries. still didn't work. the problem is bad code and the only ones that can fix is are SE and they have acknowledged this as a problem but I suspect they still haven't found a clue as to the cause
I should also note I didn't get this problem myself even once during the first 3 beta phases
I would be more inclined to believe it is related to certain third party applications interfering with the process in some way.
This is got REALLY bad now, EVERY ****ING TIME I zone from Limsa upper to lower or vice versa it happens. EVERY TIME!!!
FFS SE, your customer service is bloody awful, completely ignoring your customers?
There are numerous threads on this and only ONE has any sort of official response, and it's a moderator response rather than a Dev response....
i just want it to go away D;
People need to stop trying to fix this because there is nothing you can do to fix it, only SE.. This same runtime error was present in 1.0 although not as widespread and SE turned a blind eye then, expect them to do the same again.. The whole tech support forum right now is just a joke..
Hammer SE all you want on here for a reply but it's been nearly 2 months without a single post at all in tech from anyone, so don't hold your breath..
I don't get it at all, So there needs to be some more information from end users to determine the nature of the issue.
everyone getting the issue, please update your original posts with an info dump from ffxivsysinfo.exe
Incroyable, cette erreur existe depuis la nuit des temps, c'est UNE ERREUR DE PROGRAMMATION.
Bordel de merde, il serait temps d'avoir UNE VRAIE information, SE bougez-vous le cul, engagez des programmeurs, pas des charlots !!!!
Restez muet n'arrangera rien à vos problèmes ou faut-il que nous rendions cette information publique ? dites le moi, aucun problème.
En attendant je ne vous remercie pas, le laxisme : c'est mal.
Well hello K'ee ^^
The funny thing with this error is that one patch makes it mostly go away and the second one brings it back. Same bug happens on PS3, actually, the game simply locks up and you need to reboot the console. One could blame the Ps3 for that, but if you looked deeper, the game locks up on exact same situations this runtime error can happen.
Virtual function call is always a programming error. And this is an error with the map loading function, this error can only happen when the game is loading parts of the map.
Got a runtime error this morning after logging in and now the client won't even let me login, after entering my details the login button just doesn't do anything :(
Nothing has changed on my system over night and i've been running the game fine for weeks, absolutely no idea what to do.