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
If you're not getting past this there's something up with your setup by the sounds of it.
What's your full system specs?
32 gigs of RAM
i7-8700k
4TB drive
After I posted this I was going to move the files to another SSD to verify. But i decided to run the validation files again, and for whatever reason it, it downloaded another 1.9 gigs, and then I was able to get past the screen.
So it looks like something was corrupt in my steam files, and the first time I did the file verification, it came back clean (this was in between patch 1.05 and 1.06), so I dunno if something was different but now it seems to work so far (i got to the menu and let the shaders do their thing.
It has aomething to do with the game and not the shsthem requiremenys, does anyone know how to fix this ?
"Hey Guys, I just fixed my problem with this exact same thing. For me I looked in windows event viewer at the crash and it said Razer Chroma was the issue. I just deleted the file it listed and now it works perfectly fine. Highly recommend trying the event viewer to find whats actually failing.
On the left side of the viewer, Windows Logs->Application. It will then bring up a list of all Application events both successful and not. You should look for a Red exclamation mark that indicates an event error (not all of these are cause for concern, so just because you see one on something else doesn't mean anything is wrong with that). Find TLOU in the events and look for the error for when it crashed. Click on it and it will give you details at the bottom of the Event Viewer. In those details you should see some explanation of what failed and "Where" it failed. That is how I found the file path that was causing mine to crash. Yours may be different but its a damn good place to look. If you need any help past that I'm not sure what else to do. Good luck and let me know if this worked for you!!"