AMD R9 380 (as supplied by HP) - latest driver availability

krzemien · 06 Oct 2018

Hello,

I have been experiencing TDRs (116 bugchecks) and 141 LiveKernelEvents whilst using this card on my 1.5 year old HP OMEN 870-095na Windows 10 x64 PC and latest available driver (17.7) as supplied by HP for this card - R9 380.

Driver - OMEN by HP 870-000 Desktop PC series | HP® Customer Support

Both were happening only when PC was left unattended in logged-off state for some time. They do not happen when using PC normally - or perhaps playing some rather dated games / doing benchmarks / GPU tests. So although annoying, kind-of manageable.

With recent 1809 update deployed earlier this week however I also started seeing these upon restart (fast boot is enabled) - or started experiencing black screens and frozen PC, which requires hard-restart. Which is not great.

I am entirely aware that it's not the latest AMD driver that is available for this card, however any attempt to get it updated via AMD installers to either of these two (18.5.1 or 18.9.3):

AMD Radeon™ R9 380 Drivers & Support | AMD

is initially successful - drivers & software gets installed and does seem to work correctly - however not for long, as Windows thinks that installed driver is not a correct match (GPU is recognised as R9 200 series rather than proprietary R9 380 series card) and installs its own rather old driver (despite me explicitly having it blocked in Device Manager).

http://www.catalog.update.microsoft.com/Search.aspx?q=R9

Which does not leave me with any other option but to get the latest as-supplied-by-HP-driver installed.

So, my question is: where do I go from there?

Any thoughts / responses will be most appreciated.

krzemien · 14 Aug 2019

So to provide an update nearly one year later to this thread:

I've not changed a thing my end - with the exception of the regular drivers that got updated in the meantime - my 'AMD by HP' R380 graphics driver remains dated (Aug '18).

And yet BSODs / LIveKernelEvents etc. stopped completely on their own since late Oct '18 (so from 1809 release onwards). I'm on 1903 for some time now and things remain equally stable.

Genuinely puzzled what was the exact problem - my current guess is something within the OS itself that got patched by Microsoft silently in the background.