- Jan 28, 2005
- 6,893
- 14
- 81
Been a week or so since I last ran Origin and just picked up Crysis 3. I always run Afterburner for monitoring and overclocking. Upon launching the Crysis 3 exe. I get a AMD driver recovery. I assumed it was my overclock somehow went bad and was bummed about it so I tried a lower setting and it still crashed. Reverted to stock speed and still got a AMD driver recovery.
By now my feelings were getting hurt but I wasn't willing to accept that my card was borked so I tried a different game, Far Cry 3, and all was well. next, I went back to my 1200/1600 (7970) setting and game still played perfectly so I tried Crysis 3 again..... crash as soon as the intro screens start.
Now in investigation mode so I reboot and try again this time I didn't fire up Afterburner out of haste and was happy to see that the game played. I played for about 10 minutes before I alt/tabbed out to fire up Afterburner for monitoring purposes (I have overclocking enabled upon Windows boot) and the driver recovered upon alt/tab back in.
I fired up gpu-z (to make sure my overclock was sticking) without start afterburner and went into the game. Sure enough the Lightning was humming along at 1200/1600.
No matter what I do I can't have Afterburner "running" while I play Crysis 3. I tried BF3 and while it didn't crash immediately It only lasted about 25 seconds into gameplay before I got an AMD driver recovery with Afterburner running.
Seems as though the latest Origin patch just broke Afterburner compatibility, atleast on my rig.
I'm running 13.2 beta 6 and afterburner 2.3.0 - this is the first issue I have encountered in God knows how long
By now my feelings were getting hurt but I wasn't willing to accept that my card was borked so I tried a different game, Far Cry 3, and all was well. next, I went back to my 1200/1600 (7970) setting and game still played perfectly so I tried Crysis 3 again..... crash as soon as the intro screens start.
Now in investigation mode so I reboot and try again this time I didn't fire up Afterburner out of haste and was happy to see that the game played. I played for about 10 minutes before I alt/tabbed out to fire up Afterburner for monitoring purposes (I have overclocking enabled upon Windows boot) and the driver recovered upon alt/tab back in.
I fired up gpu-z (to make sure my overclock was sticking) without start afterburner and went into the game. Sure enough the Lightning was humming along at 1200/1600.
No matter what I do I can't have Afterburner "running" while I play Crysis 3. I tried BF3 and while it didn't crash immediately It only lasted about 25 seconds into gameplay before I got an AMD driver recovery with Afterburner running.
Seems as though the latest Origin patch just broke Afterburner compatibility, atleast on my rig.
I'm running 13.2 beta 6 and afterburner 2.3.0 - this is the first issue I have encountered in God knows how long