Ramsay Posted June 15, 2020 Share Posted June 15, 2020 (edited) DCS Crash when launched, Second launch works ok. As title, Open Beta 2.5.6.50793 Steam's DCS World desktop shortcut appears to work but the DCS GUI window never appears. Windows event viewer shows a DCS crash, launching a second time - DCS works as normal. - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2020-06-15T20:01:38.959487300Z EventRecordID 16086 Channel Application Computer DESKTOP-IER00U7 Security - EventData DCS.exe 2.5.6.50793 5ee1e6fc WorldGeneral.dll 2.5.6.50793 5ee1e604 c0000005 00000000000a3544 204c 01d6434fc4e593ce C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\WorldGeneral.dll 13194f2f-475d-498b-9f8b-d7bdb143dd63 Edited June 15, 2020 by Ramsay add various crash dmp that may be relevent i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted June 16, 2020 ED Team Share Posted June 16, 2020 (edited) The crash is reporting a windows file error. C:\Windows\System32\pid.dll try this https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Then run a verify of your dcs in steam thank you Edited June 16, 2020 by BIGNEWY Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Ramsay Posted June 16, 2020 Author Share Posted June 16, 2020 (edited) The crash is reporting a windows file error. C:\Windows\System32\pid.dll try this https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Then run a verify of your dcs in steam I'll do as you say. AFAIK pid.dll is part of direct-X http://battlelog.battlefield.com/bf4/forum/threadview/2955065219594608045/ Edited June 16, 2020 by Ramsay typo i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
Ramsay Posted June 16, 2020 Author Share Posted June 16, 2020 DCS and Windows validated without issue. My older config (i7 860 @2.8GHz, 16GB RAM, GTX1050Ti) doesn't show any similar crashes in it's event log (it's been used to view the occasional track). This new PC has a number of RGB background programs • Gigabyte RGB Fusion 2.0 • Corsiar iCUE 3.29.110 • Razor Synapse 3.5.531.51418 ... and iCUE has a small number of App crashes logged in Event Viewer but is not associated with the DCS events i.e. they differ in time/day and are fewer in number. As I've used Razor Synapse in my old PC, it can likely be eliminated. As it's possible iCUE (or Fusion) is causing an issue for DCS, I'll disable them and monitor the event log for a week or so, before reporting back. i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
Ramsay Posted June 17, 2020 Author Share Posted June 17, 2020 I've excluded iCUE and Fusion as direct causes of the crash. Today's crash/launch failure (pid.dll) was 1st DCS run of the day. IMHO the fact that Steam hadn't been preloaded is likely a coincidence. For now, I'll assume it's PC/hardware specific. i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
discwalker Posted June 17, 2020 Share Posted June 17, 2020 pid.dll is part of the core os, see the details tab in the left click menu; or you can not found if you save the dxdiag to a text file GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
Ramsay Posted June 19, 2020 Author Share Posted June 19, 2020 (edited) The only thing that's highlighted in dcs.log is that the crash occurs at the point that INPUT: Device [Mouse] created deviceId = -1 ... is normally logged. The DCS logo appears ("DCS" in a square) but then goes away and the GUI never appears. It occurs after the PC is started from cold and DCS is first run, 2nd and subsequent runs of DCS work as expected. I've eliminated the Razor software and AFAIK DCS is the only program that shows the issue. • The new PC is on Win 10 Pro 1903, while my older PC (that doesn't show the issue) is still on version 1809* * Edit: I've updated old PC to Win Pro 1909, it continues to run DCS without issue Edited June 19, 2020 by Ramsay Update old PC to see if problem is linked to Windows version - it's not. i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
Ramsay Posted July 19, 2020 Author Share Posted July 19, 2020 Clearing Joystick Calibration Data Fixed the issue ? For Info. The pid.dll crash when first starting DCS seems to have resolved itself after resetting my X52 Pro calibration data. Recalibrate the X52 H.O.T.A.S. axes: RegEdit If your X52 H.O.T.A.S. axes appear to be off-center in the Game Controllers Test Page, the calibration data range might be bad. To resolve the problem, you’ll need to run a Registry Editor (RegEdit) script to remove the entries in the Windows registry, and then recalibrate the data range. https://support.logi.com/hc/en-gb/articles/360023346933 Detail As an unrelated matter, I noted my X52 Pro throttle had a limited range of motion in the Hornet 's control indicator "RCtrl+Enter" and was stopping just short of the Min/Max positions it should have reached. https://support.logi.com/hc/en-gb/articles/360023346933 Resetting the calibration data fixed the calibration issue but also seemed to fix the pid.dll crash - can't be 100% certain as the calibration was reset on the 5th July and the last pid.dll crash was on the 7th July i.e. there's a 2 day overlap but it's 12 days since DCS/pid.dll crashed. Speculation One possibility is that the X52 Pro Throttle needs it's Joystick to calibrate correctly and as I only use the throttle, the calibration data became good when (during testing) I plugged the joystick into the throttle. i9 9900K @4.9GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
Flappie Posted July 19, 2020 Share Posted July 19, 2020 Thanks for your detailed procedure to solve this issue. :thumbup: Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Recommended Posts