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
Открой Просмотр журналов событий, попробуй найти ошибку в момент отключения.
Попробуй изменить графический драйвер на более старую версию, удалив его через DDU
In the mean time, since system shutdowns shouldn't be happening when a game crashes, do some troubleshooting to ensure you aren't having some instability somewhere that the game is revealing. OCCT is a decent test suite, but not as intensive for certain issues as I would like for narrowing down problems.
Assuming all of that checks out, you almost certainly have a rock solid build, and your hardware is likely not the issue. You can run these tests for longer in the off chance a voltage instability is happening only intermittently or what have you (some people run them for 24 hours) but that's not strictly necessary and especially in the case of FurMark is probably unwise in terms of the life span of your part.
Generate a DxDiag report and attach to a crash report here: https://support.halowaypoint.com/hc/en-us/requests/new and be sure to include details of all the steps taken above and a copy of any event log information found in Event Viewer about the crash.
Makes ya think.