Yeah my crashes are random. I’ve tried rolling back to previous AMD drivers but no luck, when it wants to crash it crashes lol
This is getting frustrating. I keep getting this error so I’ve tried…
- Turning down my game settings so my GPU isn’t working as hard. (Didn’t work)
- Turning off overlays (Didn’t work)
- Updating my drivers to the most recent ones (Didnt’ work)
Love Gears 5 but these crashes are so entirely random. I thought they might be brought on by having an overbearing heat load but then one time I launched the game and it instantly crashed the second the Title screen loaded before the head load had even built up at all.
I’m out of ideas at this point honestly and its incredibly frustrating because Gears 5 is such a good title. Going to keep playing it but boy having to fight with the game to be able to play it sometimes is a real bummer.
Demo you’ve tried 3 things apart from the one that everyone is telling people to do that seems to work for nvidia 10xx cards is roll back your driver so give that a go if your nvidia of course.
I understand rolling back drivers would fix until they launch newer drivers with that error removed. In my part tho, I play other games, not only Gears , that’s why I wouldn’t roll back drivers as it messes my other games somehow.
I hope they release a permament fix, fgs.
I’m normally reluctant to roll back but its only necessary to go back to 436.15, which doent break any games I’m aware of for 10xx cards. You can try as many other “fixes” as you like but none will have a permanent effect.
The 436.30 was no doubt targeted at 20xx cards. I will remember when I buy my next card what happened to us 10xx card owners here Nvidia
Well, I can’t play anithyng, the monitor take off and I need to restart it.
For me, the first time that I have the issue was yesterday, Septt 28 2019.
I can’t play matchmaking, only horde and escape modes… its dissapointed that the game sttill with issues after almost one month that the game launch!
hi guys, I have an i4690k running at 3.9GHz, 16GB ram DDR3 and a Radeon X590 8GB … latest Win (Win10 64bit) and Radeon drivers installed … since the snow missions I can’t play for 5-10 min straight without crashing with G502
I noticed that first - not always, or maybe I just don’t notice them - small graphical glitches appear before the crash (textures change colour… etc.)
Still getting GW502 crashes even on 436.15, not sure what to do anymore. I can’t get through more than an hour or two before it crashes regardless of mode. Most crashes are GW502, some just crash without error, and once it hard-locked my system.
GPU: Nvidia 1080ti
CPU: AMD Ryzen 2700X
RAM: 32GB
EDIT: Async compute has been enabled, likely by resetting graphics options to defaults in-game. That was what crashed G4 (aside from being above 382.53) on Nvidia hardware.
So for Nvidia users, check the following to avoid crashing:
- Disable Async Compute in INI settings “%LOCALAPPDATA%\Gears5\Saved\Config\PC” > Open “GameUserSettings.ini” > Ensure “sg.AsyncComputeQuality” is set to 0 (sg.AsyncComputeQuality=0)
- Rollback to 436.15 Drivers.
EDIT2: Game crashed (no error message) even with async disable and 436.15 installed. No idea what to do at this point.
EDIT3: Removed tag from the top of this post. I DDU’d and installed 436.15 again, as well as removing all extra Audio Devices on my system, as I’ve heard about issues with those setup incorrectly. Still crashing somewhat frequently. It may be placebo, but I haven’t gotten a GW502 since the async disable. Only game locking up with no message, and one hard-lock system crash.
EDIT4: Investigating all the Error 51 stuff, per technical FAQ, you want to have windows manage virtual paging file (which I did). However, I’ve observed after playing with this setting that when ticked a paging file was only set for the primary windows drive. All other drivers were automatically set to “No paging file”, and I have Gears 5 installed on my secondary drive. So I’m going to try unticking their recommended setting and instead choosing “System managed size” for each drive individually. Don’t forget to press the “Set” button on each drive if you try this!
EDIT5: Error 51 is occurring when the game is first loaded for me. 10 to 20 of them suddenly appear in the Event Viewer.
EDIT6: Tried moving my game to primary drive from Apps&Features, and setting virtual paging back to how their FAQ suggests (tick the very top box). Restarted PC, verified paging was still setup correctly, launched Gears 5, and still got a flood of Error 51.
EDIT7: Issue appears to be squarely pointing at the “Xvd” Drive which is created (if one does not already exist) on game launch. The drive can be found under Device Manager > Disk drives. This is an Xbox Virtual Disk, and appears to be used for paging.
Interestingly the driver is from 2006? I tried to update the drive out of curiosity with the xvdd drivers in driverstore, but it wouldn’t take.
2 Likes
If you have a consistent crash, on startup or returning to menu, possibly with video lost, with a 10xx card on 436.30 driver then a clean install of 436.15 can likely help - Ive had no problems for a couple of weeks since doing this.
If you get a sudden FPS drop then its worth trying a driver re-install in Geforce Experience selecting clean install.
If youre seeing a different sort of random crash or have a different GPU then maybe some change to a setting will help you, but remember its a random thing and specific to your PC -apart from 436.15 there really is no “Fix”
There is a new nvidia driver 436.48 but Gears does not seem to be listed as fixed in this release.
Just tried it and game still crashes T_T. Reverted back another time to 436.15.
Title Update is out today, but it makes no mention of resolving crashes for PC users (aside from Nvidia + cinematics). This is pretty disappointing honestly, but I’ll be hoping for the best when I get home and test it out.
In fact the Gears 5 issue doesnt appear in the official release notes just in a nvidia forum thread as a continuing problem.
If it was something with a Nv supported title like Control it would have been fixed inside three weeks no doubt.
sadly still present. I’ve lowered settings to medium from ultra and turned off all the advanced options (gtx 1080). Not sure if its placebo but it does seem “less” frequent. But I still can’t play more than 3 or 4 straight matches without the game crashing in between matches.
I find it so odd that it only happens while in the menus. Usually while loading back in the main menu or the next match.
Hello everyone I just got solution which worked for me
I just downgraded the Nvidia driver to 436.15 version
Sign in to Microsoft and xbox.
Turning on the offline play in Microsoft store app
Turning off Game recording
Recommend: At last updated to the Windows latest version
My specs:
Gpu Nvidia 4GB GTX 1050 (Driver version 436.15)
I7 processor
Windows 10 pro (updated to version 1903)
8Gb RAM
Hope this will let you to enjoy Gears 5 without any errors
Setting windows to automatically manage paging file size on the drive which the game is installed is what fixed the game constantly crashing for me (including the 502 crashes).
It was previously set to ‘No paging file’ (I think this was set via samsung drive optimisation). With windows managing the paging file its set to 16384MB and the game hasnt crashed once.
Hope this helps as this game was unplayable before!
i7-4790
16GB ram
Asus 1070 6GB
installed on SSD drive
1 Like
It worked also for me! Thx very much! Now I’m playing with latest Nvidia driver without any crash.
It would be annoying if Samsung (I assume you mean Magician) turned off a page file. If you have 16GB or more physical then the need to page memory to disk is minimal though - this is a technique from the “old days” with RAM memory size smaller than the total prog+data size of running progs - the OS would page out oldest data to disk.
Perhaps they think it would reduce “wear” on the SSD but I would look vary carefully at any automated optimsations made by Magician.
My name is Manuel and I am part of the NVIDIA Customer Care team. Can users who were experiencing crashes playing Gears 5 on GeForce graphics cards comment on whether they have noticed any changes since the Oct. 1st patch?
https://www.gears5.com/whatsup-oct1-2019
“Fixed crashes when transitioning through some cinematics on Nvidia Cards”
Regards,
Manuel
www.twitter.com/ManuelGuzman
There has been absolutely no change at all with the new updated drivers. I just played 1 multiplayer match and got back into the lobby & when it was about to load into another match, it crashed with the same GW502 error.