Community Manager@JorshRod Your DxDiag shows and error with CLR20r3 crsahsing, this can be a result of an issue with your .NET framework.
You can download the Microsoft .NET Framework Repair Tool here: https://www.microsoft.com/en-IE/download/details.aspx?id=30135
I've tried all the same things as the original poster plus dxdiag + .net framework repair (although I'm not seeing any errors in dxdiag.log or any windows logs) + reinstalled video drivers (GTX1070). I still have the exact same issues. The game exits to desktop as soon as I hit the field. I'm a long time PC gamer, and this is the first game I've had a game exit as soon as I start to play. Hours troubleshooting = 3. Hours played = 0. Is there a fix? If not, how do I get a refund?
Hi there,
I have exactly the same problem. Also with the GTX1080Ti.
My dxDiag looks like yours... but I don't know how old this error is:
Fehlerbucket 2280556580897081140, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Problemsignatur:
P1: Madden19.exe
P2: 1.0.0.0
P3: 10.0.17134.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
But there is no Report.wer with more informations.
@EA: Is there any possibility to start Madden with some more logging output, so I can provide you with more data?
I have already run progmon.exe during the crash.
The last action before the crash is always (see PNG):
QueryNameInformationFile - \Windows\System32\ntdll.dll
As far as I know, this is a part of the Windows NT kernel ... so there is a lot of Microsoft voodoo magic inside.
All other games runs normal. There are no network activities of Madden near the crash ... so we can rule out connection problems.
So it seems to be a problem between Madden and our HW... Surprise EA! Computer-Games means different HW configurations ;-)
I have to setup my hole machine due to hardware changes at the weekend. I can give you a feedback if the clean win10 installation will fix the problem.
If not, refund seems to be the last option. So maybe you can stay patient until Sunday. Or EA come across with a fix ... who knows? :-)
Regard.
Just finished the re-install of Win10.
It fixed the problem for me.
