A couple months ago I posted about a freeze issue that mostly happened on flights more than 5 hours. In the past I was able to do 14 hour flights without this problem. But after it started ocurring I was not able to do flights over 5 hours without a freeze up which would totally lock up the computer. The only way to use the computer again was a hard restart.

 

I tried many things and thought I had the problem licked but it kept coming back. Yes I do have the UIautomationcore.dll fix so I knew that was not the problem. Anyway after going 6 weeks without a freeze I am confident I have finally tracked down the problem.

 

The issue for me was the windows page file. I fell into that trap where people were talking about getting better response and faster load times with windows by doing this and that with their page files. I did find a way to make windows boot up 50 percent faster. I have 3 hard drives with Windows on C: Video and Photo utils on D: and FSX on E:

 

Since D: drive is not used at all when I am Flying, I thought well I will just put the page file over there. My theory was Windows could access it's files from C: The Page file could be accessed from D: and FSX could be accessed from E: . So while I was flying all 3 drives could be used. 3 drives is better than 1 right? I did notice windows booted up a lot faster and so did FSX.

 

However this seems to have been causing the freeze. With no page file on the Windows drive I believe on long flights after a time (even with 8 gig of memory) that windows would run out of memory and freeze up.

 

When I changed the page file setup to allow Windows to manage the page file for all 3 drives automatically the freeze up problem went away.

 

So I think the moral of the this story is. Windows really does know best. Let it automatically manage it's own page file and leave it alone to do it's thing.

Hopefully its solved your ctds for now on