[SOLVED] "The Last of Us - Part 1" crashes at startup ?

[kerberos_20]

Hi, installed this game, one time it launched but around 30% shader compiling it freezed and crashed to desktop, eventviewer shows 0xc0000005 error code
after that game crashes right after coin animation
tryed wiping dx shader cache and radeon shader cache without any success, game still shows 30% shader compiling progress then crash, eventho it was reseted
uninstalled it, installed it fresh and about same behaviour, but just it crashed on 26% shader compiling progress now and refuses to even enter main menu

can somebody analyze memory dump for me? quick look it shows nullpointer (NULL_CLASS_PTR_READ)
https://1drv.ms/u/s!AipaiVibgFNwgZVtN6DDiY5xXa6dRQ?e=ls2nWY

 

[boju]

TLOU update should have fixed that. Haven't bought the game yet, waiting bit longer.

Things you can try
Run system file checker and verify game files.
Have you limited pagefile by any chance?
Is resizable bar supported on your system and is it on? Maybe try disable it.

Try disable any background running apps or utilities under startup items in tm.

What's your system specs?

 

[kerberos_20]

TLOU update should have fixed that. Haven't bought the game yet, waiting bit longer.

google search shows that im not only one with crash on coin

Run system file checker and verify game files

reinstalled few times (as game can be played on first try after reinstall), sfc/dism are clean

Have you limited pagefile by any chance?

nope, i did set it once to 32768 - 65535, but no diff
game eats around 22GB RAM/12GB vram with mixed high/ultra settings @ 1440p, so it shouldnt need to touch page file at all,paged pool shows 700MB used in task manager

Is resizable bar supported on your system and is it on? Maybe try disable it.

re-bar is supported and enabled, id rather not disable it as i get stutters in some games when its disabled

Try disable any background running apps or utilities under startup items in tm.

nothing runs in background, just the usual microsoft services

What's your system specs?

windows 11pro x64 - 22H2
ryzen 7 3800x
32GB DDR4-3600
radeon RX6800 16GB
seasoninc focus plus platinum 750watt

Haven't bought the game yet, waiting bit longer.

graphics looks fine, cant find yet any visual corruptions (patch 1.0.2.0)
game can be played during building shader - no stutters, fps is limited to 60fps, cpu howers around100fps/GPU seems to be doing slightly better

cpu usage looks funny, right? 1 full core load lol

building shaders is currently at 46%...but it takes hour to jump by few percent up (doesnt matter if youre in game or just let it sit in mainmenu)..shader compilation seems to be limited to single CPU thread,no clue whats takin so long...it should take 10-15min max? currently its 3hrs for those 46% and dunno how long it takes before it crashes again and oce it crashes game become unusable until game wipe+reinstall :/

 

[boju]

Im hoping compiling shaders just need to be done once. Try disable resizeable bar anyway to see what happens if this round of compiling fails. Suggesting it wasn't meant to be a permanent thing, can always turn it back on. Besides, if this was something dev's overlooked you could be a hero.. help those who help others.

As for resizeable bar stutters, whether related or not, i dont get that with it on or off. So this could be an underlying system issue the game is also exposing due to seriously poor optimisation. Reason me asking about pagefile because looking up your debug errors seems to point to something like that.

Anyways, blame the game and probably best give it another month.

 

[Frag Maniac]

@Metal Messiah, PLEASE with all due respect for your attempting to research problems people are having with games, IT IS NOT the same as actual experience playing them. Therefore it makes zero sense to give advice on such things if you've spent no time playing the games in question.

The fact that OP makes mention of attempting to play without waiting for shaders to compile makes it rather obvious he is not taking the proper steps to assure it plays well. I've played on patch 1.0.1.0, 1.0.5.0, 1.0.6.0, and now 1.0.2.0. The latest patch 1.0.2.0 added a CLEAR warning if you attempt to go in game before shaders compile that you might encounter performance issues if you choose to do so.

I NEVER had a crash on the coin twirl page on ANY patch version, and only had ONE crash in now two and a half play throughs, which was on version 1.0.1.0, and likely caused by my having the game minimized for some time while doing something else. I say this because the 2nd playthrough it did not crash at all, but I'd also not minimized the game at length.

Patch 1.0.2.0 is the largest patch file yet, about 8 GB. Aside from many various bug fixes, it addresses streaming so that the CPU is used less. My guess is the patch size is huge because it adds roughly 10% more texture files to the game so it doesn't have to do as much texture unpacking while streaming them, which would obviously be easier on the CPU. So I'm saying I think they made the total texture files about 10% bigger, but from what I've seen it reduces CPU usage by about 20%.

I've also noticed the frame rate window seems to have tightened. It used to run between 55-60 FPS for the most part for me, regularly dipping to 45 FPS. Now it pretty much stays between 55-60 on patch 1.0.2.0.

Please though MM, stop suggesting refunds on a game you've not even spent any time playing! I'll add that the video I posted recently showing that TLoU Part I plays well even on patch 1.0.6.0, is currently my most viewed video with over 250 views in just 5 days. WHY, well I can't help but think it's because a lot of players whom haven't bought the game want to know if all the performance complaints have merit, and IMO many of them don't. More people need to stop jumping on the performance bashing train and pay attention to what those whom are having plenty adequate performance are saying.

 

[Frag Maniac]

cpu usage looks funny, right? 1 full core load lol

It's understandable given what you're doing. What's "funny" is expecting everything to be rosy when you choose to play WHILE shaders are compiling, which is something the game CLEARLY warns you not to do now on patch 1.0.2.0.

And these are likely the scenarios for most on Steam whom have claimed the game to be a performance disaster, very likely it's mostly problems that arise when people don't have a CLUE how to game on a PC!

It would be nice if threads like these were automatically diverted to a forum called Noob Gamers Problems. A forum showing examples of what can happen when the Problem Exists Between The PC and the Chair!

 

[kerberos_20]

It's understandable given what you're doing. What's "funny" is expecting everything to be rosy when you choose to play WHILE shaders are compiling, which is something the game CLEARLY warns you not to do now on patch 1.0.2.0.

odd, this is after fresh install shader compiling on first try freezed and crashed on around 30%, on second try it crashed while in game on roughly 26%, keep in mind that after install game work until it crash, then impossible to enter game without reinstalling

game is smooth to play even during shader compiling...you could see from mine posted image that both cpu and gpu have reserves for compiling shaders


btw updated radeon drivers which mentions optimisations for last of us and shader compiling finally finished without crashing (4hrs caching shaders and 6 reinstalls xD)

but im not entirely sure if radeon drivers solved that, switched to no DRM version to move away from steam (rune)

 

[Frag Maniac]

odd, this is after fresh install shader compiling on first try freezed and crashed on around 30%, on second try it crashed while in game on roughly 26%, keep in mind that after install game work until it crash, then impossible to enter game without reinstalling

game is smooth to play even during shader compiling...you could see from mine posted image that both cpu and gpu have reserves for compiling shaders


btw updated radeon drivers which mentions optimisations for last of us and shader compiling finally finished without crashing (4hrs caching shaders and 6 reinstalls xD)

but im not entirely sure if radeon drivers solved that, switched to no DRM version to move away from steam (rune)

Well it's common sense to use the latest driver, or at least check for a driver version made for the game. And if shader compiling took that long in game or even in menu, clearly either something with your PC is messed up or you have TONS of stuff running in the background.

At any rate, this is what you get these days when you offer advice from much experience playing a game, more gibberish that makes no sense and a down vote. This is what I get for chatting with casuals that don't know games as well as they think they do.

 

[kerberos_20]

And if shader compiling took that long in game or even in menu, clearly either something with your PC is messed up or you have TONS of stuff running in the background.

windows was running in background
there was just single worker thread for shader compiling,...so just single threaded game in 2023 , looking through steam people says that its supposed to be multithreaded to get ~15-25 min compile time...
in UE5 you can atleast create more worker threads in configs, but here in this game i couldnt find any settings to create more worker threads

 

[Frag Maniac]

...looking through steam people says that its supposed to be multithreaded to get ~15-25 min compile time...

That was the compile time for me, regardless of patch version. It was closer to 15 min on patches 1.0.6.0 and 1.0.2.0, but there's no reason the 8 core, 16 thread CPU you have shouldn't be using more than 1 thread. I mean that's more cores/threads than my 8700K has.

I get the feeling there's something you're not telling us, because this just doesn't add up.

 

[kerberos_20]

That was the compile time for me, regardless of patch version. It was closer to 15 min on patches 1.0.6.0 and 1.0.2.0, but there's no reason the 8 core, 16 thread CPU you have shouldn't be using more than 1 thread. I mean that's more cores/threads than my 8700K has.

I get the feeling there's something you're not telling us, because this just doesn't add up.

i could make some video, what do you wanna see?

 

[Deleted member 2838871]

building shaders is currently at 46%...but it takes hour to jump by few percent up (doesnt matter if youre in game or just let it sit in mainmenu)..shader compilation seems to be limited to single CPU thread,no clue whats takin so long...it should take 10-15min max? currently its 3hrs for those 46% and dunno how long it takes before it crashes again and oce it crashes game become unusable until game wipe+reinstall :/

Seems like you have something else going on.

I purchased and installed this game last night... a week after doing a full system wipe and CPU/GPU upgrade.

Building shaders took 30 mins total... and the game has run flawlessly for the first couple hours at 4K Ultra 60 fps.

 

[kerberos_20]

Seems like you have something else going on.

I purchased and installed this game last night... a week after doing a full system wipe and CPU/GPU upgrade.

Building shaders took 30 mins total... and the game has run flawlessly for the first couple hours at 4K Ultra 60 fps.

could be some hardware combination which that game doesnt like, hardware unboxed did video and he waste more time on shaders then me xD

 

[Frag Maniac]

What patch version are you on now? They just released a 1.0.2.1 hotfix, but it's mainly for mouse look stutters.

 

[kerberos_20]

What patch version are you on now? They just released a 1.0.2.1 hotfix, but it's mainly for mouse look stutters.

1.0.2.0

i did some digging with process hacker and while game folder has included dxcompiler.dll library, but its not used, instead its using d3dcompiler_42.dll which is not included in game folder library, so i added this file into game folder from other game (horizone zero dawn) and now compiling is fast while there are multiple shader workers running

now its compiling under 30minutes

guess i can close it now

 

[Frag Maniac]

Why would you have to take the d3dcompiler_42.dll file from another game, since you said "instead it's using" that already? And where exactly in the game did you put this file?

 

[kerberos_20]

Why would you have to take the d3dcompiler_42.dll file from another game, since you said "instead it's using" that already? And where exactly in the game did you put this file?

because games includes those files if they make some changes to avoid using default microsoft libraries
ive put it in root folder where executables are

 

[Frag Maniac]

because games includes those files if they make some changes to avoid using default microsoft libraries
ive put it in root folder where executables are

Sys32 also has that file, and I copied and pasted it into the game directory and it made zero difference.

 

[kerberos_20]

Sys32 also has that file, and I copied and pasted it into the game directory and it made zero difference.

is your radeon drivers using it?

 

[Frag Maniac]

is your radeon drivers using it?

As you can see in my sig, I have an Nvidia GPU, not AMD.

 

[kerberos_20]

As you can see in my sig, I have an Nvidia GPU, not AMD.

yup, thats why youre using different compiler then mine gpu driver

 

[Frag Maniac]

yup, thats why youre using different compiler then mine gpu driver

Well compiling shaders was never that slow on my Nvidia GPU, so I'd blame that on AMD.

 

[kerberos_20]

Well compiling shaders was never that slow on my Nvidia GPU, so I'd blame that on AMD.

yea i guess, amd released fix for it in Adrenalin 23.4.3

 

[Frag Maniac]

yea i guess, amd released fix for it in Adrenalin 23.4.3

Turns out Jedi Survivor has a MAJOR performance problem that many were hoping would be addressed with a day 1 patch (but wasn't). It requires a MASSIVELY powerful CPU or a GPU even as good as the 4090 will sit at 33% utilization (on a AMD 5900X), and that's even at just 1440p.

I mention this because apparently a 7900XT utilization is more like 83% with similar CPU due to AMD drivers requiring less CPU overhead.

I can't believe even dev teams like Respawn are falling into this horrible PC port trap even on UE 4, an engine they are plenty familiar with by now.

Back on topic though, TLoU Part I just got a 1.4 patch, which most seem to be saying finally fixes the performance and stability issues some were having.

I really don't get why publishers are so anxious to force their dev teams to adhere to unrealistic deadlines instead of making SURE their titles are ready for launch. They should know it can cause launch disasters that make many want to not trust preordering or buying at full price within a month or so of release, which obviously affects their cash flow.

 

[Deleted member 2838871]

Turns out Jedi Survivor has a MAJOR performance problem that many are hoping will be addressed with a day 1 patch. It requires a MASSIVELY powerful CPU or a GPU even as good as the 4090 will sit at 33% utilization (on a AMD 5900X), and that's even at just 1440p.

It wasn’t quite that bad.

Well after having controller connection difficulties that ended with me having to update firmware I just played it for an hour and it definitely didn't suck.

The stats in the upper left is pretty much where I was the whole time... 70-80% GPU... roughly 40% VRAM.... 20% CPU...

So where's the bottleneck?

I had everything at Ultra (Epic) with RT on... this is a pretty small sample size so gonna check it out more later and see how the performance is... but so far it wasn't bad at all. I had one frame drop when I was climbing up a wall... but after exiting and reloading the game the 2nd time it didn't happen. So I dunno.

That was the only time frames weren't at 60 or within a couple fps. All the "OMG it's running at 30-40 fps" that I saw in online reviews today didn't happen to me.

Haven’t had any problems with Hogwart’s or Last of Us either.