Client Crash - "runtime error R6025 - pure virtual function call", C++ library dialog

kitzken · January 2015

I am also getting this error R6025 - pure virtual function call. It really started getting back on 1/18/2015 at the end of Coldharbour, stopping the planemeld and it is happening Khenarthi's Roost in regular v1 fights.

Sacadon · January 2015

@kitzken‌ are you running 1HS when it happens?

Sneski · January 2015

Sacadon wrote: »

@kitzken‌ are you running 1HS when it happens?

I have the problem when I'm playing with my DK 1H and shield. Only then.

When it happens it's always at the exact same enemy. For exemple, I'm doing a solo dungeon. Everything 's going fine, I have the crash. When I log on again I'm dead, I spawn back at the entrance. I start over again but at the same mob BANG ... crash/dead again.
The next day it can be at a different place in that same dungeon. Always somewhere, 1HS is unplayable for me.

Tried every step. Also the ones on other sites (other games, microsoft, ...).
I hope it gets fixed in a future update. I'm playing dual wield now but would like to go back to my first choice.

Nhilandra77 · January 2015

As an update, I would like to add I still get this crash, but nowhere near as often. It is so annoying though when in run in tanking board and sword, owning the mobs then in mid fight it crashes and when I log back I'm dead.

Nardvark · January 2015

Same.. I Did everything they told me.. to do i went 5 days with out a crash now they are coming here and there.. but its been 3 days and i'm running windows 10 and i have not had a crash so fingers crossed

Sacadon · January 2015

Good to hear re: v10

@ZOS_MollyH‌, for those that can reliably repro, why don't you send them some public symbols and a debug release to capture the data you need?

Minimally, what are next steps since "we're working on it" is really unacceptable given how long ZOS has had on this now.

Thanks

C3N50R3D · January 2015

.

Sacadon wrote: »

Good to hear re: v10

@ZOS_MollyH‌, for those that can reliably repro, why don't you send them some public symbols and a debug release to capture the data you need?

Minimally, what are next steps since "we're working on it" is really unacceptable given how long ZOS has had on this now.

Thanks

Hahaha. I have been begging them for this for months for various repeatable bugs. Good luck. XD

Sacadon · January 2015

Maybe they're afraid we'll learn to much about their game, sigh.

RinaldoGandolphi · January 2015

I'm not going to go into too much detail, I'm on my phone but.

Uninstall .net 4.5.2.

Install .net 4.5.1

Hide .net 4.5.2 in windows update. Their are outstanding issues with that version MS plans to address in a future update.

For those who don't have .net 4.5.2 installed, they can run the .net repair tool

http://www.microsoft.com/en-us/download/details.aspx?id=30135

In the meantime I suggest not installing optional updates from windows update, only install security or critical ones only. I hope this helps.

C3N50R3D · January 2015

Bump. Still not fixed and no amount of deinstalling/ installing combinations of .net and C++ redistributables or .net repair tool fixes this likely bad pointer problem.

Nardvark · January 2015

Getting really disgruntled about this now.. Nothing works game is broken. they cant even fix the spider world boss that has been broken for the last 3 months. really fed up.

kitzken · January 2015

Sacadon wrote: »

@kitzken‌ are you running 1HS when it happens?

Yes I was using 1HS on my Templar Imperial, I am now using Bow and DW and have notice allot less crashing of the client. Now the client don't crash with r6025 error it just closes down the client and it crash a few times a week. Before it crashed at lease once a day. But I had uninstalled and reload completely the game and all of the C++ redistribution packages, then update them.

Snowfaerie · January 2015

Same problem here, ran into some mobs in open world while questing and...

1H+Shield as well, as you can see. Happens to me about once a week.

RinaldoGandolphi · January 2015

Out of curiosity, what gpu you have? Are these crashes happening on AMD? NVIDIA?

that crash could be driver related and not necessarily eso.

I can say with confidence that AMD Catalyst 13.12 is the best driver to use with ESO for AMD people. I can count on one hand the number of crashes I have had in the last 2 and a half months on 1 hand after going back to that driver version.

If your not on AMD have you tried going back to an older Nvidia driver release? Sometimes their are regressions and drivers can also cause those c errors, they don't necessarily crash the PC just the application they are using will crash.

Try rolling back to an older driver, AMD users roll back to catalyst 13.12 and see if the errors stop.

Use DDU to completely remove all rements of previous driver install before rolling back to a previous release.

http://www.wagnardmobile.com/DDU/

Just choose your gpu manufacture, it will reboot in safe mode, remove your drivers for gpu then reboot and install previous release and see if the issue persists. You may have to try a few dufferent ones before you find the one that works best. Catalyst 13.12 seems best for AMD users.

Sacadon · February 2015

Been leveling a 2H and destro DK recently to be a CP farmer... Not a single crash. (No changes in my Nvidia GPU driver). Now that I've leveled those weapons I switched to 1HS and Resto and immediately started get the crash again while blocking with shield or bashing. My GPU driver has not changed and has been without issue. The ZOS client has changed and this issue arose after it. So while I think it's still possible to be a GPU driver, I just think it's highly unlikely.

Nhilandra77 · February 2015

bumping too. I still get this crash, not as often though. its only on my 1h+ s . I cannot upgrade or reinstall anything else. It has to be the game itself . only started when the updated the launcher

RinaldoGandolphi · February 2015

I am going to throw in my last 2 cents.

I have been dual booting Vista 64 and Win8(used to have 7 here) for months. I finally decided one day about 2 months ago to copy my ESO files over to Vista64 and run ESO on Vista64 since multiple clean install images of Win 7 or 8 would always crash at some point no matter what i done.

What i found?

The game pretty much don't crash anymore at all.I can go 10-11 straight hours in Cyrodiil or anywhere for that matter on Vista64 without a single crash ever. I have clean installed 7/8.1 numerous times and the game is never stable on those 2 OS. Even the new PTS build runs better on Vista64 then it does on Win7/8 or 8.1 because I have tested it on both.

I get:

Higher min framerate
less FPS drops
etc

FX 8350 Crossfire R9 280x

Believe it or not, just Upgrade to Vista64 and all your problems with ESO will simply vanish. The game flat out runs better on Vista64 then it does on Win7 or Win 8/8.1

I have no idea why this is, but it does. I kept Vista around for compatibility reasons, and now I am glad i did.

Also the unresponsiveness with weapon swapping? Don't happen on Vista64. I can reproduce it every single time on Win 7 or Win 8/8.1 but on Vista64 weapon swapping works 100% of the time period.

MS changed how some of the input functions with mouse and keyboard work on Win 7/8 and pretty much it will never be fixed.

http://support.microsoft.com/kb/2908279

You can help it in some games, but it will never be really fixed...Windows 10 is going back to the Vista way of handing mouse and keyboard functions on the backend which means it will run ESO better with no more of that weapon swapping not working nonsense.

Honestly, I never would have dreamed in a million years that all the aggravating annoying things about ESO would be solved by simply running the game on Vista64. Vista64 will receive security updates until April of 2017, so i don't have to be in any rush to move to 10 when i choose to do so.

right now, Vista64 is where its at if your sick and tired of the annoying crashes and weapon swapping delays, and losing sound nonsense. Yes Vista64 also solves the sound cutting out issue in Cyrodiil large battles, haven't lost sound once since i started running the game on my Vista64 partition.

Long story short, if you can, just start playing ESO on a Vista64 rig if you can, all these annoying issues will probably go away. They have for me. I have 3 clean OS images files i switch between, right now i use Vista64 to play ESO, and do work on 8.1. I just got sick and tired of it...its funny though that Vista64 runs this game 100% better then Win7 or 8 does. hopefully Win10 fixes that once and for all.

C3N50R3D · February 2015

Source for your Windows 10 mouse input claims? Windows 8.1 changed the mouse input to batch mouse events. This does not affect windows 8 and previous. Adding explorer.exe to the registry setting to disable the new mouse input will put the system back to the previous mouse event handling method. Google how to do this. There is also a command line you must run. Dynamicticks was introduced in windows 8 to batch timer events. This also increases latency and is easily disabled through a bcdedit.

RinaldoGandolphi · February 2015

C3N50R3D wrote: »

Source for your Windows 10 mouse input claims? Windows 8.1 changed the mouse input to batch mouse events. This does not affect windows 8 and previous. Adding explorer.exe to the registry setting to disable the new mouse input will put the system back to the previous mouse event handling method. Google how to do this. There is also a command line you must run. Dynamicticks was introduced in windows 8 to batch timer events. This also increases latency and is easily disabled through a bcdedit.

umm...I have been testing it since they released the 1st beta previews of the OS?

I know what Dynamic Ticks and such are, and thats not what im talking about. Im talking about how The Windows API's and the wrappers behind them changed in Windows 7 and Windows 8 compared to Vista and XP. Some of the behind the scenes things changed in those 2 OS

For example, Windows Vista by default will use HPET(High Precision Event Timer) as the default timer for the OS if its available on the Motherboard and enabled in the BIOS, this can easily be checked with WinTestTimer Windows 7 and Windows 8 default to TSC or APIC unless bcedit commands are used to specifically force it to use HPET.

It is my theory that HPET has an effect on input and the input lag experience in conjunction with it. HPET don't give you a FPS increase or make the game run better per se, but i do believe it will help in other scenarios. Why Microsoft backed off of HPET after Vista i have no idea, but I have heard chatter they are strongly considering going back to HPET as default on Windows 10.

i can easily reproduce the weapon swapping bug on Windows 7 and 8(even with the reg hacks), it simply doesn't happen on Windows Vista. Why does Windows Vista not have these problems? I have a hunch HPET along with changes under the hood to how mouse and keyboard commands work(most likely the wrappers around them) have changed in 7 and 8 in comparison to its older sibling. This, the HPET, etc is a guess, but its the only thing i cna put my finger on as to whats different, and its the only thing i can see that would cause Vista to not have any issues with this.

or it may be something completely different, I don't know. All i know is, Vista don't have these problems, nor the crashes 7 and 8 do.

C3N50R3D · February 2015

woodsro wrote: »

You can help it in some games, but it will never be really fixed...Windows 10 is going back to the Vista way of handing mouse and keyboard functions on the backend which means it will run ESO better with no more of that weapon swapping not working nonsense.

I agree OS's like XP where the hardware is not so abstracted from application space tend to be more efficient and less versatile when processing hardware calls. I am just curious about the source for your claim about Windows 10 mouse input going back to Vista method. I would like to understand this more. Do you have a Microsoft link?

C3N50R3D · February 2015

Copied from my post in the other thread.

http://support.microsoft.com/kb/125749

It is a game bug that may be handled differently depending on which .net versions you have. Your OS already contains several versions of .net even if you did not separately install them. Some versions of .net have issues in certain configurations. I believe the engine now relies on .net v4.5
.net v4.5.2 may have issues but I will have to test further to confirm.

Those still getting the repeatable error try uninstalling only .net v4.5.2 with this cleanup tool and report back. You may also want to use the setup verification tool to ensure correct setup of v4.5.1 and v4.5

http://blogs.msdn.com/b/astebner/archive/2013/11/11/10466402.aspx

Emma_Overload · February 2015

I uninstalled .Net 4.5.2 AND uninstalled Adobe Flash, and this bug STILL happens when I'm fighting bosses with Sword and Shield and doing a lot of blocks and interrupts.

C3N50R3D · February 2015

Install the latest Adobe Flash and Java. If you run 64 bit OS install both 32 and 64 bit Java versions. The game doesn't seem to like some of the older default installations.

Edit: Uninstall your old Java versions before installing the newest.

Twyst · February 2015

I am getting this crash at least once each time I run a dungeon or delve. It's really really annoying now. I have tried installing the VC++ re-distributables and disabling all addons. Nothing works, I just cannot tank anything 1H+S.

Shadow27 · February 2015

Got this one as well. So far I found, I got it when I was sprinting with my horse and was trying to jump (remeber JUMP not ride down) from stairs in Belkarth city center. Happened 3 times there, on exact same spot. Maybe it´ll help?
Note that once I avoid jumping from stairs there, it works fine and I never got it so far...

Sacadon · February 2015

Interesting... That's definitely different than the 1HS circumstances most of us have had. Maybe it's some call in response to health damage? I was beginning to think it was narrowed down to proc of a 1HS passive, but not so sure now.

I'm sure that we should not have to reinstall Vista-OS to get rid of it. If doing so does fix it, then I'd be surprised if ZOS was not able to code for the difference in architecture. I'm skeptical that such an underlying and fundamental OS function would only negatively effect 1HS passive and health damage while on horse. I would expect much more widespread issues if this was the case. Wouldn't be first time I was wrong of course. )

RinaldoGandolphi · February 2015

C3N50R3D wrote: »

woodsro wrote: »

You can help it in some games, but it will never be really fixed...Windows 10 is going back to the Vista way of handing mouse and keyboard functions on the backend which means it will run ESO better with no more of that weapon swapping not working nonsense.

I agree OS's like XP where the hardware is not so abstracted from application space tend to be more efficient and less versatile when processing hardware calls. I am just curious about the source for your claim about Windows 10 mouse input going back to Vista method. I would like to understand this more. Do you have a Microsoft link?

No its just chatter I heard about on a mailing list I'm part of where their are a lot of devs testing the OS.

The API calls and such will remain the same, they are just removing some of the overhead we have now to make it more like Vista in somewsys just making it more efficient.

However this is subject to change if course as win10 isn't final yet.

You can download win10 preview it does run eso better then 7 or 8 and input us more responsive.

RinaldoGandolphi · February 2015

Sacadon wrote: »

Interesting... That's definitely different than the 1HS circumstances most of us have had. Maybe it's some call in response to health damage? I was beginning to think it was narrowed down to proc of a 1HS passive, but not so sure now.

I'm sure that we should not have to reinstall Vista-OS to get rid of it. If doing so does fix it, then I'd be surprised if ZOS was not able to code for the difference in architecture. I'm skeptical that such an underlying and fundamental OS function would only negatively effect 1HS passive and health damage while on horse. I would expect much more widespread issues if this was the case. Wouldn't be first time I was wrong of course. )

It is strange how well Vista SP2 runs this game. Its insane.

Now this won't solve your crashing problems, but I have found forcing HPET in win 7 or 8 helps on my hardware.

To do this go into your BIOS and ensure HPET(high precision event timer) is turned on.

Next run the following command from a command prompt ran as administrator

bcdedit /set useplatformclock true

Reboot system.

Now HPET is enabled.

If you find HPET don't help you, then

Run this command first

bcdedit /deletevalue useplatformclock

Then reboot to BIOS to turn it off.

Don't turn it off without disabling it via the command above or it may cause problems.

I run HPET on, it makes things run better for me on my specific hardware, ymmv

C3N50R3D · February 2015

Forcing HPET can help in certain circumstances. It can cause stutter in others because although higher resolution, it can get out of sync.

@woodsro, Regarding Windows 10 it would be great if Microsoft is finally taking gaming seriously.

What FPS are you getting in Wayrest Courtyard between the castle and bank with your crossfire rig running Vista?

RinaldoGandolphi · February 2015

C3N50R3D wrote: »

Forcing HPET can help in certain circumstances. It can cause stutter in others because although higher resolution, it can get out of sync.

@woodsro, Regarding Windows 10 it would be great if Microsoft is finally taking gaming seriously.

What FPS are you getting in Wayrest Courtyard between the castle and bank with your crossfire rig running Vista?

Usually somewhere between 47-52 fps. It very rarely drops into the 30s, but it does so less often. It seems overall smoother. As I said I have no idea why this is though.

PS: I just recently fixed my 1440p monitor (bad power brick, got it replaced), i did lost 4-5 FPS going from 1920x1080 to 2560x1440. the 47-52 was based on 1080p. Im glad to be back to 1440P, playing at 1080 for a few weeks was pretty painful when your used to a higher resolution.