Hell Let Loose - UE4 Crashes- Execution Access Violation

I need some help. I can no longer Play HLL for more than 20 minutes, at any time of day in any server. I keep getting UE4-crashes. Execution Access Violation 0x00000638. I've tried everything. Updated bios, drivers and Windows. Verified files, checked for malware, reinstalled steam and Uninstalled / reinstalled HLL twice. Even went to the point of completely restoring windows with a fresh reset. Nothing has worked. I'm at a loss as to what to do now, short of just deleting the game.

Found this forum post on the Steam Community page posted by one of the Devs.

https://steamcommunity.com/app/686810/discussions/1/4349865446115708307/

There are some suggested fixes.

Outside of that reddit was suggesting making sure there are no pending windows updates.

Hopefully that helps!

Thank you for the link, unfortunately still a no go.

Sounds to me like it could be unstable hardware, like possibly a memory error.

Really need the full call-stack to solve this one. If you can download the full error report that would be helpful.

Thanks for posting. When you say "memory" would that be Ram? 

Yeah, I was thinking RAM. It could be something else though, such as the drive. It might be time to start troubleshooting hardware.

Are you overclocking your CPU, GPU, or RAM?

If you need some help with what to do to troubleshoot your hardware, this is what I would check if I were in your situation.

• Check Event Viewer Logs (This is usually easiest right after a crash, the logs get cluttered during boot events and stuff.)
  1.  
     1. Open the Windows Start Menu, then type "Event Viewer". Open the Event Viewer App.
     2. Expand the 'Windows Logs' folder in the menu on the left, then click 'Application'.
     3. This is where you would see issues involving installed applications on your computer, including the game itself or stuff like GeForce Experience or the AMD equivalent.
     4. Look for anything with a level of Warning, Error, or Critical. Click the line to view details in the bottom half of the window. You might only see some Warning level entries that say something like "Application 'C:\.......\HLL\bin\HLL*.exe' cannot be restarted...", which just means that Windows couldn't reopen the game after the crash happened.
  1.  
     1. Click the System tab under the same Windows Logs folder in the left menu. This is where you would find issues with the Windows Kernel or System Services.
     2. Look for anything listed as Warning, Error, or Critical. Here, you'd be looking for something like your GPU drivers failing or not being loaded. Drivers are usually listed with a source of 'Service Control Manager', but I would check everything just to be sure, which is why I recommend looking immediately after a crash so you only need to look at a 5-10 minute time range.
  • Check the Application Event Logs
  • Check the System Event Logs
• Test your RAM for faults
  • You can use HCI Design's MemTest application while logged in to Windows. Download: https://hcidesign.com/memtest/download.html
  • PassMark's MemTest86 is more accurate, but you have to install it to a USB drive, then boot into the USB to run the tests. If you're comfortable with that process, I would recommend this method. Download: https://www.memtest86.com

If you find anything that points toward the problem in the above steps, then you would need to continue troubleshooting the related component.

For example, if your GPU drivers are crashing, that will be in the Event Log. In that case, I would then download 3DMark to run the GPU stress test in order to see if you are getting crashes there as well. If you don't crash, the issue would probably lie with HLL itself. If you do crash, your GPU might be failing, or your PSU.

If your Event Log is clear but your RAM throws errors, you would want to check your RAM BIOS settings to make sure the RAM is using the more conservative XMP settings. If you already are, you might have some failing sticks of RAM, or once again you might have a failing PSU. It's also worth making sure you have your RAM in the right slots for dual-channel if you don't have all your slots full. Check your Motherboard's user manual for the order you should populate slots in.

Like others here, my initial assumption would be the issue is with your RAM, or potentially your PSU. The fact that computers work at all is borderline magic considering they're just electricity being pumped into silicone chips. When a PSU starts to go bad, wonky stuff like this happens since the voltage tolerances on the motherboard can be pretty tight, or at least do not like dirty power with voltage spikes/dips.

Edit - If you find events in the Event Viewer directly related to an HLL executable or process, or if you just want to submit a ticket to the devs for support directly, you can do so here: https://support.team17.com/hc/en-gb/requests/new

Thanks for the reply borari. I've checked and rechecked all of your suggestions and everything has tested good. No bad events, just normal ones. Ram is brand new, installed yesterday. DOCP is set at 3600, FCLK is set at 1800 and voltage is 1.350. New ram is 3600mhz CL16, 4 sticks of 8gb. NOW here's where I found a strange thing- my monitoring software is showing only 0.85v to memory....strange!! New PSU arrives any minute. LOL! Would have never thought of psu but makes perfect sense. Will keep you posted. Thank you for expert advice and information. Much appreciated and Happy New year to you and yours.

UPDATE! Fixed, Fixed and Fixed!! Made possible by all of your suggestions. Many, many thanks to everyone!! Had a couple of corrupt files and a C: drive issue. I discovered a YouTube channel named Britec09 and followed one of his videos (go check him out) .I checked and repaired everything through Command Prompt. Lots of fixes to Drive C: . Who would've thought (not me).

Awesome good news! So it sounds like you did a chkdsk /f on C: to repair filesystem issues? You might also want to do sfc /scannow as well if you have not already.

Also, what drive is this? SSD/HDD, make, model? I ask because it is possible that the issue was not just software, but signs that the drive could physically could be slowly failing. You should check the SMART data for the drive, to determine its health. If it has issues such as bad sectors, you should probably backup any important data on it, and RMA/replace the drive.

Update of the Update. Still a no go!! SSD is good. Team17 gave me a few suggestions and nothing worked. Been avoiding the game for days now. Seems like the only solution. Really can't do any more. Hardware and software checks out fine but something is up since update 11.

Hello everybody. Final UPDATE! Exception Access Violation 0x00000638 is caused by (according toTeam17) a controller being plugged in to PC or connected via Bluetooth. Team17 is absolutely correct!!   You can use a controller or keyboard/mouse but not both at the same time. Go figure! I've tested the theory many times and I'm back to playing full games without a single crash. You must turn on controller before launching game and do not touch keyboard/mouse at all! If you do, UE4-crash immediately. Now, about that discharge request and reinstalling teamspeak!!