Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
tip #7 here works splendidly against memory leak
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
combine it with tip #2
though it is no guarantee that it fixes your issue. I would still try using DDU (tip #1) if you have not done that for a proper reinstall of the graphics card. Something is still odd with it, and the tuning down not helping is worrisome.
https://steamcommunity.com/app/2246340/discussions/0/599646570829331259/#c599646570829340196
I persist with same issue but will try some of these
I wish you good luck. I am still highly irritated why it is so easy for Nvidia card to activate debug mode, but I cannot find it that easy with AMD cards... For Nvidia it is just a simple checkmark in the control panel - but where is it for AMD...?
how can a game be so badly coded that it causes GPU driver crashes and system failures. over the past 2.5 years of owning this PC and dozens of games from indie to AAA titles, not a single one had caused a single driver crash, while this game throws them around like its nothing, and not a word from crapcom either.
I played for ~2hours straight before a new error
Fatal D3D Error (22, DXGI_ERROR_INVALID_CALL, 0x887A0001)
Dxdiag
https://pastebin.com/qXw5mCcz
anything you can glean?
A common trigger for me to crash with d3d errors is to talk to gemma and start looking at different weapons. I will say maybe three out of five times. However overall crashing has improved to 1-2 hours of playtime by reducing textures and switching to AMD FSR3 for whatever reason.
Aside from some memory leak, I cannot see anything unusual. Since you are on Nvidia, try running the GPU in debug mode.
Before that, delete the shader cache / do the game update routine - tip #16 here - if you have not done that today.
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
Running my gpu which is a stock oc variant of the nvidia 4070ti super in “debug mode” from the nvidia control panel puts it at stock normal settings and seems to fix the problem fwiw
Running on i9 12900, rtx4090.
Underclocked using MSI after burner, first had core clock set to -200MHz and memory clock at +0MHz and this was running all good. I have since changed it to -100MHz underclock and it is also running stable for last 2 days.