Jump to content

Kolbuddy

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 New Car Smell

Gaming Setup

  • Platforms
    Steam
    Linux
  • Peripherals
    Keyboard
  1. Kolbuddy

    [PC] Crashes after the latest update

    @ChrisGrovesMCM Are you guys tracking the crashes on PC as well? It looks like y'all got a fix out for Xbox. Just curious if PC is getting some attention as well.
  2. Having similar issues on a Ryzen 5 1600. Game worked perfectly without a single crash before the update but I have a lot of crashes now For me the crash happens during the game launch for most of the time. Rarely do I even get to do a race and even when I do, sometimes the game crashes during the race as well. Oh well....
  3. After the latest update, the game intermittently crashes to desktop with segfaults. Before the update, things were absolutely fine and I did not get even a single crash but this update must have messed with something. Here are my specs: Ryzen 5 1600 OC'd to 3.8 GHz Nvidia 1070Ti with r415_77 driver. OS: Windows 10 Pro Build 16299 Nothing on the PC has changed before and after the Game update from both the HW and SW sides. I've attached the export of the crash dump files in the bug here. Since the crash looks like a segfault inside grid_dx12.exe and both Nvidia and AMD people have been experiencing these crashes, I'm pretty sure this cannot be due to the graphics drivers and has to be a bug in the game code. Some info from the crash dump file opened in VS 2017: Unhandled exception at 0x00007FF7E27A3B1B (Grid_dx12.exe) in crashdump.dmp: 0xC0000005: Access violation reading location 0x0000000000000000. occurred. Null pointer dereference? I can't get more info out of the dump file (unless you guys want to send over a debug build / pdb file as well 😉 ) Some more observations that might help with the debug: This seems timing related. I am able to avoid the crashes if I do not skip the intro scene and do not wait for racenet to connect. The above hack/workaround alas only works intermittently. WIth the above hack I can mostly get into a race but I've had crashes during the race itself. Since I seem to have a consistent repro setup, I was thinking of performing the following experiments to see if it helps narrow down the repro scenario : Modify the CPU / GPU clocks and check the repro rate because this seems timing dependent. Were there some perf imporvements on the CPU side with this patch that could be exposing the bug on my HW? Update GPU drivers (highly unlikely that this have anything with the bug because of the above guesses). I'm currently too lazy to do the above experiments but IF you guys don't have a consistent repro of the issue on a PC in your QA labs, let me know. I'll try these experiments if it'll help you guys rootcause the issue. Also could this be related to the crashes PC players have been facing before the update as well? I haven't checked the HW setup of the other crashes but perhaps you guys could see if there's some pattern over there? EDIT: If anyone else is hitting similar crashes to desktop do "Like" this report. Seems like this is how Codies prioritize their bugs. hardware_settings.zip
×