Hi all,

 

I get CTD's seemingly randomly in FSX but I have no idea how to get rid of them! I found a guide to produce error reports so I've attached them accordingly!

 

Further information is...

 

core i5 760 @ 3.5ghz (stable, tested for many hours with other games, benchmarking, stresstesting etc)

4gb DDR3 ram @ 1333ghz (Good quality, Mushkin with decent sized heatsinks)

GTX 560TI 1gb - latest drivers installed.

 

Windows Home Premium 7, 64bit, fresh install as of about 2 days ago with all updates and drivers installed prior to installing FSX.

 

 

My updates are (and were installed in this order with restarts and running the sim between each install).

 

FSx, Acceleration, UTX Europe, GEX Europe, REX OD, NGX 737, FS2Crew NGX

 

also using an x52 Pro - TrackIR was not enabled at the time of crash.

 

 

I hope I've provided enough info to be of help (Also, UI automation core has been put into my main FSX folder which has significantly reduced the number of CTDs I experience)

 

Thanks very much for your help in advance :) I hope I can finally get this sim working properly!

Hey all,

 

Maybe this sounds weird but....I disabled Windows Defender which was using active defence and scanning and also ran FSX in admin mode and the CTD's stopped!

I get CTD's seemingly randomly in FSX but I have no idea how to get rid of them!

 

Please look at the post just below yours with subject: StackHash_0a9e.

 

Best regards,

Jim

Much appreciated Jim,

 

They've stopped happening now - Could this have been the cause...?

 

My memory was set to 9,9,9,9,25 (it had automatically gone up to that with an OC) h owever I manually set it to 9,9,9,9,24 (factory defaults) - since then + killing windows defender, its stopped crashing. Does memory timing being out by just one point cause that kind of issue?

 

Thanks

Does memory timing being out by just one point cause that kind of issue?

 

I doubt it but just the fact you went into the BIOS and then saved and reset the BIOS may have fixed it. I suppose you could test it by going back into the BIOS and change it back to 25. The fix I directed you too in this forum was not an adjustment of the memory settings in the BIOS but changing virtual memory settings to 'system managed size'. It seems to have worked for the individual who had the same problem (well, the same faulting module) as you.

 

Best regards,

Jim