Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Game freeze =/= PC freeze
the first is most likely due to a software issue, the second a hardware issue
Did you run memtest as well for your RAM?
I've ran stress tests like OCCT and Y-Cruncher for both my RAM and CPU and didn't get any errors.
So no dedicated RAM test.
In general it is hard to think of a PSU issue, considering you already using a 750W one. But we cannot outrule random hardware issues - so yeah, even the PSU might have come defective out of the box.
But a PC freeze is still unusual, from my personal experience. Normally it is more likely for the PC to emergency shutdown or crash/loose power entirely if it is the case.
Based on your description alone the prime suspect would be a RAM issue. But there are also some parts missing in your story, such as whether you restarted your PC between the tests, did it with a clean boot and so on.
Personally I do not think much of OCCT, knowing that app well. A lot of PC gamers have been mislead by the summary of information again and again when troubleshooting.
Y-Cruncher I see acceptable for checking the CPU, but completely unnecessary.
Monster Hunter Wilds is an awesome game for troubleshooting hardware issues, as its nature of being a console-port demands some very stable system environment.
For the moment I would recommend to take out the RAM and use the alternative slots - sometimes a simple loose contact can cause the symptoms you described.
Also disable XMP/EXPO on your mainboard / BIOS, before running the memtest.
Last but not least you could share a DxDiag report for checking the details. Personally I recommend to you the usage of ISLC from the maker of DDU.
Use it like as seen here
https://images.steamusercontent.com/ugc/33317948943644100/23B5914E18C8F0CAB915353E548390AF8292DB9B/
Use 16384 instead of 32768 and make sure that your pagefile is set to a >>fixed<< 128 GB as minimum and upper limit to ensure virtual memory stability.
Last but not least, go to your game's folder and search for shader.cache2 <--- that file you delete, and make sure you delete it every time you test the game - otherwise it will falsify your results when testing the game.
Really?! Is the card that sort of a monster?!!! Scary...
But yeah, capping the framerate is a good idea to stabilise the power usage.
Also revert RAM settings to default.
If it runs you can enable EXPO again, but I suggest to disable any CPU OC. Most games do not neet it and it just ads under 1-5 FPS with huge instability and consumption/heat.
The game burns both GPU and CPU at the same time and 750W PSU may be likely issues.
I do not think so, my system RTX4070TiS, Ryzen 7800X3D just consumes 200-350W with WHWilds. So not likely the PSU draw.
Just disable PBO and OC, this has nearly no benefit for FPS on modern systems. EXPO is fine and ads some FPS up, if your RAM can handle it.
RTX4070TiS recommend 750W, Here are
RTX 4090 1000W
RTX 4080 Super 850W
RTX 4080 850W
RTX 4070 Ti Super 750W
I would say 750W is quite a bare min but OP didnt state its GPU.
I just built a 9800x3d system as well and have had something similar a few times.
with no PBO I was booting up MH wilds and my system would become completely frozen on launch requiring a hard reset to fix it. I'm not sure if its buggy bios or GPU drivers, But after updating to a beta bios and reinstalling chipset drivers I haven't had it again. The only thing I changed in bios was turning WIFI and audio off.
I can't find the thread again but i saw something about some of the newer nvidia drivers causing system crashes for some people.