BATTLETECH - Hard Crash and reboot

[KEVs77]

One line summary of your issue
Hard Crash and reboot

What platform are you running the game on?

Steam

What operating system do you use?
Windows 10 Home 64-bit(10.0, Build 18363)
Which version of the game are you running?
1.91-686R
What DLC do you have installed?
Flashpoint,
Urban Warfare,
Shadowhawk Pack,
Heavy Metal

Please explain your issue is in as much detail as possible.
After running the game for awhile, I notice my temps and on my GPU and motherboard get a little hot, nothing dangerous just puzzling as the game is not that graphic intense. Then, while either in a mission or clicking to confirm mission over my entire system reboots. No BSOD, no warning, nothing. I have tried doing a clean uninstall re-install with directions here, GPU drivers up to date, etc. This seems to be the only game that causes this issue. I was getting a Kernel power 41 warning in event viewer after I investigatef along with others. I attempted fixes recommended for those online to no avail. I honestly think it has something to do with the game as this only has happened after I've been playing the 1.9 update. Please help. the game is unplayable for me now. I know I can roll back the update but I want to play with all the newest fixes, etc. I have no mods installed.
Have you tried verifying your files?
Yes

Steps to reproduce the issue
Play the game for 30 minutes or more

Attach DxDiag (PC), System Info log (Mac), or run sudo lshw -html > specs.html and uploaded specs.html (Linux)

Attach Output Log
Windows: \Users\YourUserName\AppData\LocalLow\Harebrained Schemes\BATTLETECH\output_log.txt
Mac OS: Users >{name} > Library > Logs > Unity > Player.log
Linux: ~/.config/unity3d/Harebrained Schemes/BATTLETECH/Player.log

If the game crashed, please attach the crash file with the time stamp closest to the crash.
Windows: [Steam library folder]\steamapps\common\BATTLETECH\DumpBox
For v.17 and beyond try here: C:\Users\[YourUserName]\AppData\LocalLow\Harebrained Schemes\BATTLETECH
OSX: Macintosh HD > Users > [username] > Library > Application Support > Steam > steamapps > common > BattleTech > DumpBox
Linux: [Steam library folder]/steamapps/common/BATTLETECH/DumpBox

If a save game was loaded at the start of the game session, upload it. Please make sure to upload the save game with the timestamp closest to when you loaded it.
Windows:
Steam: [Steam installation folder]\userdata[SteamID]\637090\remote\C0\SGS1
GOG: 'C:\Users\USER_ID\AppData\Local\GOG.com\Galaxy\Applications\50593543263669699\Storage\Shared\Files\C#\SGS#'
Vanilla:'C:\Users\USER_ID\AppData\LocalLow\Harebrained Schemes\BattleTech\C#\SGS#'
OSX:
Steam: Macintosh HD > Users > [username] > Library > Application Support > Steam > userdata > [SteamID] > 637090 > remote > C#> SGS#
GOG: Macintosh HD > Users > [username] > Library > Application Support > GOG.com > Galaxy > Applications > 50593543263669699 > Storage > Shared > Files > C# > SGS#
Vanilla: Macintosh HD > Users > [username]> Library > Application Support > unity.Harebrained Schemes.BattleTech > C# > SGG#
Linux:
Steam: /home/.steam/steam/userdata/[steamID]/637090/remote/C#/SGS#
GOG: /home/[username]/.config/unity3d/Harebrained Schemes/BATTLETECH/remote/C#/SGS#/
Vanilla: /home/[username]/.config/unity3d/Harebrained Schemes/BATTLETECH/remote/C#/SGS#/

Attach screenshot / video

 

[Havamal]

While you wait for customer support;

It might not help you but I had a similar issue with another game recently and it turned out to be a recent graphics driver update install. Doing the full re-istall rather than express driver install was the solution.

 

[KEVs77]

While you wait for customer support;

It might not help you but I had a similar issue with another game recently and it turned out to be a recent graphics driver update install. Doing the full re-istall rather than express driver install was the solution.

Yeah I tried that as well. Clean install of drivers from 3/19. Issue happened with previous 2 drivers for my graphics card as well.

 

[KEVs77]

A little more added info, I just tried again and it happened, it seems to happen mostly if I leave to go do something and windows 10 goes to screenshot mode or sleep mode. Not sure if it is related but I'm done playing the game for the foreseeable future until I figure this out. I hope someone can help me out.

 

[AndrewT]

After running the game for awhile, I notice my temps and on my GPU and motherboard get a little hot, nothing dangerous just puzzling as the game is not that graphic intense.

What actual temps please? Anything over 80c?

 

[KEVs77]

No, highest temp I witnessed was 52 C. Sorry, had to edit there. Been a long week.

 

[KEVs77]

I don't have the actual temps, is there a way to view them at time of crash? I have a physical temp I can see on my motherboard through my case and another temp monitor for my GPU. Neither got into any dangerous temps that I witnessed.

 

[AndrewT]

72c is getting up there ... !

You'd need a utility that records temps real time into a file. I'm not aware that my two usual ones Speedfan and Speccy do that, but I'm sure there are some out there that can!

In the game's Video options- advanced, scroll down - if Vsync is not enabled try enabling that.

 

[KEVs77]

72c is getting up there ... !

You'd need a utility that records temps real time into a file. I'm not aware that my two usual ones Speedfan and Speccy do that, but I'm sure there are some out there that can!

In the game's Video options- advanced, scroll down - if Vsync is not enabled try enabling that.

Sorry, been a long week, 16 hour work days with everything going on. I meant 52C, regular idle is around 35C. I did not see the physical temp when rebooting because I am usually out of the room when it happens. I don't think it is a hardware problem as this is the only game that this occurs with and it didn't happen to any previous version pre 1.9.

 

[KEVs77]

I just took my rig apart made sure all connections were good, cleaned out dust. Ran a stress test, everything passed, highest temp was 54.5C. I'm going to try battletech one more time and see if the issue is still there. Nvidia just release a new driver today which I clean installed.