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
Usually I'd recommend to check your cooling solution - the most frequent cause for sudden shutdowns if overheating due to insufficient cooling, which can happen if the PC builder skimped on the cooling or if too much dust has settled on the fans. But I would have expected the problem to occur with other games as well in that case, I don't think Skywalker Saga is terribly demanding. But did you play the games that you listed after running into the problem with Skywalker Saga? It could be that the root cause of the problem didn't exist in your PC until very recently.
Lego Star Wars is not even 10 minutes in the game...
I already put the game to run as an administrator, reduces the graphics, and still nothing. Sad :(
1- I forced the game to run in Direct x 12,
2- turned off Steam overlay and
3- turned on V-sync.
I don't know which of these actions solved the problem, but I've been playing the game for 3 hours with the graphics at maximum, and no shuttdown. Tomorrow I turn on the Steam overlay and test more.
Man, unfortunately I haven't been playing Lego this week; have you tried keeping V-Sync on?
No software is able to shut down a properly cooled and functioning pc.
Install hwmonitor and make sure temperatures of components are not through the roof when playing.
Clean up cooling parts
Don't man; as you can read right after, I managed to solve the problem (which only occurred in Lego Star Wars) by forcing the game to run in Direct X 12.
As you can see in my timeline, after Lego, I already have more than 20 hours in Days Gone, today I played more than 2 hours of Star Wars Jedi Fallen Order... I repeat: The problem only happens with Lego. I have no doubt it's the game that was shutting down my PC; just wanted to find a solution (and i find).
Im running this game at native 4k resolution with all my graphics settings on ULTRA. Believe it or not, my CPU is a 7 year old Intel i7 6700k that has been overclocked to 4.5 Ghz, along with a EVGA 3080ti FTW3 GPU. Prior to the 3080ti I was running the game at the exact same ULTRA settings in 4k using my EVGA 1080ti FTW3 GPU. But both of my GPUs that I have used with this game have 12GB of VRAM. This game likes a lot of VRAM and 4GB strikes me as being way too limiting for decent performance based on my experience with this title.
I have always had a locked 60fps in all areas of this game, including the Droid Factory and Ewok Village. I am outputting my PC to my SONY XBR 55" 4k TV. Once I made the two changes I mentioned above to my .exe file way back in April of last year, the game has never crashed on me since, and frame rates have always been a rock solid and locked 60fps to my 60hz SONY XBR TV/Monitor. (V-Sync has always been ON)
Yes, you have a point. But in this kind of situation we expect performance problems (like FPS drop, delay in loading textures...) you shouldn't turn off the whole PC! I believe it has something to do with Direct X and some processors.
Direct X could also be playing a role to some degree, but between that and a VRAM under capacity issue, I have my money on your 4GB of VRAM not being enough to run the game using whatever settings you are attempting to use.
The obvious fix is to either upgrade your GPU to a card with at least 8GB of VRAM, or run with much, much lower graphics settings than you are currently attempting to run with right now.