Advice on FS2002 blue screen crash

[Guest]

Hi guys. Have joined the forum for some help hopefully. Whilst flying in FS2002 my computer crashes with a blue screen and then restarts. The Microsoft error reply was device driver problem.Spec of my machine is:Athlon XP2400+MSI K7N2G-ILSR nForce2 motherboard512mb memory128mb nVidia nForce2 graphics.Windows XPI have been to the nVidia website and downloaded the latest driver and updated DirectX.Anybody got any ideas ?

[SteveLewis 0]

You probably don't want to hear this but the only way to correct this is to completely reinstall FS2002. I had similar problems as did others. I tried everything and nothing worked except to completely, 100% reinstall. You can copy over some of the folders but the reinstall will correct register errors.Others may chime in here.:-waveSteve

[Guest]

Another means is 3rd party software like "fix-it". Many of these have programs to find and correct registry errors, among others, that work better than what Microsoft supplies. HOWEVER, some work good on some versions of windows, but not others. This is a matter of finding the best one for your system. I run systems from MSDOS3.0 up to Win98SE and various Linux, and Unix, and I have not found any single software program set that works well on ALL. Sometimes even the same OS on different hardware needs a different program for system maintainence!!!

[Guest Toni Rauch]

It is possible that you might be able to highlight what's causing this.In your Programs menu in XP, go to Accessories, then System Tools, then system Restore.Chose a date a short while back to reset your computer to, before it started crashing when you use FS. Then, one by one, re-install every item you've put onto your system since that chosen restore date (FS-related or otherwise), until it starts giving you problems again. In this way, you should discover the offending software or add-on without having to start 'building' FS all over again (very useful if you have a lot of add-ons!).Hope this helps,Toni.

[Guest Barney1]

Is this a 'new' problem? If so, try to remember when it first happened and what if anything had you altered in the way of soft/hard ware? Is this a result of recently upgrading video drivers, for example. If so, d/l a set of older drivers from Nvidia and experiment. I also ran into a similar problem after upgrading the Direct X version and then installing 'newer and better' video drivers. Since the Direct X is permanent, I was reduced to going backwards in video drivers until stability was restored.I've found that the 29.42 seem to work just fine; but your mileage will probably vary.