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]

Just gave this a second try on a fresh install, got the full graphics card having a fit crash where it just shuts down and my monitor loses all signal forcing a full hard shutdown and reboot. Here's the output log, it occurred while clicking through and reading the deployment dialogue shortly after getting dirtside on Panzyr.
Going to try to see if the issue replicates with a fresh campaign as well, I know on my initial playthrough (the one stuck on Panzyr with errors, I got the full GPU crash periodically throughout the campaign)

 

[Nikos Steiner]

This is my DxDiag for my system specs, "on paper" I should have zero issue playing the game according to Paradox support.

 

[Nikos Steiner]

This was one last try on Liberate: Panzyr on my main playthrough, about to start a second playthrough to see if I can replicate it at a different point of the game.

 

[Nikos Steiner]

This Output Log is from a fresh playthrough just about a few moments after checking out the guard post in Coronation Day

 

[Nikos Steiner]

to post in this thread, I attempted the codec/media fixes in this thread: https://forum.paradoxplaza.com/foru...etech-access-violation-in-ffmpeg-dll.1092512/
No avail, still get crash to blue screen forcing a hard shutdown and reboot, only third party apps running are Malwarebytes Anti Malware and CCleaner
posted most up to date output_log here

 

[AndrewT]

The error.log in your OP here shows a crash in the AMD Video driver. You should update that AMD driver at least:
http://support.amd.com/en-us/download


There's no crash in that last log at all, but plenty of DirectX errors. They will not lead to bluescreens though! next time you get one take a photo showing the text of the BSOD clearly and post it here, or at least write that text down for us.


Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php

 

[Nikos Steiner]

The error.log in your OP here shows a crash in the AMD Video driver. You should update that AMD driver at least:
http://support.amd.com/en-us/download


There's no crash in that last log at all, but plenty of DirectX errors. They will not lead to bluescreens though! next time you get one take a photo showing the text of the BSOD clearly and post it here, or at least write that text down for us.


Please report the temperatures of your CPU and video (GPU)
1/ before starting the game up and
2/ after say 10 minutes' play.
If your PC's vendor has given you no way of reading temperatures, install
SPEEDFAN http://www.almico.com/sfdownload.php

The blue screen is just my monitor flashing ‘NO SIGNAL!’ Over and over again after the GPU fan goes batty off the hook.
I’ve updated to the latest AMD stable drivers and tried the latest optional updates up until Saturday night when I went to AMD directly and it reverted to last stable. My only option is to do a full clean uninstall and reinstall which I am not confident in my own skill, knowledge, and ability to do confidently without issues.

 

[AndrewT]

The blue screen is just my monitor flashing ‘NO SIGNAL!’ Over and over again after the GPU fan goes batty off the hook.

Ah, so the GPU is probably overheating; can you get the temps I asked for?

If that's the problem (ie you see temps approaching or over 80c when the game is running) Clean out all air vents it has (compressed air cans are good for this). Make sure airflow to them is not blocked by anything like walls, books or whatever.
If that doesn't drop the temps enough, you probably have a faulty fan or a heatsink/thermal paste problem. You may need professional help at that point.

 

[Nikos Steiner]

Ah, so the GPU is probably overheating; can you get the temps I asked for?

If that's the problem (ie you see temps approaching or over 80c when the game is running) Clean out all air vents it has (compressed air cans are good for this). Make sure airflow to them is not blocked by anything like walls, books or whatever.
If that doesn't drop the temps enough, you probably have a faulty fan or a heatsink/thermal paste problem. You may need professional help at that point.

Already a step ahead, I have an NZXT Kraken and they’ve got a handy app, it runs between 40-60 C, in game and 25-30 at rest, I just cleaned all the vents and fan ports EXTENSIVELY this weekend, trying to line up some ‘phone a friend’s’ to be ‘on call’ while I try a clean uninstall and reinstall of the drive

 

[Nikos Steiner]

Already a step ahead, I have an NZXT Kraken and they’ve got a handy app, it runs between 40-60 C, in game and 25-30 at rest, I just cleaned all the vents and fan ports EXTENSIVELY this weekend, trying to line up some ‘phone a friend’s’ to be ‘on call’ while I try a clean uninstall and reinstall of the drive

It only spikes above 60 if I leave a game running for HOURS on end just unattended (such as in a spot where I had to go AFK and saving isn’t an option short of losing significant progress)

 

[AndrewT]

If it never gets over 60c that really shouldn't cause any problem. But then the fan should not go crazy either ...

 

[Nikos Steiner]

Yeah, so, my current step is to try and do the driver uninstall and reinstall. That's the last step before I seek a professional (and three of the friends I'm lining up as "phone a friend's" are professionals). So I just need a GOOD walkthrough that I can follow and such.

 

[Nikos Steiner]

clean driver uninstall/reinstall complete, let's see how this fares on the battlefield!

 

[Nikos Steiner]

and I still crash, posting the output log, probably full of more DirectX debauchery.
I'm not sure what to do about DirectX... that's handled by Microsoft and they don't have a 'standalone' install for Win10... I looked, when I saw the DirectX errors in my first Output Log

 

[AndrewT]

I don't see any DirectX errors in that log file, indeed no real errors at all. That log was taken immediately after the crash?

 

[Nikos Steiner]

I don't see any DirectX errors in that log file, indeed no real errors at all. That log was taken immediately after the crash?

That log is immediately after the crash after reinstalling the driver. Like the fan didn’t even go batshit this time, the game or GPU just said ‘nope, gotcha!’ I’m starting to refer to my GPU as Schrödinger from here on out for what, by now, should be obvious reasons.

 

[AndrewT]

Did it make an error.log then? Does the crash show at the end of a dxdiag.txt ?

 

[Nikos Steiner]

I’ve only received the one error log this whole time. I’ll have to run a new DXDIAG in the morning

 

[Nikos Steiner]

This is the DxDiag I just ran this morning, it shows everything "firing on all cylinders" without issue.