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
My laptop: ROG Strix G16
That's interesting. A lot of my friends and I had absolutely zero hard shutdowns after doing both of these workarounds. Are you sure that you've done everything correctly? If your answer is still yes, I suggest turning off multithreading in the game settings. It does lower your performance a lot, but it can stop crashes (at least it did before I found this workaround).
I was unsure if I needed to use the forward slashes, I could only get it to work with back slashes:
Windows 11?
my computer is brand new so not trying to play a game that will end up breaking it until the devs release an update.
Until December 30 I was running POE2 with Ryzen 5 5600G integretad graphs (everything on low, obviously) and this problem never happened. Then I got a RX 7600 and this error starts showing up at least once a day, with less then 3hours gameplays. I've done some benchmark and stress test with FurMark2 and Kombuster and it was smooth. I have tried to disable rebar, switch from Direct12 to Vulkan, and it still happens. All the temperatures 73°C tops