Visual c++ runtime error

[legacy-Runtime2003]

Visual c++ runtime error

r6025

Pure virtual function call

at startup of ut2003

Please help

[legacy-Rune100]

Im geting the same thing, what is it ?

[legacy-therealvader]

taken from microsoft knowledge base
Microsoft Knowledge Base Article - 125749

PRB: Cause of the R6025 Run-Time Error
This article applies to…
This article was previously published under Q125749

SYMPTOMS
The C++ program fails, and reports the following run-time error:

runtime error R6025
- pure virtual function call

CAUSE
This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.

The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description.

RESOLUTION
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.

STATUS
This behavior is by design.

MORE INFORMATION
For more information, refer to the "C Run-Time Errors R6002 through R6025" chapter of the "Build Errors" book included with Visual C++ 32-bit Edition, version 4.0, Books Online or search the Books Online for "R6025."

NOTE: The R6025 error is not documented in the manuals or online help included with Visual C++, versions 2.x or below. However, it is briefly discussed in Part 3 of the README.WRI file shipped with Visual C++ version 2.0.

Uhhhhh....thanks microsoft

:haha: :haha:

If I were you i would re-install UT.

[legacy-SuperBosse]

Reinstall UT2003 did not help for me. I even went in to the registry to remove everything that had "ut2003" or "unreal" in it to make sure that nothing was left. Also did a search on "epic" but found nothing that seemed related to UT2003. After that I removed the stuff that was left in the UT2003 folder (even after I did an uninstall). Restarted computer and reinstalled the game, same error.

The problem started when I installed a new graphic card (FX5950 ULTRA DeLuxe) and the latest Detonator Drivers from Nvidia.

If anyone has solved this problem, please reply :)

[legacy-SuperBosse]

I have now reformatted my harddrive, installed XP Professional and XP servicepack 1, after I only installed the graphdrivers that came with the game and the soundcard drivers, and no, it still wont work. Clean reinstall all the way, and the freaken game still dont work for me.

[legacy-IQ454]

The problem started when I installed a new graphic card (FX5950 ULTRA DeLuxe) and the latest Detonator Drivers from Nvidia.
I can pretty much say that the GC is not compatible with the game. Your settings are wrong in some way, maybe a guy named mluckey can help on that subject.

Or GC is not set to the games liking.

Try rolling back a few things a step at a time to find the problem.
Or better yet, If you have another GC laying around, wack that in and test it then you will know if it's your GC:)

All in All, UT2k3 does not like GC's that much and is very touchy on settings and compatability, I have a few problems of my own :(

UT2k3 seems to be a load of junk when it comes to compatibility with hardware.
But still a great game if you can get it to work :)

[nwsKrazyK]

I have had that card for years - it runs EVERY game I've ever installed, don't believe ppl that don't know and guess... its a load of poop...

I found that certain Antivirus programs cause this error - nortons can, AVG does and Kasparov - also - "Fast Search" and several other SPYWARE programs and BHO's create this error...

Search GOOGLE for r6025 - I've found several fixes and fixed my UT up - on this pc the problem was an "Anti-spyware" addon called spysweeper -i uninstalled it and the problem went away...

Hope this helps... (btw there is a bios hack for the 5950 and it will run 6 series drivers and games beautifully)

[zombielord666]

Iv uninstalled microsoft visual c++ entierly and now UT3, hellgate and crysis work great. i dont know why its in the ATI driver pack in the first place, its not needed to run the game!! :)

[[PSI]dark_whisper]

FIXED!!! I did some more searching and found that I should run dxdiag from the command promt. These are the errors I found:

Direct3D 7 test results: Failure at step 8 (Creating 3D Device): HRESULT = 0x80004005 (Generic failure)

Direct3D 8 test results: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)

Direct3D 9 test results: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)

After further investigation, I learned that the last three Catalyst updates from Ati were causing this. I emailed Ati support with no avail. It seems the newest drivers (7.9, 7.10, and 7.11) are causing some havoc. I uninstalled the card (radeon X1300) and all drivers, then reinstalled using 7.8. I am back up and running and will be on tonight!!!