Home Trending Latest threads New posts Developer diaries

BATTLETECH - Crash to desktop at least once a mission, every mission

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
BATTLETECH 5562 BATTLETECH Bug Reports 3823 BATTLETECH Suggestions 1569 BATTLETECH Mod-forum 700 BATTLETECH Universe 246 BATTLETECH Fan art, fiction & creations 164 News and Updates Archive 129 BATTLETECH Multi-player 106
P

pentriket

Private
Oct 12, 2020
13
0
One line summary of your issue
Crash to desktop at least once a mission, every mission

What platform are you running the game on?
Steam

What operating system do you use?
Windows 10 Pro

Which version of the game are you running?
1.9.1-686R

What DLC do you have installed?
Flashpoint, Urban Warfare, Heavy Metal

Please explain your issue is in as much detail as possible.
At least once a mission, but sometimes multiple times the game crashes to desktop. Nothing in particular will be happening, but it's always in a mission. Sometimes within seconds, sometimes 30 minutes into a battle. I've tried clean booting with everything not essential turned off, reset RAM, CPU, and GPU to stock settings, every combination of disabling Steam cloud-sync, clean uninstall/reinstall multiple times having followed the guides on how to completely remove all files.

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x000000000140a65c
Faulting process id: 0x2300
Faulting application start time: 0x01d6a09507ebf980
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: c7f4ee2c-9ad4-48c3-ab07-36627a9e6f4e
Faulting package full name:
Faulting package-relative application ID:

Have you tried verifying your files?
Yes

Steps to reproduce the issue
I just have to play the game and get into a mission and it'll happen.

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

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
File(s) attached

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
File(s) attached

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#/
File(s) attached

Attach screenshot / video
File(s) attached
 

Attachments

  • DxDiag.txt
    90,6 KB · Views: 0
  • output_log.txt
    458,1 KB · Views: 0
Upvote 0
There's no crash recorded in that output log. Can we get a new one from just after a crash please?

And, has this always happened ever since you've had the game?
 
No crashes recorded in those either I'm afraid. That tends to point to a cause outside the game.

The black screen you mention is a whole of Windows crash, is that right?

If you check the Windows Event Viewer around the time of a crash do you see any significant ERROR or WARNING entries?


What CPU and GPU temperatures are you seeing before running the game? In the main game menu? Then when in a misison?
 
AndrewT said:
No crashes recorded in those either I'm afraid. That tends to point to a cause outside the game.

The black screen you mention is a whole of Windows crash, is that right?

If you check the Windows Event Viewer around the time of a crash do you see any significant ERROR or WARNING entries?


What CPU and GPU temperatures are you seeing before running the game? In the main game menu? Then when in a misison?
Click to expand...
Yeah, the black screen crash is a whole PC reset. The Event Viewer looks like what I posted originally, they're always those. But here, the most recent:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x000000000140a65c
Faulting process id: 0x2978
Faulting application start time: 0x01d6a187dfc03625
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: 953c48b3-f751-4125-816c-9c41ac26723e
Faulting package full name:
Faulting package-relative application ID:

Menu temps: 29 C and 46 C CPU/GPU
In mission temps: 31 C and 72 C
 
The Event Viewer error looks slightly different if I force Windows Data Execution Prevention off for the whole system via cmd. (I've been trying everything I can think of.)

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8e0f7a67d
Faulting process id: 0xabc
Faulting application start time: 0x01d6a194fb9452ec
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: unknown
Report Id: 9fc488ee-b299-4f15-afb6-d3908bf13ba9
Faulting package full name:
Faulting package-relative application ID:
 
From that I'm fairly sure this is a hardware problem of some sort.

72c is getting up there but not quite to the level when I'd expect problems, 80c or so.

Can you up the cooling anyway, try to get down into the 60s?
 
I don't know but this is the only game that does this. I can play something like DOOM Eternal at 1440p High/Ultra for hours or like literally anything else.

I've also tested Battletech at Low through Ultra and it's the same frequency of crash to desktop.
 
Do those other games get to those sorts of temperatures?

Your original dxdiag recorded no crashes at all in anything. Since then you've had the black screen crash among oers, is there anything in there now?
 
AndrewT said:
Do those other games get to those sorts of temperatures?

Your original dxdiag recorded no crashes at all in anything. Since then you've had the black screen crash among oers, is there anything in there now?
Click to expand...
You made me paranoid about the temp so I dusted out my computer yesterday, then did a fresh repair of Windows. No crashes yet since so crossing my fingers.

So to answer you, Battletech has been the only thing to routinely crash and certainly black screen my system. The GPU temp is fairly normal for me across other games. I changed the power setting in NVidia's control panal to prefer maximum power for the game so it tends to get hot. Looks to be that way for every other program with any kind of GPU demand as well, and yet never a crash to desktop or complete PC freeze on anything else.

Oh, and what made me look at repairing Windows was when running the game through its launcher instead of Steam I of course crashed but the Event Viewer Exception code was different. Forgot what it was and its not in the log now after redoing Windows, but Googling it said it were a memory caching issue. Similary to the Exception code: 0xc0000005 which I was always seeing before when running it through Steam, the culprits according to Microsoft would be virus, driver, registry, faulty RAM. I'm very confident that its not hardware or virus related so only thing left to try was just repairing Windows.

I'll update if that ends up not solving it.
 
Last edited:
Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x0000000000c4a653
Faulting process id: 0x3750
Faulting application start time: 0x01d6aca3c09492ac
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: aa841fe2-aec8-493f-8852-b26d08ff90a2
Faulting package full name:
Faulting package-relative application ID:

Still crashes, maybe less frequency now but not that much less. Nothing like this on any other game.
 
It is of course possible this is a game bug, although if so it does not seem to affect all players as often as it does you. Unfortunately at this point I strongly doubt there will be any more patches for this game.

That said it is interesting that what you've done so far has reduced the frequency. Perhaps there were two issues and what you've done has fixed one.
 
Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x000000000140a65c
Faulting process id: 0x17b0
Faulting application start time: 0x01d6bc447e5f8059
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: df1c0bf2-b11a-4237-aa78-66800405f5d0
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x0000000000e4a65c
Faulting process id: 0x120c
Faulting application start time: 0x01d6bc1f772f4662
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: babb169d-94cf-4472-bb29-eb5c67502716
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: UnityPlayer.dll, version: 2018.4.2.64310, time stamp: 0x5cf7e9ab
Exception code: 0xc0000005
Fault offset: 0x0000000000645d8b
Faulting process id: 0x426c
Faulting application start time: 0x01d6bb48e9a9f7fa
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\UnityPlayer.dll
Report Id: a9d0416f-951b-449b-b4c2-07e4329c569a
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffcc4cfa653
Faulting process id: 0x1b8c
Faulting application start time: 0x01d6bac8d2d4c87c
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: unknown
Report Id: a14bc24c-4a28-4fda-85e2-a89f1a614ab5
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: ntdll.dll, version: 10.0.19041.610, time stamp: 0xe5d7ed5c
Exception code: 0xc0000005
Fault offset: 0x0000000000016d4f
Faulting process id: 0x233c
Faulting application start time: 0x01d6ba0ab42d173b
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: cf64d322-5d2d-439a-8c6c-ec4aa77afbde
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000022db684a22b
Faulting process id: 0x15a0
Faulting application start time: 0x01d6b9ffec954136
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: unknown
Report Id: 781d52bc-7b68-4528-ba62-62c8e79e2899
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTech.exe, version: 2018.4.2.64310, time stamp: 0x5cf7e95c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffab221a65c
Faulting process id: 0x104
Faulting application start time: 0x01d6b9f3ab170fc6
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTech.exe
Faulting module path: unknown
Report Id: fa45072e-9679-45aa-bcb1-95eebd3ee8c3
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: BattleTechLauncher.exe, version: 1.0.7103.23035, time stamp: 0x5d02a867
Faulting module name: KERNELBASE.dll, version: 10.0.19041.572, time stamp: 0x979ddb1d
Exception code: 0xe0434352
Fault offset: 0x00129ab2
Faulting process id: 0x2a54
Faulting application start time: 0x01d6b936c12c05d6
Faulting application path: C:\Program Files\SteamLibrary\steamapps\common\BATTLETECH\BattleTechLauncher.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: f8e50fa7-2c90-456b-a428-ff640d7e46b1
Faulting package full name:
Faulting package-relative application ID:
 
Those fault offsets are all over the place. A game bug would typically have the same offset in every crash.

Do you have any other hardware you can test this game on?
 
I see, then I cannot think of anything else to try or suggest. While this game is by no means perfect, it is not having the problem you are seeing elsewhere, with crashes in multiple different code offsets. If it isn't game bugs or hardware, that doesn't leave much ... !
 
Game bugs that crash the game without writing a crash to the log? And are in different memory offset locations each time? Not absolutely impossible I suppose, although you'd think every player would be seeing those then.
 
You must log in or register to reply here.
Top Bottom
Back