Well I deleted my old FS9.cfg file and allowed FS2004 to re-create it with default settings....When I tried a flight, the PC now restarts without any prior notice (i.e. OS crashes but DOES NOT show the Blue DOS screen of death and just restarts).. as if someone presses the restart button on the PC casuing it to restart immediately (and not safely).....

"I have read somewhere that there is a way to stop the auto reboot when at the Blue DOS screen when the computer chrases but I can seem to find out the method.... Would you happen to know how to stop the auto reoot so that I can find out what caused the crash?".....I think you achieve this by doing the following:Right click on 'My Computer'Click on 'Properties'Click the 'Advanced Tab'Click on 'Settings' under 'Startup and Recovery'Then, under 'System failure' make sure 'Automatically restart' is unchecked.Mike

Ah thank you! :DOnly now it crashes without the blue DOS screen!! But it will help if and when it crashes to the blue screen again!Thanks!

I tried yet another flight and the sim1.dll error occured.... I might have forgotten to mention that I use FSManager (for the diagnostic purposes) and I have heard it leaves invalid *.air files but cannot find these files....Is there anything that can cause this crash since I have replaved the sim1.dll for a known working one...

Scooby, hate to say this but chasing crashing Dlls won't help you. You've had enough different "culprits" just since beginning this thread to make Windows' error reporting virtually meaningless.I hate to see you wasting your time tracking a phantom software issue. If you Primed using the 3 tests in SP2004 without problems then I would suggest you next focus your attention on the power supply.Any info on that item?Regards,Greg

I am not sure what you mean by "Primed"??WEll it truns out that it's a bit hard to get hold of a decent power pack above 500W in my country suprisingly... Will have to keep searching!Your're right about having enought trouble with the original problems though...... But in all this I have not yet gotten a crash due to g2d.dll though I am not sure if thats because it has been fixed somehow or if all these other problems occur first before the g2d.dll error can kick in!I really don't have any clue as to why this is the ONLY game that is giving me this much grief!! All other games that I have runs flawlessly!!! Yes I know that FS2004 finds bugs in your PC that you never knew existed but it should have a better way of dealing with it rather than just crashing!!!! (Sure hope thats been improved on FSX!)

I am not sure what you mean by "Primed"??I was referring to the three tests within SP2004. SP2004 is essentially Prime95 wrappped around a user friendly GUI. So when a system can run the application without experiencing any errors it is said to be "Primed" or "Prime Stable". It usually takes many hours to "prime" a system (successful overnight runs for each test).Have you established that the system is Prime stable?Greg

Sort off... I have completed the small and large FFTs (left it for about 7-8 hours each) but I have to do the blend tests...Will report on those results in another 7-8 hours! :DBut other than that the other tests were succesful....

Well... I have a bit of a mixed result from the Blend Tests.... After running it for about 7 hours 30 minutes, it still says it is on Test 1 (is that normal??) and that there were no errors... So I stopped them (I have running 2 simultaneously as it suggested if you have Hyper Threading) and restarted my PC normally.... EXCEPT during boot up on the restart it crashes to the Blue DOS screen!! The only error on it was some STOP error.... Then I have to restart again.. but all went fine after the 2nd restart....

>>The only error on it was some STOP error....<< Hi Scooby, such stop errors are very helpful to track eventual shortcomings. So, write it down next time (incl the digits and letters). Then punch that line into a search machine and you'll likely receive a couple of hints in which direction you'll need to look. Concerning the power supply, you'll probably not need 500W. Maybe look for quality instead? You might be surprised to hear that only a very small amount of systems require PSUs of 400W and larger. Nevertheless, before going for a new PSU, I would suggest going down the 'STOP-search path'. My personal guess is either bad RAM or some basic (bios?) settings. Apart from Prime, another very useful system test tool is MemTest86+ from memtest.org. Case you give MemTest a go, make sure you let it run at least 10 passes. I know, another time consuming analysis... :-) Hope this adds to thoughts, good luck and kind regards Jaap

Will do Jaap! Didn't know anything useful could be interpreted from those Stop errors!Lol.. *yea* (<-- sarcastic) another long running test! Oh well.. I have actually used memtest... but it was only for one pass i think.... I'll run it for longer tonight!

FYI, the assumption with memtest, is: 1 pass without errors = 90% that your RAM is healthy (TYRIH) 10 passes w/o errors = 99% TYRIH 100 passes w/o errors = 99.9% TYRIH etc... Stop errors will often indicate a tendency, i.e. whether troubles are driver or hardware related. Good luck Jaap

LOL Thanks! Yea ok I will try 10 passes (I don't think I will be able to bear not being able to use my PC if it runs a 100 passes!! :D )FYI Got another Stop error shortly after trying again...STOP: 0x0000007F, 0x0000000D, 0x00000000, 0x00000000, 0x00000000) (<-- If that means anything to you!!)Ok now I know after I tell all you guys, who spent time to help me, this that you will probably hunt me down and kill me for making SUCH a NOOBISH and DUMB mistake... I am telling you this because I think I have stopped all the problems that I have mentioned here (and probably more) (or so I hope since I have not had any problems after i did the thing i mentioned below and ran FS2004 for about 40minutes; which is early for testing purposes but late in the fact several errors would have occoured in this time by now) *touches wood* *crosses finger* *does anything that prevents the errors from coming back just because I wrote this*... Well what I did was..... I removed the two 256mb RAM memory which where of a different company (same type though, DDR) and different speed RAM..........!!!!I realise I should have checked this right from the start but Windows recognises both memory (2x 256mb Kingston PC3200 RAM, 2x 256mb SpecTek PC2700 RAM, both running at dual channel) and all my games don't crash because of it (except FS2004... I knew it was notourious in crashing at the simplest of things..... but this......!!!)*Hangs head in shame*, *long sigh*.... well I geuss it should be alright now.. but I will carry out a 2-3 hour flight just to see if it works for now...... ... Now gotta hunt for another pair of 256mb Kingston PC3200 RAM.....

Well I just completed a 1 hour 30 minutes flight with no problems!! Seems like the memory was the problem after all!!I have to thank all you guys sooooo much for helping me out A LOT!!I really appreciated it!! :D :D :D

Fantastic news and well done! You were right all along - it WAS hardware related.I performed a quick Google search and you might be interested in this (a bit like closing the door after the horse has bolted, I know, but reassuring nevertheless):http://aumha.org/win5/kbestop.phpScroll half way down the page to: 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAPThen click on the 'General Causes' link. You will note one of the causes is 'Mismatched Memory Modules' which appears to be what was behind your problem.We can all relax now...LOLMike