On two separate fly-ins, toward the end of the flight, my computer has just completely konked out.I have an older compter, and am flying with Flight 1 ATR and FS2Crew.Any ideas on what's happening and how I might correct things?Flights with Radar Contact never have this problem, so I'm thinkingperhaps my computer is just being overwhelmed with all the traffic.Thanks in advance.SluggerP4 2.0 ghzATI 9600 pro1 gig ram

Hi, Slugger,What is the message on your blue screen? The important part is the first two lines, beginning with the word STOP, followed by a hex number followed by other numbers in paren, e.g. 0x0000000A (0x00000002,0x00000038F,0x00000000,0x00000000), followed by an text phrase given_in_words_separated_by_underscores. These lines hold the clue to what failed.Here's an example of how the first two lines on the blue screen might look:Stop 0x0000000A (0x00000806, 0x00000002, 0x00000000, 0x804fd3aa) IRQL_NOT_LESS_OR_EQUALAdditionally, other information given on the STOP screen tell what module or driver is loaded at particular memory addresses. One of the 4 parameters in the paren will have a number that often corresponds to the tabular info on the remainder of the screen. Put the two together and you can often come up with the offending software or driver. It's best to have your digital camera ready and capture this screen, close-up with good resolution. Then you (or someone here) can pick it apart for ya.