So the usual then, Atiapfxx.exe called via CMD with the arguments being "Atiapfxx.exe -r -sys -s test.xml" to copy atiapfxx.blb into atiapfxx.xml in the SysWOW64 folder in Windows. And then comparing that to last month's driver, well last weeks more like ha ha anyways 17.11.1 against 17.10.3 shows the following changes. 🙂 17.10.3 driver string. 17.40.1021.1011_20171026_2201 17.11.1 driver string. 17.40.1031_20171102_1430 That's the top of the XML. Then comes a lot of different properties and eventually the Crossfire flags. In the 17.11.1 driver these two profiles were updated. CFX Star Wars Battlefront 2 Call of Duty WW2 And this profile was added. Destiny 2 Below these we have the DXX settings which I think have something to do with DX11 and possibly some flags for that API but I'm not 100% certain on well actually what most of the things in this file really do. Anyways the following shows updates for the 17.11.1 driver. DXX Ghost Recon Wildlands Destiny 2 Below that there's a lot of different settings such as OpenGL but there's no changes here for this driver, the Destiny 2 profile linking to a exe now has a Crossfire property to it though on account of the above CFX profile addition. HighPerfGPUAffinity Destiny 2Profile And the Mixed Reality UWP app got a additional exe so together with MixedRealityPortal.exe there's now a profile for HoloCameraApp.exe MixedRealityProfile Not really game related but there's a number of applications that have profiles too included UWP ones. 🙂

https://i.imgur.com/4cedaLi.jpg Windows 10 x64 (16299.19) feel smooth for some reason when opening apps & programs.

Thanks @JonasBeckman for the 'comparing' as always. 😀 @NvidiaFreak650 Did u had the taskbar problem before and unresponsive UWP programs? and its better with that driver?

JonasBeckman:

Download: http://www.guru3d.com/files-details/amd-radeon-software-crimson-relive-17-11-1-driver-download.html EDIT: Looks like it's a non-WHQL driver.

Hi well this night I open AMD Settings to see if have some update then appear "new optional driver" 17.11.1 for experience I already know that this driver is not WHQL but as I never had issues proceed express installation in sequence I stay seeing the process then sudenly my screen stay black and after return and so on for several times (in this moment I note that have some issue) then is show one infamous BSOD that I dont have NONE for several years lol; there appear stopcode: Video TDR Failure and reason: atikmpag.sys then I restart system to see what happen and concluding my actual O.S. 2016 LTSB x64 start fast as one ray and all works fine so I open device manager \Video adapters\AMD RX460 and NO issues in sequence I open DXDiag to see some issue but nothing!! now I have doubt maybe is better remove this new driver with DDU and install again AMD Chipset drivers and another time this new 17.11.1? what you think thanks in advance sorry for my bad English 😉:)

There's still several users recommending staying on the 17.7 drivers due to some changes introduced in the newer ones which seem to affect stability and Wattman in particular can still be a bit wonky. I have not encountered any issues myself but I am on a older Fiji series GPU (Fury) and not the more recent Polaris (400 and 500 series.) models or Vega so I don't think the drivers will be doing much for this particular card. (Wattman is a bit so-so though, I agree on that and AMD needs to start fixing that sooner rather than later.) My advice would be to do a clean install and see how that works, if you notice anything out of the ordinary such as crashes or as in this case a full blue-screen ("BSOD") error then remove the driver and install a older one, you don't always have to update to the latest available particularly if the highlighted fixes doesn't affect anything for you. 🙂 EDIT: Wonky - Meaning that AMD Wattman as a replacement for GPU Overdrive can report incorrect values and has other issues which can be a big problem with how voltage and GPU clocks in particular can be really unstable if things go badly. Seems to have been especially bad for GCN 1.0 and GCN 1.1 owners, your own GPU uses GCN Gen4 as it's called since AMD now uses Generations to define the version supported by the GPU. 🙂 7000 series - Gen1 or GCN 1.0 200 and 300 series - Gen2 or GCN 1.1 Fury / Nano (And the 285 I think it was?) - Gen3 or GCN 1.2 400 and 500 series - Gen4 Vega - Gen5 If I remember it right. (With the upcoming Navi being something like GCN Next or what AMD called it as a next-generation GCN GPU.) EDIT: But that's not that important, hopefully the 17.11.1 drivers will be stable and that first install was just a temporary one-time issue. Perhaps some program running in the background? (I try to shut down any active 3D programs in particular, monitoring software especially but also things like Steam and the web browser.) Essentially the GPU driver will reset the device during installation as to update any files currently used by Windows and to apply new settings and such, if a program doesn't respond well to this it will crash and if the driver doesn't respond to well to the crash you get a driver crash which could lead to a stability problem especially if it happens during a driver update. Which is why I try to take care and ensure all current active 3D software is closed down before updating the driver. (Since I use the installer from AMD's website this includes Catalyst itself and it's processes.)

Is Forza H3 OK? Do you have 16gpus in Catalyst tray?

There's a new Vulkan runtime from the latest SDK of 1.0.65.0 available on their website. 🙂 https://vulkan.lunarg.com/doc/sdk/1.0.65.0/windows/release_notes-1.0.html Runtime download only. VulkanRT.rar http://www79.zippyshare.com/v/vaB5TRHz/file.html And the changelog.

Vulkan SDK 1.0.65.0 Release Notes Version 1.0.65.0 for Windows November 2, 2017 Visual Studio Versions: Visual Studio 2013 is no longer supported by the Vulkan SDK. This means that Visual Studio 2013 may not be able to build the demos or samples in the SDK. Writing Vulkan programs with Visual Studio 2013 may still work but is not actively supported. In order to ensure that all functionality of the SDK works properly, it is necessary to use Visual Studio 2015 or 2017. This SDK supports Vulkan API revision 1.0.65. The prior SDK supported Vulkan API revision 1.0.61. Drivers: LunarG recommends that you update your Vulkan-capable hardware drivers to the latest recommended version from your hardware vendor. A list of Known Driver Issues appears at the end of this document with more information. CMake: CMake 3.2 or later is now required to build the source code contents of the SDK. Any user with an older version will need to upgrade. Overview of new features in SDK 1.0.65 Scores of bug fixes, validation coverage and accuracy improvements, and many feature additions Extensions introduced since the 1.0.61 SDK: VK_AMD_shader_image_load_store_lod VK_AMD_shader_info VK_EXT_global_priority SDK Components This version of the SDK components are based on the following specifications and source code repositories: Vulkan Specification including extensions Vulkan Loader and Validation SPIR-V Specification version 1.1 Glslang library and tools SPIR-V headers SPIR-V tools Vulkan Tools Vulkan Samples Last Commits are designated by the following Git Tags in the respective repositories: LoaderAndValidationLayers: sdk-1.0.65.0 VulkanTools: sdk-1.0.65.0 VulkanSamples: sdk-1.0.65.0 Fixed Issues Fixed Vulkan-LoaderAndValidationLayers Github Issues: #2152 VK_ERROR_INITIALIZATION_FAILED with 280x #2146 Validation layers have multiple bugs with destroyed render passes bug #2145 vkCmdCopyImage and compressed texture destination issue question #2144 Descriptor set layout shader stage binding validation #2143 Exposing extension entry points from loader? #2139 Link errors when trying to use functions from some extensions #2137 Add warning on mismatch between sharingMode and queueFamilyIndexCount #2134 Report names, associated with VK objects via EXT_debug_marker, if provided by app. enhancement #2128 VK_DEBUG_REPORT_INFORMATION_BIT_EXT: Message clarity on successful insertion of validation layer enhancement loader #2127 Resizing the window in vulkan-smokescreen led to crash #2124 Vsync in cube demo malfunctions in high-contrast mode help wanted #2123 Core validation layer: Invalid validation error reported for a specific RP configuration bug #2121 vulkan.pc contains extraneous Libs bug #2120 32-bit builds unknown_ext_chain_gas.asm:373: Error: operand type mismatch for `push' question #2112 Core validation: Report error when an app requests both VK_AMD_negative_viewport_height and VK_KHR_maintenance1 extensions at device creation time. incomplete #2111 text relocations in 32-bit loader build on Linux bug loader #2106 Crash in vkCreateComputePipelines when layout is VK_NULL_HANDLE bug #2104 Invalid buffer in bufferViewMap causes crash bug #2099 [Help] How to fix the descriptor not accessible from stage error ? #2098 Consistently prefix handle values with 0x enhancement #2096 Memory validation does not account for external memory bug incomplete #2090 Wrong ParameterValidation(ERROR) when using VK_KHR_get_physical_device_properties2 bug #2089 No error when recreating swapchain while rendering to an existing swapchain image incomplete #2086 VkDrawIndexed validation layer suggestion incomplete #2079 Layer tests terminate with RangeCheck exception in VS2017 enhancement #2074 Write test to verify no pipeline state / renderpass lifetime issues #2070 Core validation crashes accessing renderpass info after destruction #2051 Filtering extensions, NVidia 385.41 and VK_KH(R/X)_external_memory_capabilities help wanted loader #2037 Core / Parameter Validation: Identity swizzle requirement is not checked for framebuffer attachments incomplete #2035 VK_ERROR_OUT_OF_HOST_MEMORY when extent is not specified for vkCreateSwapchainKHR incomplete #2019 vkCreateDescriptorSetLayout Crash - Heap Corruption bug #1937 Implement VUID-VkImageViewCreateInfo-image-01014 validation check incomplete #1787 Memory leaks in vkCreateInstance with standard validation layer enabled bug #1771 Failing tests bug #1425 Error message: PSO with VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST when patchControlPoints = 0 enhancement #1146 READ_BIT in srcAccessMask bug #948 EnumeratePhysicalDevices resets surfaceFormatCount bug #802 Core validation mishandles invalidation of dynamic state when a new pipeline is bound bug #711 Validation suggestion: Need to validate clear regions passed to vkCmdClearAttachments() incomplete #699 Layer Validation: Add Valid Usage Cases and Tests for INVALID_MEM_OBJ and vkFreeMemory incomplete #640 Adjust Validation Layer Checking if vkCmdCopyImage Restrictions are Lifted incomplete #438 Add tests for threading validation layer tests #287 Validate Image and image view parameter compatibility requirements incomplete Fixed LunarXchange Issues: #719 - Layer VK_LAYER_LUNARG_api_dump print value of pointer different from value in GDB #718 - VkLayer_standard_validation.json missingt #716 - Error during build of SDK cube example #715 - SDK Setup Linux CLion #714 - Missing inline declarations for function template #713 - Can't run the Vulkan Sample for can't open"GLSLANG_DLIB_NOTFOUND.obj" #711 - Crash when enumerating hardware (nVidia+Intel) #707 - Vulkan incorrectly tries to invoke AMD/NVIDIA driver in virtual machine #706 - Incorrect minImageTransferGranularity depth check Fixed VulkanTools Github issues: #296 DevSim should emit warning when exceeding device limits #253 api_dump layer does not log vkGetDeviceProcAddr and vkGetInstanceProcAddr calls

wow a lot of fixes in the new vulkan.

on Windows 10 16299.19 this driver does not work Mail and Maps :-(

Tiko82:

on Windows 10 16299.19 this driver does not work Mail and Maps :-(

No issues here.

Haven't tested yet, but they seem to solve 2 issues I've reported previously: - amdmatt announced that the uninstalled printers (and other misc drivers) problem was fixed in this release - After applying memory clocks on a RX480, the vram slider shouldn't reset, so the reset feature should also undo previously applied memory clocks.

https://www.3dmark.com/compare/fs/14031252/fs/14028894/fs/13464627 17.11.1 vs 17.10.3 vs 17.7.1 Every on 1070/600 (3DMark shows bad core clock) Nice improve 😀 I tested on 17.11.1 three times, score always near 13 400pts.

Has someone checked it with older mobo(s) (X58 or Z68) and RX Vega on Win10? Previous drivers are notorious for causing RX Vegas to BSOD on older mobos. I'm waiting it to be resolved before buying one for my compute rig. So can anyone check? (RX Vega + older -2011 or before- mobo + Win10)

No, FH3 loading takes for-ever 😱 Reverted to 17.9.3 WHQL !!! AGAIN !!!

OnnA:

No, FH3 loading takes for-ever 😱 Reverted to 17.9.3 WHQL !!! AGAIN !!!

Matt‏ @TheMattB81 We are investigating Texture Corruption and Long Loading Times on Forza Horizon 3.

http://i64.tinypic.com/9blwlu.jpg I love this. Well done AMD, since 1709 versions, it keeps getting better for me. I am bored reporting this to RTG. Any solution to this questioning behavior?

warlord:

http://i64.tinypic.com/9blwlu.jpg I love this. Well done AMD, since 1709 versions, it keeps getting better for me. I am bored reporting this to RTG. Any solution to this questioning behavior?

Expecting bug-free service on Alpha software is the definition of insanity.

warlord:

http://i64.tinypic.com/9blwlu.jpg I love this. Well done AMD, since 1709 versions, it keeps getting better for me. I am bored reporting this to RTG. Any solution to this questioning behavior?

Hmm, so you are running BETA driver on an OS in Preview/Alpha version, you are complaining about bugs and on other hand you are telling us that you won't report a bug to MS neither AMD? Quite interesting o_O

warlord:

http://i64.tinypic.com/9blwlu.jpg I love this. Well done AMD, since 1709 versions, it keeps getting better for me. I am bored reporting this to RTG. Any solution to this questioning behavior?

Perhaps don't use Insider preview for "production" purposes. I, personally, don't have that issue on latest non-beta build (Win10 FCU). If you feel bored of reporting it to them, have you tried joining them on the beta tester program (https://gaming.radeon.com/en/radeonsoftware/crimson-relive/vanguard/)?

@LocoDiceGR Not sure, I don't pay attention what goes in the taskbar 😀 & UWP programs work fine on my end. Rise of the Tomb Raider UWP crash when I factory reset the setting, other then that stable on my end. AMD keep removing things from RX Vega, first was Mantle now FRC. I use DDU latest version in Safe Mode, ran amdcleanuputility in safe mode & normal mode. if I install the old drivers it show up both Mantle & FRTC. 😱 😱 😱 Update: it just show up now then it remove again. not sure if it's a bug. https://i.imgur.com/GqCMpch.png