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
I mostly crash exiting the game and see the UE-Alabama box pop up
I think I was too paranoid now and am feeling more positive about the game running for sure thank you!
It will look like this:
</CallStack>
<IsCrashed>true</IsCrashed>
<Registers></Registers>
<ThreadID>[some crash ID number]</ThreadID>
<ThreadName>[cause of crash]</ThreadName>
</Thread>
-The ThreadName/Cause of Crash is sometimes something ambiguous like:
<ThreadName>EXCEPTION_ACCESS_VIOLATION</ThreadName>
But UE5 doesn't know that it ran out of memory until after it's getting told NO by Windows. Which leads to my next point.
One of the most common causes I see for persistent crashes is running out of memory. In that same file you can check it out by searching for "memorystats" and you should see something like looks like this:
<MemoryStats.TotalPhysical>34281295872</MemoryStats.TotalPhysical>
<MemoryStats.TotalVirtual>140737488224256</MemoryStats.TotalVirtual>
BAD<MemoryStats.PageSize>4096</MemoryStats.PageSize>
<MemoryStats.TotalPhysicalGB>32</MemoryStats.TotalPhysicalGB>
BAD<MemoryStats.AvailablePhysical>0</MemoryStats.AvailablePhysical>
BAD<MemoryStats.AvailableVirtual>0</MemoryStats.AvailableVirtual>
<MemoryStats.UsedPhysical>0</MemoryStats.UsedPhysical>
<MemoryStats.PeakUsedPhysical>0</MemoryStats.PeakUsedPhysical>
<MemoryStats.UsedVirtual>0</MemoryStats.UsedVirtual>
<MemoryStats.PeakUsedVirtual>0</MemoryStats.PeakUsedVirtual>
-First BAD, he didn't have his page file set to System Managed so he only had 4gb
-Second BAD, he ran out of RAM
-Third Bad, he ran out of page file....bc it was only 4gb lol
In this case, you would win search for advanced systems settings>under performance clcik settings>go to advanced tab>under virtual memory click change>
from here if you only have one drive you can just click on "Automatically manage paging file size for all drives"...if you have multiple drives and they're all equally as fast, you can do the same; HOWEVER, if, like me, you have a really fast one and a kind fast one and then two really slow ones, go to your main gaming drive, or your fastest one, make sure you have ~size of your RAM as free space, and then click System managed size and click set. This should help!! Restart and try again.
https://www.youtube.com/watch?v=YE27Ic37hQI&ab_channel=TechFixIT
For XBox PC and Steam
That can't happen.
I would try looking into reshade if you want to change the way the colors are.
I use Nvidia filters for all my games that support it. Its better than reshade.
It really can't. Get mad at me if you want. I build computers and diagnose them for a living.