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
Description: Upon exiting the game by any means (Selecting "Quit" on the main menu, using alt+f4, using "end task" in Task Manager) from anywhere (main menu or elsewhere in game), the screen will freeze. The mouse can be moved and some programs, such as VLC, will continue to run. The only way to end this is to hard-reset the computer. As a note, this has happened to me on both the OpenGL and DirectX rendering.
Hardware: I am using a 2-monitor setup on an ASUS ROG GL752 laptop.
Intel i7-6700HQ 2.60GHz
16GB RAM
Windows 10 Home, Ver 1803
GTX 960M
Kind of a game-breaking/fun-ruining bug that I've never seen in another game. Really hoping it gets fixed.
Intel i7-6700HQ 2.6GHz
16 GB RAM
Windows 10 Home 64-bit (version 10.0.17134.165)
NVIDIA GeForce GTX 960M + Intel HD Graphics 530
EDIT: I've been quitting the game at the start of every run to try to avoid a crash (or at least try to not lose save data), got one anyway on the third of the day. However, I seem to have managed to stop the slow-crash in progress. Opening task manager I started killing processes as soon as I saw what was happening, of the multiple Steam processes one of them seems to have averted the crash by being closed. Unfortunately I have no idea which one seems to have done it.
CPU : Intel Core i7 Quad Core (2.6GHz)
GPU : Intel Iris Pro 580
RAM : 16GB
Thank you for your feedbacks, this issue has already been reported and we're working on it. :)
The crash now causes the BIOS to have to "scan and repair" my M.2 drive. Uninstalled.