Not to be horrid or anything, but Google IS your friend..
http://www.google.com/search?lr=&ie=...unction%20call
Oh okay then - this C++ errorcode is due to a programming error in whatever app you're using.
"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."
So it ain't your fault!
PS: I have to disagree with Spinflight about disabling VM - particularly if you have less than 1GB of memory.
Some apps (admittedly not most of the standard ones) just won't run without VM. In addition, this wastes a lot of the RAM. The reason is that when programs ask for an allocation of Virtual memory space, they may ask for a great deal more than they ever actually bring into use — the total may easily run to hundreds of megabytes. These addresses have to be assigned to somewhere by the system. If there is a page file available, the system can assign them to it — if there is not, they have to be assigned to RAM, locking it out from any actual use.
I run a pagefile of 512MB (don't use the "2.5 x installed RAM" story) with 1.5GB of memory, but could get away with 100MB.
Windows (and apps) expects there to be a pagefile - disc space is cheap and the performance hit (?) is minor while the stability hit can be major.
"You are in a dark and damp cellar with a narrow passageway leading north, and a crawlway to the south. On the west is the bottom of a steep metal ramp which is unclimbable."