安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Ehm...
First you misunderstood completely what I am saying:
I said that high level software can't brick your hardware, not that sudden shutdowns because of faulty hardware or drawing too much current through a PSU that isn't supposed to be used like that can't.
Second:
The "80+" certificates are related to the efficiency of the PSU, not safety features like surge protection.
Third:
The "Extreme" VRAM usage claim is just wrong, and anyone can look at that for themselfs in the task manager even.
And even if that were the case, it would use the normal RAM and even harddrives as buffer memory necessary to run the process, which should result in insane framedrops/performance drops and not system shutdowns or hardwarebricking...
I installed this game tonight, and the 'out of video memory' happened to me during the initial 'loading shaders' screen. Which is ridiculous as my PC could run ten of these games simultaneously side-by-side without running out of system or video memory.
- I have a RTX 4090 with 24gb of vram and 64gb of DDR running with a i5-14600kf @ 5.8ghz all p-cores and 4.4 e-cores with 50x ring. DDR5 @ 6400mhz xmp cl30. Stable as a rock at less voltage than stock. Doesn't hit 75c in cinebench r23 or other long stability tests. maxes out 150w. Using latest bios. yada yada. Stable as a rock and cool as a cucumber.
To fix it, I reset my 4090 card core+memory to run at default settings in MSI Afterburner. Then held down 'ctrl+windows key+shift+b' on the keyboard to refresh the video driver. The game then loaded through the shaders and went to menu no problem. Yet it almost used 22gb of vram during this and less than 12gb of system ram.
However, once it get to the menu at 4k highest settings and locking to 120 fps Ultra settings my graphic card is using 30-35% maximum usage and only 70 watts of power. With less than 14gb of vram used and about 10gb of system ram.
My system is completely stable yet, the only crashes have happened with that error messages during first time initial 'shader loading with the new 5.x Epic game engine. It seems to want to use as much memory as possible, but Windows likes to keep some for itself. So, it terminates it.
This has happened in 1st time loading Shaders for STALKER 2, Wukong, Indiana Jones and now this. Just have to get through the first time launch and then there is no issue.
Also, for this game If I left the game play uncapped with vsync off and no fps cap my gpu would then usage 100% with 450w power and get an unnecessary 500-999 fps. Fortunately, this game defaults with vsync on. Otherwise, if people go afk while its loading the shaders then come back an hour or 3 later it is not good. Bit like revving your car in the red line for way too long. That is, if you have a 4090/5090.
As someone has written before:
New games are always a good test if your hardware is properly configured (in a real-life hardware sense).
Either you have an unstable overclock or a powerdraw spike shuts your PSU down.
The fact that you already confirmed that limiting your frames helps completely removing the issue, confirms that as well.
Only because multiple people have the issue, doesn't mean that it still can't be their PCs at fault.
Yes, Marvel Rivals could be more optimized and less heavy on the hardware for how it looks, but that doesn't mean that the game "damages PCs".
If it was the PC why did disabling AA fix it? If it was the PC why is it the only game that crashes? It’s because it’s the game, a stress test should also cause a crash but it doesn’t.
My bad, I must have mixed you up with a different guy of a different discussion about the same topix then.
Have you tried disabling XMP/Curve optimization and the undervolt you are running with the game being framelocked then?
Again, different games/programs have different workloads, resulting in different behaviour.