November 9, 20178 yr I have been using P3D V4.1 exclusively but it gives me CTD for unknown reason, no error message, no windows event was recorded (in most of the cases), that was with default airplanes and third party as well, had same issue with P3D V4. I searched the internet for a solution and read somewhere that memory mode XMP could cause such a problem, went to my BIOS and switched memory mode from XMP to (AUTO). I have tested P3D for a week now with all scenarios that I used to fly (had to be long time flight, not less than 2 to 3 hours in general, or let us say P3D had to be running for long time, with some take offs and landings) and everything seems to be working just fine. Noticed two things though and I think it’s a normal; 1- There is a new spar short stutters. 2- Lost couple of FPS with memory in AUTO mode. Now, is it a memory module defects or P3D coding optimization problem? I really can’t say since I don’t have another memory module to try out, therefore I will leave it for someone else to determine that if they have same issue and extra memory module to swap for trouble shooting. I wrote this post trying to help folks like me with same issue, and to extend my thanks to the unknown (at least to me) original guy who brought this fix to the community. happy flying. Ali A. MSFS on PC: I9-13900KS | ASUS ROG STRIX Z790 MB | 64GB DDR5/6000MHz RAM | ASUS TUF RTX4090 OCE | 1TB M.2 Samsung 990 Pro (Windows) +2TB Samsung 990 Pro for MSFS + 2TB Samsung 860 EVO SSD for DATA | EK-Nucleus AIO CR360 Lux D-RGB CPU cooler. HP Reverb G2 VR (occasional use) | LG-45GX950A-B 5K 5120X2160 monitor | Tobii Eye tracker 5 | Logitech sound system 7.1 | VIRPIL Controls (Joystick + thrust levers + rudder pedals) | Windows 11 Pro.
Archived
This topic is now archived and is closed to further replies.