|
Home > Archive > Flight simulator > October 2005 > Runtime Error Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Runtime Error Problem
|
|
|
| Hi,
HISTORY: I've had this computer for almost a year and so far it has
performed flawlessly. I can max out most of the FS04 setting and
still get 20+ FPS except in very dense scenery areas. The few
problems I have had always turned out to be due to scenery file errors
I had made (tried to use old macro's with FS04 scenery I made and they
were not compatable) - which were quickly resolved.
PRESENT: The silly thing has gone nuts (started just after I
downloaded and installed the latest "critical" Microsoft patches).
Six times today I got the following error and FS04 stopped dead:
Runtime Error
R6025 - pure virtual function call
I Googled this and found nothing that helped, especially from
Microsoft (their answer was nothing but gibberish - to me, anyway).
I have done nothing to cause this to happen, to the best of my
knowledge. The people who test my scenery as I develop it are not
seeing this. As mentioned above, the only coincidence I can think of
are those patches. I can see no event taking place that causes it
(like entering a specific scenery area) - it appears to happen totally
at random. It does not seem to happen with any program except FS04.
What the heck, anyone????
Operating system - Windows XP Pro with Service Pack 2
Computer - Dell Dimension 4700 (2.8GHz, 800 FSB)
Memory - 1024MB Dual Channel DDR2 SDRAM at 400 MHz
Video Card - 256MB PCI Express x16 (DVI/VGA/TV-out) nVidia GeForce
6800NV6800
(NOTE: computer info was copied from the data sheets, I only
understand a small part of what it is saying).
Jim
| |
| L. Mulder 2005-10-24, 7:33 pm |
| Oh dear,
Jim, I do fear a virus on your computer after installing this so called
"critical patch". Those messages mostly come with the W32.Swen.A@mm virus or
W32.Sober.A@I@mm!enc . My first advice would then be to run a comprehensive
virus scan with a good virus scanner. And while you're busy anyway use an
anti-spyware tool as well. Wish you luck and hope for you the solution is
simpler and that I am wrong!
Loek
"Jim" <BozAir@REMOVETHISchartermi.net> schreef in bericht
news:vu8ol15igptspjavrjr78qa0ad2s8p3ckh@4ax.com...
Hi,
HISTORY: I've had this computer for almost a year and so far it has
performed flawlessly. I can max out most of the FS04 setting and
still get 20+ FPS except in very dense scenery areas. The few
problems I have had always turned out to be due to scenery file errors
I had made (tried to use old macro's with FS04 scenery I made and they
were not compatable) - which were quickly resolved.
PRESENT: The silly thing has gone nuts (started just after I
downloaded and installed the latest "critical" Microsoft patches).
Six times today I got the following error and FS04 stopped dead:
Runtime Error
R6025 - pure virtual function call
I Googled this and found nothing that helped, especially from
Microsoft (their answer was nothing but gibberish - to me, anyway).
I have done nothing to cause this to happen, to the best of my
knowledge. The people who test my scenery as I develop it are not
seeing this. As mentioned above, the only coincidence I can think of
are those patches. I can see no event taking place that causes it
(like entering a specific scenery area) - it appears to happen totally
at random. It does not seem to happen with any program except FS04.
What the heck, anyone????
Operating system - Windows XP Pro with Service Pack 2
Computer - Dell Dimension 4700 (2.8GHz, 800 FSB)
Memory - 1024MB Dual Channel DDR2 SDRAM at 400 MHz
Video Card - 256MB PCI Express x16 (DVI/VGA/TV-out) nVidia GeForce
6800NV6800
(NOTE: computer info was copied from the data sheets, I only
understand a small part of what it is saying).
Jim
| |
| Iain Smith 2005-10-24, 7:33 pm |
| Jim,
If you obtained the Microsoft updates from the Microsoft site then it is
highly unlikely that you got a virus that way. However, if you recieved the
so-called Microsoft critical updates attached to an e-mail (MS *never* do
this) then Loek is probably right!
Iain
"L. Mulder" <lbn.mulder@hccnet.nl> wrote in message
news:sl57f.256192$aL2.20528@fe02.buzzardnews.com...
quote:
> Oh dear,
>
>
>
> Jim, I do fear a virus on your computer after installing this so called
> "critical patch". Those messages mostly come with the W32.Swen.A@mm virus
> or
> W32.Sober.A@I@mm!enc . My first advice would then be to run a
> comprehensive
> virus scan with a good virus scanner. And while you're busy anyway use an
> anti-spyware tool as well. Wish you luck and hope for you the solution is
> simpler and that I am wrong!
>
>
>
> Loek
>
| |
|
| Hi,
On Mon, 24 Oct 2005 15:29:49 +0200, "L. Mulder" <lbn.mulder@hccnet.nl>
wrote:
quote:
> My first advice would then be to run a comprehensive
>virus scan with a good virus scanner. And while you're busy anyway use an
>anti-spyware tool as well. Wish you luck and hope for you the solution is
>simpler and that I am wrong!
I suspect you are, but I still appreciate the reply! My "thing" is
computer security, so naturally I'm running the latest and greatest in
anti-virus and anti-spyware programs (1 anti-virus, 1 firewall and 2
anti-spyware programs). The critical patchs I was referring to were
the ones Microsoft finds it necessary to put out almost every month
(about the middle of the month) - they came direct from Microsoft, not
from some other vendor. And in addition to the scheduled scans, I run
manual virus and sypware scans frequently (it's something to do when I
get bored).
I mentioned the Microsoft patches as possible villians because
Microsoft is known to put out faulty patches now and then, and picking
up the latest batch was the only thing I could remember doing about
the time I started seeing this. That doesn't mean I know for sure
they caused this problem, I'm just speculating. The error message is
so totally useless, doesn't even give me a place to start looking or
an indication of what program or process was making the "pure virtual
function call". But if this goes away the next time Microsoft comes
out with a patch, I guess we'll know......... ;-) In the meantime,
it's like flying with a bomb in my plane; you just never know when
it's going to go BOOM.
Jim
| |
| L. Mulder 2005-10-24, 7:33 pm |
| Hi Jim,
In that case It was my misunderstanding about this Microsoft message. I
thought it was a message like those Iain Smith is referring to.
And you are correct that some Microsoft patches may cause bags of trouble. I
only install those of which I think (educated guesses though!) I may need
them. I know people who had lots of trouble after SP2. So they just did
their Format and reinstall!! Hope you don't need that. Sorry I can't help
any further. All the best,
Loek
"Jim" <BozAir@REMOVETHISchartermi.net> schreef in bericht
news:9fdql195k5ltvb4qbjpt97c80kq74lnnqf@4ax.com...
Hi,
On Mon, 24 Oct 2005 15:29:49 +0200, "L. Mulder" <lbn.mulder@hccnet.nl>
wrote:
quote:
> My first advice would then be to run a comprehensive
>virus scan with a good virus scanner. And while you're busy anyway use an
>anti-spyware tool as well. Wish you luck and hope for you the solution is
>simpler and that I am wrong!
I suspect you are, but I still appreciate the reply! My "thing" is
computer security, so naturally I'm running the latest and greatest in
anti-virus and anti-spyware programs (1 anti-virus, 1 firewall and 2
anti-spyware programs). The critical patchs I was referring to were
the ones Microsoft finds it necessary to put out almost every month
(about the middle of the month) - they came direct from Microsoft, not
from some other vendor. And in addition to the scheduled scans, I run
manual virus and sypware scans frequently (it's something to do when I
get bored).
I mentioned the Microsoft patches as possible villians because
Microsoft is known to put out faulty patches now and then, and picking
up the latest batch was the only thing I could remember doing about
the time I started seeing this. That doesn't mean I know for sure
they caused this problem, I'm just speculating. The error message is
so totally useless, doesn't even give me a place to start looking or
an indication of what program or process was making the "pure virtual
function call". But if this goes away the next time Microsoft comes
out with a patch, I guess we'll know......... ;-) In the meantime,
it's like flying with a bomb in my plane; you just never know when
it's going to go BOOM.
Jim
| |
|
| That error seems to be pretty bad. A "pure virtual function call" is
something that never should happen (hence illegal). It's hard to explain,
but there's some type of software incompatibility within your windows
environment.
Does it give you any options to "Debug"?
Mike
"Jim" <BozAir@REMOVETHISchartermi.net> wrote in message
news:vu8ol15igptspjavrjr78qa0ad2s8p3ckh@4ax.com...
quote:
> Hi,
>
> HISTORY: I've had this computer for almost a year and so far it has
> performed flawlessly. I can max out most of the FS04 setting and
> still get 20+ FPS except in very dense scenery areas. The few
> problems I have had always turned out to be due to scenery file errors
> I had made (tried to use old macro's with FS04 scenery I made and they
> were not compatable) - which were quickly resolved.
>
> PRESENT: The silly thing has gone nuts (started just after I
> downloaded and installed the latest "critical" Microsoft patches).
> Six times today I got the following error and FS04 stopped dead:
>
> Runtime Error
> R6025 - pure virtual function call
>
> I Googled this and found nothing that helped, especially from
> Microsoft (their answer was nothing but gibberish - to me, anyway).
>
> I have done nothing to cause this to happen, to the best of my
> knowledge. The people who test my scenery as I develop it are not
> seeing this. As mentioned above, the only coincidence I can think of
> are those patches. I can see no event taking place that causes it
> (like entering a specific scenery area) - it appears to happen totally
> at random. It does not seem to happen with any program except FS04.
>
> What the heck, anyone????
>
> Operating system - Windows XP Pro with Service Pack 2
> Computer - Dell Dimension 4700 (2.8GHz, 800 FSB)
> Memory - 1024MB Dual Channel DDR2 SDRAM at 400 MHz
> Video Card - 256MB PCI Express x16 (DVI/VGA/TV-out) nVidia GeForce
> 6800NV6800
>
> (NOTE: computer info was copied from the data sheets, I only
> understand a small part of what it is saying).
>
> Jim
| |
|
| Hi Mike,
On Fri, 28 Oct 2005 21:09:58 -0400, "Mike" <nospam@comcast.net> wrote:
quote:
>That error seems to be pretty bad. A "pure virtual function call" is
>something that never should happen (hence illegal). It's hard to explain,
>but there's some type of software incompatibility within your windows
>environment.
>
>Does it give you any options to "Debug"?
No, the message I sent was all I'd get. However, there has been an
additional "event" since I first posted this message which may shed
some light on the problem.
Two days ago, as I was shutting this machine down for the evening, I
got a similar error message (the first time it's happened outside of
FS9) and this one referenced some kind of problem with Symantic (I use
the Norton Internet Security program - it came already installed on
this Dell computer). While I have always (until now) been a strong
supporter of Symantic products, the one I have on here has given me
constant problems since Day One and Symantic offers no solutions that
work (they don't even seem to want to talk to me). For instance, when
I'm checking my email (I have several email addresses for various
purposes), I can only check one at a time. If I allow my email
program to check all of them, Norton crashes and I lose all of my
virus and Internet protection. I could go on all day about my trials
with this edition of NIS, but that's getting even farther off topic
then I already have, so I'll shut up.
So, since I haven't heard any other solutions, the bottom line
appears to be that my FS9 "virtual function call" crashes have
something to do with the Symantic NIS program. Plan of action is to
just live with it till the subscription runs out, then find something
that works better, made by a company that gives better support.
And I will also start thinking twice before I recommend a Symantic
product to anyone else.
Thanks for all your interest.
Jim
| |
| Quilljar 2005-10-30, 7:35 pm |
| First thing I ever do when I buy a computer with Norton ready installed for
a client, is to uninstall it immediately and download the free AVG from
Grisoft. Never had any touble since. Symantic stuff wants to take over your
computer.
It's the same with AOL. If anyone has AOL installed I refuse to touch it.
Some of these companies want the user to stop thinking and leave all to
hem - aaarrrrgggg !
--
Sincerely,
Quilljar
| |
|
| On Sun, 30 Oct 2005 12:22:28 +0000 (UTC), "Quilljar"
<wykehill-flightsim@yahoo.co.uk> wrote:
quote:
> Never had any touble since. Symantic stuff wants to take over your
>computer.
Yep. I'll check into this when I get a chance. Thanks.
Jim
|
| |
|
|