What Games are you playing right now? [2]

blackroseMD1 said:

I edited my post to mention it, but I'm on the latest driver. This one and the one before it have both thrown this error, and they're both the 400 series drivers. Seems like the RTX ready drivers don't like SotTR on my system for some reason. I haven't tried running the game in DX11 mode yet. I may do that and see if the crashes still occur. If they don't, I'll just roll back to the last 399.xx driver, because I'm not willing to give up DX12 and it's mGPU tech that gets such great SLI scaling with this game.

Oh boy, a bad day on the gaming thread. I haven't had a crash (yet) with 411.63 but I ran the benchmark and then only played for about half an hour which is maybe not long enough. I assume you have MFAA off in NVCC, right? It's said to cause issues. I was looking at the Geforce forums and the only one talking about SOTTR crashes also had the problem with the 399.xx drivers. I think they are discounting his problem to a specific system issue. Wondering if it's SLI related. You should post the problem on the Geforce forums as it's the time now (early after driver release) when Manual G is active over there. FYI, Sora is guessing at fixes related to :

"My suspicion is that all those affected have a singular correlating factor that exists outside of the driver.

Close discord
update to steam beta
install RTSS 7.2beta5

etc. "

specialkone said:

Oh boy, a bad day on the gaming thread. I haven't had a crash (yet) with 411.63 but I ran the benchmark and then only played for about half an hour which is maybe not long enough. I assume you have MFAA off in NVCC, right? It's said to cause issues. I was looking at the Geforce forums and the only one talking about SOTTR crashes also had the problem with the 399.xx drivers. I think they are discounting his problem to a specific system issue. Wondering if it's SLI related. You should post the problem on the Geforce forums as it's the time now (early after driver release) when Manual G is active over there. FYI, Sora is guessing at fixes related to :

"My suspicion is that all those affected have a singular correlating factor that exists outside of the driver.

Close discord
update to steam beta
install RTSS 7.2beta5

etc. "

Alrighty. I'll give it another runthrough tonight and if it crashes again, I'll head over to the GeForce forums and try some of those suggestions by Sora.

blackroseMD1 said:

This one and the one before it have both thrown this error, and they're both the 400 series drivers..

What driver? The one before 411.63 was 399.24, or do you mean the beta and test drivers 411.17-5x leading up the final build?

blackroseMD1 said:

I haven't tried running the game in DX11 mode yet. I may do that and see if the crashes still occur. If they don't, I'll just roll back to the last 399.xx driver, because I'm not willing to give up DX12 and it's mGPU tech that gets such great SLI scaling with this game.

The consensus for DXGI errors for this game - and RotTR - is the DX12 implementations. Disabling DX12 should fix it. Also overlays and overclocks have caused similar issues in the past, that may also be worth checking out. But if using the 399xx drivers works for you then just use them instead. If it ain't broke don't fix it.

Nicely done on the COD Black Ops vid. dude. I remember and loved that part running the gauntlet on that boat. I assume you are practicing for the BFV October 19 release.

PS: the game status crap "objective reached" (important to most gamers) for me as I'm sure you are not surprised is just getting in the way of the all important OSD data. For this game at least (no map display on right) IMHO OSD is better set on the top right.

You're right. I just checked. More bad news.