20,741
edits
System Crashes: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
So if you are running a modern OS (such as any more recent version of Windows, Mac OS or Linux) and running FlightGear still affects overall system stability in one way or another, something is likely very wrong with your hardware or software setup. Things specifically to look out for include: | So if you are running a modern OS (such as any more recent version of Windows, Mac OS or Linux) and running FlightGear still affects overall system stability in one way or another, something is likely very wrong with your hardware or software setup. Things specifically to look out for include: | ||
* insufficient power supply (make sure that your power supply can handle all your hardware, especially graphics cards!) | |||
* insufficient free system resources (memory, CPU or GPU power) (see [[Hardware Recommendations]]) | * insufficient free system resources (memory, CPU or GPU power) (see [[Hardware Recommendations]]) | ||
* OS/driver issues (graphics/sound) | * OS/driver issues (graphics/sound) | ||
| Line 10: | Line 11: | ||
* faulty RAM, CPU or mainboard | * faulty RAM, CPU or mainboard | ||
* computer viruses | * computer viruses | ||
If you do experience system crashes or so called "blue screens" (on windows), you'll want to increase the FlightGear [[log level]] and have all output be redirected to a file, so that you can later on inspect the file and check for suspicious warnings or error messages. | If you do experience system crashes or so called "blue screens" (on windows), you'll want to increase the FlightGear [[log level]] and have all output be redirected to a file, so that you can later on inspect the file and check for suspicious warnings or error messages. | ||