Forum Discussion

ClosetLumberjac's avatar
2 years ago

Dirt Rally 2.0 - Guaranteed CTD or BSOD After <20min

Base Info:

  • Platform: Steam 
  • Country: United States
  • Place where the error was encountered: During race (Time trial and campaign. Different maps/cars.)
  • Kind of error: Various. The most common is different versions of "Access Violations". No performance issues at all outside of the crashes. Even in the moments before a crash. Both CTD and BSOD occur suddenly with no warning after about 5-10 min and always in a run. If the game only CTDs, then my whole system runs poorly after until a restart (if it doesn't BSOD before I do so).

System Info:

  • CPU: Ryzen 5 - 7600X
  • GPU: RTX - 4090
  • OS: Windows 10 (KB5034122)*
  • MB: Gigabyte B650M Aorus Elite AX AM5
  • RAM: 4 x 16GB Corsair Vengeance DDR5-6000 CL40
  • HD: Samsung 980 Pro 2TB M.2 NVME
  • PSU: Corsair RM 1000x (1000W)
  • Monitor: Samsung Odyssey G95SC
  • Equipment: Fanatec CSL DD Base, P1 V2 wheel, and pedals.

*Rolled back from KB5034203. That Windows update is what when the problems started.

What Has Been Tried:

Most troubleshooting was done in both OS versions. I will use an '*' to indicate anything only performed after the OS rollback. (List is relatively in order, but many things were done numerous times, or repeated under different circumstances.)

  • Verification of game files.
  • Disabled all overlays and ended all non necessary apps/services.
  • Uninstalled/reinstalled game.
  • Updated OS and Windows drivers. (*Network and *monitor drivers were uninstalled / reinstalled at least once.)
  • Rolled back OS using a system image.
  • Updated and rolled back GPU drivers.
    • Drivers were pulled from Nvidia,
    • DDU & reinstall were performed in safe mode each time.
      • I used the Nvidia install tool (clean install) on 2 separate attempts, but ran DDU for the same change after each one resulted in continued failure,
      • *One attempt was made allowing Windows to install the drivers (*post OS rollback).
  • Verified current version of firmware (wheelbase and monitor).
  • Frequent sfc scans and chkdsk repairs. (All have come back clean.)
  • *Ran the .exe in Windows 7 compatibility mode as Administrator. Launched directly and through Steam.
  • *Attempted various graphic settings:
    • Used both 120 and 240hz
    • Reduced all graphic settings to lowest values.
    • Ran game in windowed, full-screen, and border-less. (One crash in fullscreen was preceded by the game suddenly switching the resolution to windowed at 720p.)
  • Verified hardware is seated properly.
  • 4 passes of MemTest came back clean

Other Info:

  • GPU/CPU running at under 70C. (exact numbers not known due to disabled overlays, but my fan curves are set up in a way that I can get a rough idea based on noise level. 70C is one of my bigger 'attention-grabbing-steps'.)
  • Only one other game (Forza Horizons 5) has given me similar issues. (FH5 would always hang and CTD without error though.)
         Sensing a theme here EA...
  • All other recently played games have ran flawlessly at max settings. These include:
    • Assetto Corsa
    • Control (w/ RT)
    • MGSV-TPP
    • NFS Heat
    • NFS Unbound
    • Cyberpunk (w/ RT and some reduced settingsPT)
  • I've attached the screenshots I thought to grab of the errors I've gotten from Dirt's crash reporter tool. (Most crashes were reported.) Unfortunately, I haven't been able to record the BSOD errors, but I can pull reports from Event Viewer or any other Windows log that may be helpful.

I may have attempted some other miscellaneous tweaks that aren't listed, but I normally don't have to keep a documented list of my troubleshooting attempts....

No RepliesBe the first to reply

About Other EA Racing Games

Join other players in celebrating classic EA Racing games. Loyal Real Racing or Burnout Paradise player? You're in the right spot.1,244 PostsLatest Activity: 3 hours ago