Інсталювати 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 (в’єтнамська)
Повідомити про проблему з перекладом
Game didn't used to crash this bad, but since one of the patches it an everyday thing.
Then next time I started it applied a patch, and I haven't been able to get any substantive playtime without a crash since. I've got a pretty low tolerance these days for the fiddling people do posting 15 step guides to try and make the game work. Either a patch properly fixes it or this purchase will be a waste.
As a start if you really want a solution post the following:
CPU and OC status:
GPU and OC status:
GPU Driver Version:
Memory and Memory Frequency:
OS:
I've also found the game can become unstable, resulting in crashes to desktop, at high frame rates - if you are regularly rendering at above 150 FPS or so then either enable V-Sync at a refresh rate of 144Hz or less (ideally with VRR) or use a frame rate limiter and see if that helps.
"If your CPU can't calculate Pi correctly, you are not fit to spread managed democracy."
Download y-cruncher: http://numberworld.org/y-cruncher/
Extract to a folder
Right-click the y-cruncher.exe file and create a shortcut
Right-click the shortcut, click Properties and add this command at the end of the shortcut in the Target line (after the quotes):stress -TL:1441 VT3
Run the shortcut!
If y-cruncher randomly closes or reports errors, your CPU is calculating Pi incorrectly. It may be pretty much instant, or it may take close the duration of the test (24 minutes). But, this is much less demoralizing than playing a 40 minute game just for the CPU to give HD2 the middle finger right as your extract from the game 😭
⚠️ Try to watch the window closely at ~22 minutes as the test will complete at 24 minutes. If it finishes successfully, it will simply close (no log or anything). If you miss it finishing, and aren't sure if it closed because it finished, or because it crashed. Check %USERPROFILE%\AppData\Local\CrashDumps for Kurumi.exe crash dmps (On Intel processors... different CPUs run different exes. They can all be found in the bin folder of y-cruncher.) If you have dmp files from Kurumi.exe... it crashed.
In rare cases, these crashes can be caused by RAM timings, but in most cases, this indicates a CPU stability issue. On to some fixes!
https://www.reddit.com/r/Helldivers/comments/1awow3j/crashes_in_helldivers_2_have_a_13th_or_14th_gen/
I never had issues before this week. It's almost unplayable. I hope they sort it out, great game but when you play for 20 minutes and crash before extraction a few times, you feel pretty defeated.
Intel® Core™ i9-12900KF Processor
OS
Windows 11 Pro 64-bit
System Board
ASUS TUF GAMING Z690-PLUS WIFI D4
System Memory
32GB DDR4-3600
Hard Drive
1TB NVMe Solid State Drive
Video
NVIDIA GeForce® RTX 3080 Ti 12GB PCI Express
Sound
Realtek 7.1 Surround Sound High Definition Audio CODEC
LAN
Intel WiFi 6 AX201 Wireless B/G/N/AC/AX/Bluetooth
LAN
Intel® Integrated 2.5Gb Ethernet
Software
ESET Internet Security Trial and Microsoft Office 365 Trial
Power Supply
750 Watt 80+ Gold Modular Power Supply