We want to thank all of the players who've made these 8 years as exhilirating and as fun as possible. Hope this helps.Asphalt 8: Airborne is celebrating its 8th anniversary! To mark this momentous milestone, we've prepared an equally momentous update, with special time-limited events, fashionable new features, and a completely overhauled look for the game! It crashed roughly 45-60 seconds the first time (I started it up a second time to recreate the readings I got. These readings are from roughly 30 seconds in-game. Tried loading Asphalt again but windowed this time so I could keep an eye on the HWmonitor and I don't know if this is normal or not but in the following screenshot, the bottom two readings (Graphics and Memory) would stutter from the MAX to 500MHz (graphics) and 300MHz (memory). went ahead and did the RAM test for the sake of time and everything checked out. I'll test out the RAM after work tomorrow and will update you guys once again. I will be trying to unpark all CPU cores after this (adjusting the power settings) and I'll let you know in an hour how it went.ĪNOTHER UPDATE: The last hour didn't have much change, everything went smoothly. UPDATE: 1 hour in and it's evening out around 52C (125F) and between 48w-55w no effects on the screen as far as crashing. I updated my BIOS, my chipset drivers, checked msinfo32.exe (everything seemed to be in order) I reinstalled the AMD drivers, rebooted and crashing occurs once again. Although it was 7 fps, my computer didn't crash. I removed all of the AMD drivers for my GPU and ran a game that would usually crash my computer in under a minute. While I let this run, I should go ahead an give a little bit of what I've done to troubleshoot. Which option should I use? Small FFT's, Large FFT's, or Blended? These steps would apply to you as well Steve. Next step would be to test your RAM, unlikely but still lets not leave anything unchecked, for this use memtest86. Start by testing your CPU with Prime95, monitor it's temps and voltages with HWMonitor, give it at least a 2hour test. Jonas if it didn't crash while running Furmark then it's likely to be another component the issue (still there's a chance it is the GPU but lets discard the other components first).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |