Gears 5 mini survey for those who do and do not have issues

Mini survey for affected users, prefer it if you do not reply to comments, leave that up to nvidia staff.

Some of this information can be obtained in the Help > System Information section of the nvidia control panel, others will require a tool such as Aida64.

GPU Name: Refer to vendor documentation or the sales receipt
Vbios version:
Device ID:
Graphics Clock:
Memory Data Rate:
Have you ever run the NV UEFI firmware update?:

HDMI or Displayport:
or
VGA/DVI adapter from HDMI or Displayport:

Refer to tools such as aida64 for the following if you do not already know.
Panel Manufacturer:
Model:
SKU:
Resolution:
Refresh Rate:
Colour depth:
Gsync Type: Native / Compatible

Did you provide feedback previously?:
If yes, run dispdiag.exe and save the data to the desktop, then email the output to driverfeedback@nvidia.com with the mail address provided to the driver feedback survey.

Have you tried the game again via a Clean startup by using MSCONFIG to disable non-microsoft applications?:

Do you experience a CTD or hardlock?
If CTD, is there a visual anomaly on screen at the time the crash occurs?
If hardlock, is the audio still working in the background, is there garbage on screen?

Lets get @ManuelG some additional info that the driver survey doesn't cover

 

@Darren Hodgson you're a good case here for the not having issues camp, even though you did with rtss running at first.

 

by that time playing Blairwitch.....

 

no problem with Gears 5 and afterburner.

windows 10 pro 1903
RTX 2080ti

 

Only completed campaign zero issues.

windows 10 pro 1903
GTX 1080ti

 

what drivers did you guys use?

 

Latest 436.30

 

I'm startin to think the issue for those who keep experiencing it with rollbacks, is the dx12 update in the recent CU causing issues with overlay injection caches that various software use, apparently GPUTweak uses one too - or the dx shader cache itself, one user resolved it with disk cleanup.

 

Absolutely no issues, been playing since September 5th 9PM. 435.15 and 436.30, RTSS, Windows 10 1903.

 

The GW502 error, which only seemed to occur during the realtime cutscenes and never during actual gameplay, went away once I excluded Gears5.exe from RTSS 7.2.3 Beta 3. This error was just a game crash to the desktop and did not cause my system to reboot or anything annoying like that.

The game has been running great since with no other issues to report. The flashing textures during cutscenes was also fixed with the v436.30 WHQL game ready driver.

I haven't tried re-enabling RTSS since installing the v436.30 driver but since the game has its own FPS statistics overlay there isn't much need for it (and screenshots can easily be taken by pressing the Windows Key + PrtScn keys.

 

No issues with 436.30 but getting way more performance on fast ring 440.52, 10 more fps in some places, its allowed me to mostly max out settings at 4k60 with only some minor drops at into the wilds section with the sled, 55+ here and there. .30 dropped to the 40s in the same area. Both drivers had stutter with dynamic resolution placed at 60fps, none with out butter smooth. Evga xc ultra 2080ti +100 core +1000 mem 380w bios.

 

dynamic res stutter is not a driver issue unfortunately.

 

I'm having slow textures loading, or sometimes they don't load at all. Graphics gets really bad. Tried changing different settings, but still the same. FPS is great, no problem with that. Had the same problem in Gears 4, finished the game, but never solved the issue. Tried different drivers, but not helping. It is really starting to be a pain in the ass. Can someone help out? Thanks in advance.
My specs: GTX 960 2GB, Ryzen 3 1200 @ 4,00GHz, 12 GB DDR4 @ 2400MHz.

 

Thats caused by unreal engines Texture streaming and your cards framebuffer being such a tiny pool that it has to dump and pull them from disk rather than being able to cache them.

Borderlands 2 was known for the same issue.

 

Tnx... So, no way for me to fix it... Smhh