BATTLETECH - Often Crashes Trying To Start

[Finarfin]

One line summary of your issue
Often Crashes Trying To Start

Please explain your issue is in as much detail as possible.
I typically get this problem many times before the game somehow tries to start. There was no crash; the game was exited cleanly almost 24 hours ago.

Steps to reproduce the issue
Usually just try to start the game.

Upload attachment

 

[Finarfin]

Why is this game so unpredictable and unstable? I thought that it was heavily tested. It shouldn't be a test of the RNG whether the game will launch or you will get the awesome box that says:

Oops!
The crash report folder named 'xxxxxxxxxx' next to game executable. (What is the English translation of that sentence?)
It would be great if you would sent it to the developer of the game!

What would actually be great would be if they allocated someone to spend their complete work day investigating these errors. Oh, and to get rid of the Unity crap. That would be great, too.

 

[Klingon007]

What I don't get is this: the beta worked *fine*, it's the production release that gives me fits...

 

[CoffeeCupr]

@Finarfin
What graphics card drivers are you using?
Try removing what you have and going back a few.
Your drivers hate Unity:

Initialize engine version: 5.6.5p1 (b5fcd78dd1ab)
GfxDevice: creating device client; threaded=1
d3d11: failed to create device and context (8007000e).
GfxDevice: creating device client; threaded=1
GLContext: failed to create context: The specified procedure could not be found.

 

[Rebeldad]

I got this today for some reason. Played a couple hours then came back after work and kept crashing had to restart pc.

 

[Finarfin]

@Finarfin
What graphics card drivers are you using?
Try removing what you have and going back a few.
Your drivers hate Unity:

What makes you say that my drivers hate Unity? I'm using an NVIDIA GeForce GTX 960. I actually stopped playing another Unity game because I had an issue where it would randomly lock up the graphics during tactical combat. Sound would still work and you could the mouse moving over interface objects but the video was dead. Same things happens randomly in Battletech. I'm not even sure what good NVIDIA driver would be that would play nice with both Unity and everything else that works properly with updated drivers. I'm actually running the latest NVIDIA driver that was supposedly tweaked for Battletech. You would think they would know that it would have issues with Unity, if that's the case.

 

[CoffeeCupr]

@Rebeldad
From your dxdiag:

Driver Version: 24.21.13.9731

Try running with older Nvidia drivers. You have the same version as Finarfin (397.31), which is problematic.

@Finarfin
I say it hates Unity, because Unity is unable to create a device client for the graphics card. I suppose you could say that Unity and that driver mutually hate each other.


@Rebeldad

PROBLEM_CLASSES:

    ID:     [0n301]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x2728]
    Frame:  [0] : proxydx11_x64_Release

    ID:     [0n273]
    Type:   [INVALID_POINTER_READ]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x2728]
    Frame:  [0] : proxydx11_x64_Release

    ID:     [0n288]
    Type:   [NULL_POINTER_READ]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x9ac]
    TID:    [0x2728]
    Frame:  [0] : proxydx11_x64_Release

BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

IP_ON_HEAP:  0000000029cca0e0
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 0000000029cca0e0 to 00007ffa31b728d5

STACK_TEXT: 
00000000`12c2efb0 00000000`29cca0e0 : 00007ffa`42133ec0 00007ffa`31b79578 00000000`00008000 00000000`00000000 : proxydx11_x64_Release+0x28d5
00000000`12c2efb8 00007ffa`42133ebf : 00007ffa`31b79578 00000000`00008000 00000000`00000000 00000000`00000000 : 0x29cca0e0
00000000`12c2efc0 00007ffa`31b79578 : 00000000`00008000 00000000`00000000 00000000`00000000 00000000`00000007 : d3d11!DebugPrintF::DebugPrintF+0x73
00000000`12c2efc8 00000000`00008000 : 00000000`00000000 00000000`00000000 00000000`00000007 00000000`12c2f030 : proxydx11_x64_Release+0x9578
00000000`12c2efd0 00000000`00000000 : 00000000`00000000 00000000`00000007 00000000`12c2f030 00000000`12c2f018 : 0x8000

 

[AndrewT]

One line summary of your issue
Often Crashes Trying To Start

Please explain your issue is in as much detail as possible.
I typically get this problem many times before the game somehow tries to start. There was no crash; the game was exited cleanly almost 24 hours ago.

Steps to reproduce the issue
Usually just try to start the game.

Upload attachment

This appears to be a problem in the new April nVidia driver released recently. We are also seeing this in other Unity games such as Cities:Skylines.

A reboot will fix it temporarily, as you may have found. You could try a clean reinstall of nVidia:

- uninstall the driver
- reboot
- install the latest by fresh download from here:
http://www.nvidia.com/Download/index.aspx?lang=en-us
- reboot again

If that does not help you might consider doing that clean driver reinstall again, except installing the previous driver version from March:
http://www.nvidia.com/download/driverResults.aspx/132845/en-us

 

[AndrewT]

I got this today for some reason. Played a couple hours then came back after work and kept crashing had to restart pc.

proxydx11_x64_Release.dll caused an Access Violation (0xc0000005)
in module proxydx11_x64_Release.dll at 0033:31b728d5.

This module appears to come from GoG, not with the game, so you might contact their support on it.

Does the GoG client have an overlay? If so try disabling it.

 

[Finarfin]

What's interesting is that when I opened NVIDIA GeForce experience last night it told me I had a driver update available. It was the April 25th driver which I thought I had installed. So I installed it again. Both times I attempted to install the eventual result was a system crash, with the message below displayed. I think there might be something bad with this driver.