I am trying very very hard to refrain from using explicitives. To put it simply Windows 2000 AMD 3200 GeForce FX 5950 Asus nForce 2 Delux. I have only had it for 1 or 2 months so far and in those 2 months acording to my computer's error log it has crashed 79,539 times!!!!! It is driving me insane, I had the same problem with Vue D'espirit only not as big, I have all of the latest drivers critical updates etc, my computer has no viruses or anything of the sort and this is very very anoying, I know this has happened to some one els before and I want to know how to fix it.

Try to disable OpenGL. Often some graphic drivers are the reason for crashes. I use a Radeon 5700 Pro and nearly never have crashes. I say nearly, because Windows (XP) sometime crashes too:-) Also tell us what kind of messages (screenshots please) of messages you get when Pro crashes. Guitta

I have a W2K, AMD 1G, GeForce FX (forget the version) and I have few problems with Vue Pro. I left it at the first update...have not updated since then. I have Open GL disabled, as it really slows down my scenes even though it does work.

For some reason it will not let me take a screen shot of the error, I have no idea why but the error reads "has generated errors and will be closed by windows" for some reason I have more errors after ive been using windows for a while, if I restart and strangly if i do not close any of my startup aplications such as MSN or AIM after it has notified me if I have any new mail or do anything at all outside vue it crashes very rarley. I was actualy suprised by how little it deos.

Well that helps ! ?? I think the error log would have been more usefull than this. Well upgrade it turn off open gl turn off all background apps that you can and try again. If you expect us to help you must provide us with usefull information. This picture is useless, we are ready know it's crashing.

Try renaming Vue4Pro.eon to Vue4Pro2.exe (or something similar) and run that instead. Supposedly, it provides more information regarding the error, at least in some circumstances.
I actually had similar problems some months ago (drove me nuts), but discovered that I had a faulty memory circuit...well, rather the machine had. Try a memory tester, just to make sure.