“I bought this and have issues with updating the graphics driver. AMD website says Crimson 16.7.3 but it caused blue screen crashes. Anyone else update or know the latest available AMD driver version for this?”
Answer This Question
1-2 of 2 Answers
System restore is not required. Downloading the OUTDATED driver from Lenovo from 7/22/2015 (AMD Catalyst) fixes the crashing but leaves me with an outdated driver and hindered performance. As you may be aware, AMD does not even use Catalyst anymore, they use a software called Crimson. This is purely a graphics driver issue. No other drivers are having problems. Problems only occur when downloading the latest driver for the A10-7800 APU from AMD, which is Crimson 16.7.3 according to auto-detect. The same result is displayed when entering the APU manually. If the graphics driver can not be updated from the 435 day old driver that came with the system, that would be considered defective and unacceptable to me and I will just return/refund. If Lenovo is using some kind of proprietary drivers that is even worse and Lenovo hasn't updated this particular driver since 7/22/2015... It should be able to accept regular drivers from AMD who manufactured the APU, like almost every other system can. Again, this is defective, by definition. So in conclusion, there's no way to update the AMD A10-7800 graphics driver past the Lenovo version from 7/22/2015 that came with the system?
Sorry, there was a problem. Please try again later.Try restoring the system back to the original driver. Then look for graphics driver updates for this system here: Follow the link below to look for new driver updates for your specific system. As always, be sure to create a restore point on your system before you make any changes. Here is the link: http://support.lenovo.com/us/en/products/Desktops-and-all-in-ones/Lenovo-H-Series-desktops/Lenovo-H50-55-Desktop/90BG/003JUS?query=&Shallow=1&Type=&OperatingSystems=&Component=&Symptom=&linkTrack=Caps%253ABody_SearchProduct&tabName=downloads&beta=false
Sorry, there was a problem. Please try again later.