BATTLETECH - Access Violation crash

[Nikos Steiner]

One line summary of your issue
Access Violation crash

Please explain your issue is in as much detail as possible.
I had been getting some heinous crashes with my game, all of them (now that I loaded the beta 1.0.1 update) have a name, now: Access violation. Any time I would hit a dialogue or other trigger in a mission especially or occasionally in transit/the Argo/etc I would risk having an access violation somehow and it would cause my GPU to totally shut down and fail, forcing me to do a hard reboot, upon doing the 1.0.1 beta update I didn't have the crash THAT BADLY but it did still crash, and it generated several reports.

Steps to reproduce the issue
often when moving a mech to a new area with undetected enemies, during or after in mission dialogue especially as the map is being populated is when I would receive the crash, though last night's crash I was on the Argo, had stowed my blackjack in Storage, then went to launch contract for Liberation: Panzyr and I got the detailed crash report, this is the first time it had ever crashed OUT of mission, but I also have an output_log of an IN Mission crash, too (from moving my Shadowhawk toward the turret control facility in that same mission)

Upload attachment

 

[Nikos Steiner]

Andrew, my main playthrough looks like the Savegame is somehow corrupted from THIS output_log. And I just noticed significant dust buildup in one of my PC's frontal fans right over the GPU.

 

[Nikos Steiner]

Here's an output_log from after deleting all saves and starting a clean playthrough. I also am trying the "optional" AMD 18.4.1 driver.

 

[Nikos Steiner]

just updated to 1.0.1 LIVE patch. started a fresh playthrough, was able to get up until almost defeating the first two mechs on Coronation Day before I crashed again. posting output log.

 

[AndrewT]

Still no crashes or significant errors in any of those logs.

What can you say about the behaviour of the GPU and fans etc now? Any better/worse? because it's quite clear the crashes are coming from outside the game somewhere!

 

[Nikos Steiner]

Well, Andrew, I can do some movement on the Coronation Day mission, then the GPU still 'cuts off' with a brief burst of 'fan activity' either just before or during the fight with the first two mechs. the only 'third party' programs I run, normally are CCleaner and Malwarebytes Anti-Malware. What I thought was 'weird' was using my NZXT Kraken's CAM app, after doing the thorough cleaning inside the case and all the fan ports my GPU is running 'hotter' when it's idling, is that supposed to happen? I can try the game without Malwarebytes and CCleaner running and see if that helps.

 

[AndrewT]

after doing the thorough cleaning inside the case and all the fan ports my GPU is running 'hotter' when it's idling, is that supposed to happen?

Absolutely not. There is a problem there!

I think you probably have a faulty fan or a heatsink/thermal paste problem. You may need professional help at this point.

 

[Nikos Steiner]

That's weird... now the temperature when idling is back in its normal range pre-cleaning and NOW it's hovering around 30-33 C, immediately after the clean it hovered between 34-36 C, is what I meant by running 'hotter'. When I checked the last temps in game it was about 50-55 C so it 'shouldn't' be overheating.

 

[Nikos Steiner]

So, update on my end, after 1.0.2 I was able to play up until the Weldry story mission without issue, then I started having the GPU issue again intermittently but was able to play the game until I got back to Panzyr, at which point, just like in my first playthrough the 'crash' became permanent. I'm at a loss, I know that the game is getting better with each patch, so I'm confident we'll get it working in time, but it's still a bit frustrating to not be able to progress! This is my most recent output_log. The past few output_logs hadn't shown anything that even looked like it said it had an error, it's just eating up so my GPU that it's crapping out with certain in-game triggers.

 

[Nikos Steiner]

Using a fresh save with Beta and then release 1.0.3 I had zero issues playing the campaign until I got to Panzyr before the trigger-spasms began again, and I am noticing that they occur most frequently when using the Valhalla or Umbra skins. Though I haven't been able to try Panzyr without the Valhalla or Umbra skins because as soon as I changed it back to 'standard' I my GPU spasmed on the mission loading screen. this is the current output_log

 

[Nikos Steiner]

Here's an output_log for the same save but just shortly after loading into the mission.

 

[Nikos Steiner]

this is the last output_log I'm going to post because at this stage the game is absolutely unplayable and I'm getting very near to asking for a full refund of my backer pledge since I am a Initiate of the Order level backer and paid way more than I'm getting out of this game. I really hope to the gods that you're (both PDX and HBS) seeing these posts from me and other AMD users (and even the handful of nVidia users with similar issues), because I've NEVER had a game just consistently crash for no explicable reason (I have even confirmed with another friend who runs a similar set up (same GPU and a few more things in common) and he's able to play the game without issue). So, if someone from HBS or PDX can tell me personally that this issue *IS* a high priority fix I might consider keeping the game, because it's been a month and I cannot play the game at all once Liberate: Panzyr becomes available, the mission just will not load right, it consistently crashes, no matter what settings I run, no matter if I do a clean reinstall or not, no matter what I do with my drivers or otherwise, no matter whether it is a fresh campaign or not the game just ceases to function once I get to Panzyr, and generally, I'll have an intermittent crash or two or more leading UP TO Panzyr.