Now *THAT* makes a LOT of sense. I was wondering where he was on the forums on Steam. That's 100% why my bug report when without response. I thought maybe you guys were inundated there with bug reports from the recent release, or it was passed over accidentally. Speaking of which (don't know if I posted this already)... 184.108.40.206 is still crashing and burning for me, randomly during play or editing. Even in safe mode, where I only have my map in levels (but not necessarily when I am using my map, it can be the stock maps), but no other mods. Will be updating the BIOS to AGESA ABB, the system chip-set drivers, and exploring some other options such as swapping video cards between the Ryzen 3700x here and the Intel 4790k, and changing the video driver 'reset' timer within Windows registry to see if it's locking up the driver for a few seconds (it was hitching a few times). Nothing is 'over clocked' here, it's mostly all stock except the XMP on the memory. Will be double-testing system stability but so-far the only issue is 0.17.x BeamNG (16.x would run all night even with heavy traffic in the traffic app tool). Will also be copying the installation to the 4790k (my last machine) for testing to see if it crashes there, too. That will rule out Windows version (that one has 7 this one has 10) and hardware failure. It also has an AMD video card. Changing settings here on the new machine from high to medium had no effect. In response to error: AMDKMDAP has crashed and been successfully restarted by Windows (event viewer applet in control panel, Windows 10 Pro). GPU not responding dialog box in Windows 10 Pro, latest AMD driver, RX 480, also happens in July 28th (or a few days before) driver version. Beamng crashes to desktop. Support ticket 57652 from version 17.0 or 220.127.116.11 (forget), still valid on this version for the same error. Originally posted on Steam here: https://steamcommunity.com/app/284160/discussions/2/3185654583887106683/ Posted under BeamNG.Drive > Discussions > Bug Reports forum. It happens with the stock game while playing, randomly, can take an hour, can take minutes. It also happens while editing my map. Mods not required, doesn't seem to make any difference. IMPORTANT: No Windows WHEA errors are logged while this is happening, that's something to watch for on Ryzen systems, especially with PCI-E 4.0. EDIT: 0.16 using any maps or my maps does not crash. 0.17.x using ANY map crashes after a random amount of time crashing the video driver out (tried two different versions).