Direct X crash
I see several threads but no solutions. My game like apparently everyone elses is constantly crashing due to a direct X issue and is utterly unplayable. I saw a dev ask for specs, but that thread w...
Forum Discussion
Search on you computer, for Event Viewer..
Once it opens choose Windows logs from left hand list, then applications from the drop down list of Windows logs. Search the events listed until you find the DAI crash and note what it says about it, also look around it to see if any other programs are having issues about the same time and list those as well.
Nothing there, and the message I received when it crashed is the same as everyone else. Not sure why I bothered with all the DX data in my post if this is the response..
It is incredibly unusual for a system to crash with a listed error on screen and to get nothing in event log either in the "Windows>Applications" or "Custom Views>Administrative Events" the last location is for Critical,Error and Warning events from all administrative logs....because logging and storing events is what is supposed to happen when you have a crash. If you are just having the program close then yeah, I could believe it didn't log anything but since you say it is a directx crash with error message it should be in the logs.
The DXdiag file is so I and others can make sure you don't have something wrong as related to drivers, cpu, op system and most hardware that would be causing the issue and thus making looking for software changes a waste of time.
If you would rather that I not try to help you, then just say so, and I will leave you alone and let some other person try to help you....
Maybe this?
"Display driver amdkmdap stopped responding and has successfully recovered." I found this in the administrative events you mentioned in your last response.
Interesting....it says stopped responding....
You DX file shows a 5700 card but it doesn't say which one, and therefore it MAY be close to min specs and if it hits a demanding area with the graphics a tad too high for it, the card may take a bit of time to work through everything. Now if this is happening and Windows7 thinks it is taking too long, it will issue a reset call to the driver and that will crash the game. The reason Win7 does this is it thinks the card is hung and will not respond again, which used to happen in older Windows and you had to restart the PC to fix it, now Windows just resets the individual component and you continue on your way with just having to restart the program.
The problem is, if you have a Vid card that is working hard in a demanding situation, it may actually NOT need to be reset just given a bit longer to work. So Microsoft has come up with a fix to delay the time in which the Op system will issue a reset. https://support.microsoft.com/kb/2665946?wa=wsignin1.0 That is a link to the fix, you may want to try it and see if it doesn't help you out.
Also were there any other programs that stopped responding around DAI??
And what exact Vid card do you have, if you know?? 5750? 5760? 5770? 5780? 5790?
