Error 1603 is usually some sort of local system issue. Try the suggestions mentioned here if you have not already.
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
The AMD Driver Thread
- Thread starter LtMatt
- Start date
Hopefully that’s sorted it.
Most stability issues which are cited as driver issues are typically caused by unstable overclocks somewhere in the system, it's very common.
I can't remember the last time I had a driver timeout that wasn't either the result of an unstable overclock/undervolt (CPU/Memory/GPU) or a dirty OS.
It's been an issue reported by some users for a while now. I've been playing Warzone myself frequently (on a 6750 XT/6900 XT) and never really experienced the issue myself. That said, it's under investigation. I am currently using the preview driver and will be updating to this today 22.5.1 driver today.
@AMD_Vik should be able to answer that.
Think it adds support for a few recently released mobile SKUs, but not 100% sure.
I should add that these questions (and any other AMD related questions) should be directed to @AMD_Vik.
Don’t know if this might help you @Dicehunter as I recall you had that message.
What settings were used on each app? AVC or HEVC on ReLive? What about Mirillis? I know Mirillis can record AVI files which are huge and very high quality whereas ReLive would be lower quality and more compressed.Just noticed something, I was recording in Star Citizen with ReLive and it doesn't seem to handle dark scenes all that well in this particular game, I tried the same scene with Action by Mrillis, Paid recording tool on Steam, And there's no dark pixelated patches, Limit of ReLive maybe ?
Yup, big performance increases went into DX11 apps in 22.5.2, and OpenGL in a later driver (maybe 22.7.1?).
I'm using 22.8.2 but was using 22.8.1 for weeks prior to that with no issues but YMMV.
Using 22.8.2, HDR support in every game and MSI AB overlay reporting working fine here.
HDR support for 10-Bit pixel format found in the Global Graphics section of AMD Software (this is different from 10-Bit colour support (and HDR) which is still supported by using 10 Bpc in the display tab of AMD Software) was removed in 22.7.1. Key point here is that this will only affect 10-Bit OpenGL apps, like Photoshop. All games should work fine with HDR as before. There is a lot of confusion online about this for some reason.
Please submit a bug report.
Last edited:
I know, I helped a few folks that said exactly the same thing as you. Basically that HDR support had been removed and the toggle has vanished in Windows 10.
The steps below fixed the issue in each case and the HDR toggle was visible again in Windows 10.
Try this and see if it helps:
- Perform a Factory Reset, (don't tick keep user settings)
- Restart PC
- Reinstall 22.8.2
- Restart PC.
- Check Windows Display Properties
Last edited:
Yes, I tested this yesterday and reproduced it. Crashed on the menu screen after a few minutes sitting idle. Looks like a possible game issue atm.
Last edited:
Driver for Modern Warfare 2.
Default is king and is off unless app specified, but some folk think it needs to be set to always off. For gaming purproses it only applies to OpenGL anyway (in terms of actually enabling vsync) so it never needs to be adjusted beyond the stock setting.
Last edited:
Vsync can be enabled in game for apps. It can't be activated through AMD Software for DX/Vulkan.
Understood, but thats not possible as DX apps are not supported for Vsync enablement in AMD Software. It's unlikely to be added too as the interest in such old games is minimal.
Resolutions/refresh rates can be changed via Windows Display Properties, so no need for this duplicate option in AMD Software.
Last edited:
Last edited:
Vik is innocent in all this.
