Hello My FSX randomly crashes to reboot, meens that screen turns black and computer restarts.No overclocking and temps are CPU not over 65 °C and Video Card not over 75 °C.Ram was tested and no errors dertected. FSX.cfg tweaked with Bojotes tool.Uiautomationcore.dll fix already applied. DX10 preview mode active.Runing FSX with ASE and REX2. FSUIPC is the newest version.The problem occurs especially when Is use fps intense planes like the PMDG JS41 or PMDG MD11.The computer interpretes the crash to reboot not as BSOD, cause no dump file is created.Here are my specs: CPU: Intel Core i7 920 C0 (HT on)Board: Aus P6T DeluxeGPU: Radeon HD 5870RAM: 12GB DDR3 RamOS: Windows Vista SP2FSX installes with SP2All hardware drivers are up to date. I hope you can help me with this annoying issue...

I'm now getting a BSOD: PAGE_FAULT_IN_NONPAGED_AREA STOP 0x00000050 (0xFFFFFFFF856A4000, 0x0000000000000000, 0xFFFFF80002895882, 0x0000000000000005)I have already scanned my RAM with MEMTEST and executed chkdsk /f /r to make sure the filesystem is ok. There were no errors found in both tests.The command sfc /SANNOW to ensure that the systems servises are not corrupt did also not solve the problem.FSX is the only application where this BSOD oocurs. I have no idea what to do

There is a hotfix at Microsoft that might solve this issue - http://support.microsoft.com/kb/939720 . You might try Googling 'Vista 0x00000050' and see if one of those scenarios/solutions fits your specific system. You should download and install the freeware program Blue Screen Viewer (Google Blue Screen Viewer), run it and see what driver or program is shutting down your system. Most likely it is "Ntoskrnl.exe" and that means your memory settings in the BIOS are not set properly. Even though MEMTEST finds no errors, it doesn't mean your memory settings are correct. Most likely the DRAM voltages are incorrect. You should have a line in your BIOS stating Memory Frequency. Make sure this setting is correct or put it on Auto if you are not sure. For me, the ntoskrnl.exe problem was fixed by placing this setting on Auto. Best regards,Jim