Forum Discussion
Ok so for the first few weeks of playing I never had any crashes then all of a sudden this past week I've gotten the infamous material dx11 crash. I've played with numerous settings and configurations to no avail. I downloaded jetbrains dotpeek program to see if I can read more into the dll file.
I found that it's based on the .Net Framework platform. I was running the current 4.5.1 version so I downgraded that to v4.0 and restarted the computer. As of right now I have been able to play through a few complete matches without a crash whereas before I couldnt play more than a couple mins. Could someone else try this and confirm whether or not this works for them?
Win 7 64
Msi GTX660
As I have said many times before in this thread.
Just because you've played for a couple of matches/hours without crashing doesn't mean you've fixed it. Two days ago I actually went a full day and a half, about seven hours of play time, without crashing. Without changing a thing. Without doing any of these "fixes". It's random. Sometimes you will get lucky.
This is not likely something that WE can fix with silly tinkering or messing with our configs. This is something Respawn/EA has to fix, or Nvidia. Or Radeon in the few cases where someone has one of those cards. And as said, a new Nvidia driver came out today that has the name of "DX11 performance". So who knows.
- Anonymous12 years ago
I tried the new driver before I downgraded the .Net to 4.0
- 12 years ago
Put the new GeForce beta drivers to the test (released today). Removed all the special borderless windowed settings etc. and let GeForce Experience optimize the game for performance instead of having several settings to medium.
Actually managed to play through a Boneyard surprisingly but after trying out a game of Demeter (these two maps crash hardest for me) it crashed.
New drivers, same **bleep** **bleep** ass error.
- 12 years ago
@Kirkerinoh wrote:Put the new GeForce beta drivers to the test (released today). Removed all the special borderless windowed settings etc. and let GeForce Experience optimize the game for performance instead of having several settings to medium.
Actually managed to play through a Boneyard surprisingly but after trying out a game of Demeter (these two maps crash hardest for me) it crashed.
New drivers, same **bleep** **bleep** ass error.
Then that means it's up to Respawn/EA.
Look. We've gone a month without any real answers and I feel like I'm the only one really trying. I've sent messages to news sites, contacted them on Twitter. Spammed Respawn/Titanfalls/the community managers twitter, gotten at least a tiny bit of an answer from the community manager before being brushed off.
If you guys would help me out a bit we might be able to get some answers.
- Anonymous12 years ago
I was sending them a few messages a day early on. Now I'm sick of wasting my time.
- 12 years ago
I run SLI GTX 660 Ti's and have tried this game with each card solus in different PCI express slots and with different power cables. This error seemed to only occur with one of the cards so I RMA'd it. Turns out the new card I received also has this issue. I cannot, for the life of me, understand why one card is exempt from this problem.
I also consistently get driver crashes (nvlddmkm) along with the materialsystem_dx11.dll crash. Tried all available solutions and still have this issue. Can you guys confirm you get this warning in the event viewer too?
Hoping a fix comes with the legit SLI/4k patch, but I doubt it will ☹️.
About Titanfall Franchise Discussion
Recent Discussions
- 4 days ago
- 8 days ago
- 10 days ago