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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.
You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash
interesting. is this the same kinda behaviour as part 1? the day 1 shader compiler had the memory "leak" for 2 weeks. discarded memory pileup. a windows thing, afaik. i have the "janitor" running all day. page file of 8 GB should be enough safety for a craptop setup, right?
Pin the thread or mark it so that other players also see it; I've seen several threads with the same problem and no solution was found anywhere.
By the way, I got my first crash after 3 hour session, not sure what cause, after enabling virtual memory game become much more stable with 13-14 Gb VRAM usage.
"Windows itself also relies on the page file for certain system processes, like memory-mapped files, which don’t always scale with physical RAM."
"Windows is designed to use virtual memory as part of its memory management strategy. It preemtively moves less-used data to the page file, freeing up RAM for active tasks. Disabling virtual memory can force the system to keep everything in RAM, potentially leading to less efficient memory allocation and, in edge cases, slowdowns."
R7 3700X, RX 6700XT 12GB, 16GB RAM, M.2 SSD's, Windows 10, everything maxed out, No Upscaling, No FrameGen, FSR Native AA, 1080p Vsync @60FPS no problem. (screen goes no further than 60Hz)
Main Rig at home:
R9 7900X, RX 7900XTX 24GB, 32GB RAM, M.2 SSD's Windows 10, everything maxed out, No Upscaling, No FrameGen, FSR Native AA, 4K Vsync @60FPS no problem.
Probably could get a lot higher FPS but my HDMI Receiver only has 4K 60Hz troughput.
Get crashes at random on my main rig, but hardware monitor doesnt show anything weird...
If you got Xbox Gamebar installed just pust "Windows" key + "G" to bring up the Gamebar in Game, Pin the Hardwaremonitor somewhere its not covering a part of the HUD, Click on VRAM and watch, if its the VRAM filling up you see it no mather what, even if the whole system has frozen you can still see the last recorded data and the graph.
I bet its not VRAM or RAM but something else as wen mine crashes there is nothing weird giong on, i dont see a increase in CPU, GPU, RAM, VRAM or a drop in FPS untill the actual crash happens.
It crashes my GPU driver so bad that HDMI Audio no longer works (Dolby Athmos)
I have to go into the Audio settings, lower it to DVD quality, and than put it back on Dolby Athmos to get it to work again.
Could be a HDMI Audio issue, but... in 2 crashes the conversation went on with a frozen screen that went to black before the conversation stoped.
Most of my crashes happened wen a conversation was going on or a cut scene started.