Odd Runtime Problem

[Stonewall]

I'm experiencing an odd problem. I was plahying EU2 a little while ago and the game froze up on me. No crash, no exit, just froze. Had to kill the power on the machine to restart. I go back and load up a couple different games and when they load, I get a Microsoft C++ Runtime R6025 error. Any ideas on what this is or how to fix it?

 

[Castellon]

It does not ring any bell.
Try Microsofts knowledge base.

 

[jpd]

Ah, the old 'pure virtual function called' problem raises it's ugly head again.

That is something that normally should never occur. It means that a function in a base class has been called that was defined as pure virtual. Meaning that there is no actual code defined for it, and that it never should be called.

When it does get called for one reason or another, the runtime library intercepts in and aborts the program. It signals a bug in the program code.

Jan Peter

 

[Castellon]

Thing is he is getting it with other programs as well, maybe a corrupted file somewhere, or a virus.

 

[AndrewT]

Well, if it's at all related to EU2 it's likely to be one of the DLLs it installs. So a total uninstall followed by a reinstall should fix it.

 

[jpd]

Well, if it's at all related to EU2 it's likely to be one of the DLLs it installs. So a total uninstall followed by a reinstall should fix it.

If that's the case, then reinstalling EU2 won't help. EU2 is written in VC++. The VC++ runtime DLL's are part of a normal Windows distribution, and are as such not part of the EU2 setup. Same goes for the DirectX code.

Most likely a reinstall of Windows itself + DirectX is what is needed here.

Jan Peter

 

[Stonewall]

Very odd thing. I went back to some very old savegames and they have worked, however, I'm getting runtime errors with another program now. Please tell me that a Widows reinstall is not needed. Please?!?

 

[jpd]

It sure sounds like a problem inside your system.

If the VC runtime library itself has been corrupted, then they need to be reinstalled. And that's the problem. Because Windows itself is written in VC++ and uses those same runtime libraries, they get installed when you install WIndows. No other program's installer would actually install/update those core DLL's. Unless you know exactly what you are doing and are capable of selectively extracting those from the cabinet files AND using the preboot command box to copy them to the appropriate place, then a reinstall of Windows is the easiest way of getting the correct files again.

If it's DirectX that is corrupted, you could always try to run it's setup program again. But I don't know how intelligent that setup routine is. In other words, if it's capable of detecting and replacing corrupted files.

EDIT: Before you run off and do a format, you can try a hot install first. Basically, that means running the Windows setup program from the currently booted desktop, and using the same target directory as your current Windows installation. If you have the correct version of Windows (basically, a non-OEM version), then it will reinstall itself, while preserving your registry, desktop and start menu

Jan Peter

 

[Stonewall]

Thanks for the advice. I think I'm going to wait it out and hope the corrupt files don't affect any of my important programs. If it gets bad, then I'll do a Windows reinstall. I hate to do that for fear of losing all of the programs I currently have, some of which I no longer have the CD's for. Oh well.

 

[Castellon]

That's why you should always have a second drive. Logical partition at the least or Physical prefered.