Razi Posted January 28, 2019 Posted January 28, 2019 (edited) I've been running DCS for many years on Win 7 Pro, but recently got around to installing Win 10 pro, not upgrading, but a clean install on the exact same hardware. With only mouse/keyboard/logitech 3D Pro attached and a clean DCS OB install, DCS CTDs after a few minutes on any instant action I've tried. Through GeForce Experience, I updated the graphics driver prior to installing DCS OB. Crash log attached. I just tried a complete reformatting of my 2nd SSD (recreating the partition to make sure permissions were set properly) and another clean install of DCS OB on it, also completely removing the DCS OB directory in Saved Games. No change, still CTD after a few minutes.dcs.log-20190128-153403.zip Edited January 28, 2019 by Razi
Razi Posted January 28, 2019 Author Posted January 28, 2019 I rolled back the nVidia graphics driver to the previous version (417.35) and got 30 seconds into F/A-18C Free Flight (Caucasus) before another CTD.dcs.log-20190128-163022.zip
Razi Posted January 28, 2019 Author Posted January 28, 2019 As a follow up. I'm going to pin this problem on bad overclock settings. I've make changes to them and that has solved the CTD issues it appears.
Raags Posted January 28, 2019 Posted January 28, 2019 Please let use know if the OC was the issues. Having some of the same issues. I am using XMP profile that is giving me a little OC. Thanks.
Razi Posted January 28, 2019 Author Posted January 28, 2019 Please let use know if the OC was the issues. Having some of the same issues. I am using XMP profile that is giving me a little OC. Thanks. I'm still testing, but so far it does look like OCing has something to do with it. I'll share more after further testing.
FragBum Posted January 28, 2019 Posted January 28, 2019 Just as an aside I have had to throttle back some OC settings namely RAM speed, even though the settings seeded okay with tests. FWIW latest nvidia driver seems fine for me win10. Control is an illusion which usually shatters at the least expected moment. Gazelle Mini-gun version is endorphins with rotors. See above. Currently rolling with a Asus Z390 Prime, 9600K, 32GB RAM, SSD, 2080Ti and Windows 10Pro, Rift CV1. bu0836x and Scratch Built Pedals, Collective and Cyclic.
Razi Posted February 1, 2019 Author Posted February 1, 2019 After quite a bit of testing, my specific crash related problems were in fact due to overclocking. I rebuilt my rig due to a crash that corrupted windows system files and while I was at it, I upgraded to windows 10. During the rebuild and because of the earlier crash, I backed off my OC settings, but never tested them, just assumed that more conservative settings would be fine, but DCS routinely crashed at these OC settings. So I stress tested and played DCS for week with stock settings, conservative OC settings, and my original more aggressive OC settings. Turns out DCS seems to be somewhat sensitive to OC settings. I had no crashes with stock settings. Frequent DCS crashes with the conservative settings, though no crashes in benchmarks and stress testing. Lastly, my aggressive OC settings are actually pretty good, no crashes in DCS or benchmarks/stress tests. So I think the problem with my conservative settings was that I backed off the voltage too much and for some reason DCS became sensitive to this. Anyways, I consider this problem solved for me. Hope this helps someone else.
FragBum Posted February 1, 2019 Posted February 1, 2019 That is interesting, glad to see your sorted. :thumbup: Control is an illusion which usually shatters at the least expected moment. Gazelle Mini-gun version is endorphins with rotors. See above. Currently rolling with a Asus Z390 Prime, 9600K, 32GB RAM, SSD, 2080Ti and Windows 10Pro, Rift CV1. bu0836x and Scratch Built Pedals, Collective and Cyclic.
Recommended Posts