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
Discussions Rules and Guidelines
1 
Report this post
We are really sorry to hear about the crashing issues in the game.
After reviewing your DxDiag file, I noticed that your graphics card drivers might be a bit outdated. To help resolve these issues, could you please take a moment to download and install the latest drivers for your AMD Radeon RX 7900 XTX? Here’s how you can do it:
2. After that, you’ll see the corresponding AMD driver. Just choose your platform or Windows version and click Download.
3. Once the installation is complete, make sure to close the game client completely and restart your computer.
4. Your drivers will then be up to date!
• You can find detailed instructions here: AMD Knowledge Base[www.amd.com]
Get back to us when you can.
Regards,
Team17 Support
Thanks for the clarification. We deeply hope the previous steps correct the issue. But will remain pending of you if there are further questions.
tmo97 we appreciate your report on this. Could you please send us your DxDiag information? You can do this by following the steps below:
1. Hold down the Windows Key and press R
2. The Run dialogue should appear. Type dxdiag in the available text field.
3. Click OK
4. Click Save All Information
5. Set the Save as type to Text File (*.txt)
6. Save the file DxDiag.txt to your Desktop so it is easy to find.
7. Attach the DxDiag.txt file in a reply to this e-mail.
Once we've received this information, we can take a closer look and hopefully help resolve the issue.
Regards,
Team17 Support
PS: I have both a .dmp and a .xml file in the "Crashes" folder, I can share those as well if needed.
SYMBOL_NAME: HLL_Win64_Shipping+10b9a49
MODULE_NAME: HLL_Win64_Shipping
IMAGE_NAME: HLL-Win64-Shipping.exe
STACK_COMMAND: ~148s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_HLL-Win64-Shipping.exe!Unknown
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 4.25.0.0
FAILURE_ID_HASH: {4c74b889-402a-886a-b0a3-4bd9f5d8c212}
Followup: MachineOwner
Thank you for the update.
To reveal any possible issues with your Windows system, we would like to recommend that you please attempt the following actions:
- Open the Windows Start Menu
- Type “cmd”
- Right-click on Command Prompt > Run as administrator
- Type “sfc /scannow” without the quotes
- Press Enter
If the process has revealed/resolved any issues, please attempt to run the game again.Please do respond with the results.
We look forward to hearing from you.
Regards,
Team17 Support
another reason for 'invalid_pointer' can be that the game is trying to access a file which is in location X on disk but when it goes to check X, it doesn't find what is being 'pointed to'. this can come from disk errors, corruption, fragmentation and a whole host of other sh*t, but basically, if you were to put HLL on an SDD, you would never get this.
if it's not a disk error, then it's an out of memory error.
bit of a sidenote: depending on how this game is fumbled together, that'll give you a similar error code, even though invalid_pointer would not be the right term. often programs are designed to throw that error by default when the program realises it is running into a problem but can't afford to figure out what the error is before it has to shut everything down to avoid damaging your components with whatever happens when it's doing something it's not designed for.
for example if it runs out of memory because 9 billion objects are being spawned and some script has no memory to run in, that might push a bunch of calls to your graphics card and fry it, so stuff like this is a failsafe. someone will go and correct me on the nitty gritty but eh, you get the Point(tm)
in other words, you could give sfc /scannow a try. image file corruption is annoying when it happens, but at least when it happens, you know what's up, and there are fixes for that.
i barely remember sh*t about how to fix this but there's a number of things that can cause out of memory error. i'm gonna be shooting in the dark, scrolling my memory for things i remember having to do to fix this kind of sh*t in a lot of games after googling my ass off, so i hope one of these helps.
some anti-viruses will dislike some operations done by programs that only run once in a long while, like garbage collection, and will then decide to make it go through some protective routine, which can interrupt some scripts that don't expect to be interrupted. that can lead to memory errors, but is unlikely the problem here.
permissions. yes, having your steam folder installed into a weird location (like desktop or my documents) can cause lots of random problems where something is trying to access a file but can't. usually most of the files will be accessed and the game does not detect a problem until it wants to run that one operation that is somehow not allowed from that location. welcome to windows. program files should be fine.
having your HDD partitioned, or using virtual drive programs like poweriso. this is another one that demands a long explanation for the full understanding but sometimes paths get mislabeled, or paths are referenced. if you disconnect a drive, or the drive refreshes its connection, sometimes that can relabel it from whatever it is (ex. D:\) to something else (ex. C:\) and then the program will call for something in D:\ but no such thing exists and the program throws an error.
paging file size. you have to google for this one, i hate this thing and for the life of me i can not remember, but it is problematic. paging file serves as a backup RAM, essentially. it's much slower, but can cause some problems when programs are wrestling with windows to use it, especially when the game is calling for any memory and does not care for whether something is RAM or paging file. it's either wrong to set it to automatic, or it's wrong to set it too small, i remember both being an issue for different games where out of memory 0x000005 is a thing.
XMP, memory overclock, or mismatched memory speeds. metaphor: drive a bus, turn a corner, try to throw a ball at your friend in the bus and watch him not catch it. XMP is not enabled by default in BIOS, and if your PC is prebuilt (bought as-is) then you won't have mismatched memory sticks. if you have XMP turned on in BIOS, disable this. if you have mismatched RAM stick speeds, get ones that match. if you have memory overclock, le don't. many games don't like that. alternatively, you could turn down your memory overclock a bit, some games like it worse.
UAC. if you install something and you get the "a thing is trying to do a thing on your computer", that is User Account Control. that stuff can get in the way. many people don't recommend disabling it, i have that disabled. That said, you want your HLL-Win64-Shipping.exe to have admin rights. right-click, properties, compatibility, change for all users, check run this program as admin, hit apply, done.
sidenote: full-screen optimizations, probably a good idea to keep that checked, too, but it should not be necessary anymore. HLL used to run in exclusive fullscreen mode and that has many drawbacks, so they changed it. running your game in borderless windowed could also help with performance, but it can also make performance worse. depends on a number of things.
steam overlay. don't ask me how. you can google this. steam overlay is capable of causing out of memory errors somehow.
those built-in bloatware power settings programs that some prebuilt computers come with, e.g. Lenovo Vantage and stuff like that. set that to balanced. sometimes those will try to overclock your VRAM (if you don't believe it, i didn't either, it sounds nuts.) if you don't have one of those programs, ignore this.
you can also check Event Viewer in windows and look around the time of the crash. that'll give you some more to stuff into google
can also try -dx11 in launch parameters. more stable than -dx12.
DISABLE WINDOWS GAME MODE.
settings -> gaming -> game mode -> no no the bye bye
you will not miss it. the reason i suggest it here is because game mode can mess with memory management.
disable discord overlay, xbox overlay and all that sh*t
also make sure your components are not overheating.
memory does not like being ultra hot. memory, that is, VRAM,RAM,HDD,SSD.
if you don't know, GPU has VRAM. in super basic english: hot pc bad
i use HWINFO64 for this.
a smaller program is HWMONITOR,
this'll just tell you the temperatures of your components.
if you want to prevent overheating:
-you can clean your PC with compressed air,
-undervolt your GPU through AMD Adrenaline.
pretty involved, but could have good results. worst case scenario, your PC crashes and you have to restart it and the voltage settings reset themselves automatically, and there are plenty of tutorials for this.
-create a custom fan curve (this one's easier and less easy to get wrong)
couple of obvious ones:
-check for RAM- or disk damage. handful of programs you can use, can also bring it to a shop, just make sure to delete blushing_midgets.jpeg
-legit running out of memory. unlikely with your fat 64gigs but possible. keep an eye on it while it runs and see the size of the process in task manager. might be worth closing the six million chrome tabs if you have them.
-memory leaks are a common thing in games.
the game might have an actual memoryleak that only triggers on some systems with some configurations, and could require very specific info to get to the bottom of. this is the reason why i laughed when they sent you "sfc /scannow" because that sometimes translates to a dev saying "i don't wanna assume that we have code that is prone to memoryleak, lets see if you have a faulty disk". don't google "is sfc /scannow useful". can totally understand holding off on the full inspection, crossing fingers that it's not that. if it is that, it could be as a simple fix, or it could be something they never fix.
AMD is known for having very fickle issues with lots of things. i'm unfamiliar with how AMD does their gfx stuff, all i know is that there is a crapton of forum threads about AMD-related game crashes from all kinds of games. the upside is that you won't be the only one with this problem, which means that you can probably google the details of your crash with the game name beside it.
i hope one of these helps
I did the sfc scan and found no errors whatsoever because I did a fresh Windows install a few days ago. As tmo97 mentioned, I have an EXPO OC profile enabled in my BIOS, which I suspect may be the problem. But then again, why doesn't this happen in other games? It cannot be the hard drive because it's an M.2, not and HDD and everything is installed in the default folder Steam sets.
I mentioned in the past that I reinstalled my GPU drivers just to make sure and I realised AMD wasn't installing the latest drivers in the first place. For some reason, if you install AMD Adrenalin with the automatic detection, they install an stable version that barely updates, even if you enable the optional ones in the menu as well. The interesting part is that optional updates happen to be the latest so I don't understand why they call them as such. Anyway, I erases all my GPU drivers again and directly installed the optional ones specific to my GPU. Hopefully that works because I don't want to disable my EXPO profile just for this game.
PS: thank you both for your help, especially @tmo97, which had such a detailed response. I appreciate your time and effort.
computer parts are tools
each piece of software use its toolset differently
it is not a perfect toolset
it is not a perfect game
every game has ways to hammer its thumb.
it is like how a fork is made for eating, but there is a way to misuse it
i remember not being able to use MSI Afterburner with some games.
it wouldn't like any clockspeed and voltage apart from factory standard,
not even undervolt and underclock
some games will fare better with OC than others
i can run some games at 843mV.
other games will crash my driver at that low voltage
same goes for overvolt and overclock
some just don't like the timing,
some just base their timing off of factory standard,
things go wrong when timing is off.
that's for gpu, it's even moreso for RAM.
many games don't like tweaked memory speeds,
some RAM sticks will handle it better than others.
the software utilising the memory is not made with every RAM stick in mind
think of a car with two drivers. :s
if you still want to use your OC,
check if it doesn't crash without the profile,
then tune it to be more gentle OC
if the game doesn't crash, your new OC works for HLL
you can then still use OC, just not as much
my computer can run on epic.
only reason there is still stutter and fps drop is because of stuff happening that requires CPU.
my CPU is ryzen 5 5600g, it is a bottleneck. RTX3060 can outpace it.
it is already long done by the time the CPU comes stumbling in with the data the software needs to make a frame.
if you are using VRAM OC,
it is not necessary for HLL at your resolution and with your powerful components.
if you are using RAM OC, your disk is still much slower than your RAM.
if HLL is loading and unloading textures from disk, RAM will have to wait for the disk.
it happens in steps, but RAM is generally much faster than disk.
it depends also on how the game uses the computer toolbox.
PS: I just disabled my EXPO profile, I'll report back if I have another fatal error. This might be the only time I want to have one.