Maybe this?
"Display driver amdkmdap stopped responding and has successfully recovered." I found this in the administrative events you mentioned in your last response.
Forum Discussion
4 Replies
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?
Computer documentation, from when you bought it.
Box from where you bought the card and installed it.
You can also usually open the computer up and take numbers off the card itself(sometimes you have to run them through the manufacturer to see).
But honestly...I am betting you are on the low end of the scale...have you tried the link?? Did it make any difference?
I thought I had found a work around by lower my graphics settings to very low settings, which worked for a while, but now it's crashing again. I reviewed the entry in the log you showed me and this is the message displayed:
"The description for Event ID 1903 from source HHCTRL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
http://go.microsoft.com/fwlink?LinkID=45839"
