GeForce 451.85 hotfix driver download

Posted by: Hilbert Hagedoorn on: 07/25/2020 08:39 AM [ 16 comment(s) ]

Advertisement

Download the Nvidia GeForce 451.85 hotfix driver, as released by NVIDIA. This release fixes issues with Shadow of the Tomb Raider, Death Stranding as well as other issues at hand.

Game Ready Drivers provide the best possible gaming experience for all major new releases, including Virtual Reality games. Prior to a new title launching, our driver team is working up until the last minute to ensure every performance tweak and bug fix is optimized for the best gameplay on day-1. We have a discussion thread open on this driver here in our Nvidia driver discussion forums. For those that wonder, the DCH driver is a Microsoft DCH (Declarative Componentized Hardware supported apps) driver, and refers to a new Windows 10 driver package preinstalled by OEMS implementing the Microsoft Universal Driver paradigm. While the base core component files remain the same, the way DCH drivers are packaged differs from previous Legacy (Standard) drivers.

GeForce Hotfix display driver version 451.85 is based on our latest Game Ready Driver 451.67.

This Hotfix driver resolves the following issues:

[Shadow of the Tomb Raider][DirectX 12]: The game may crash when launched with Hardware-accelerated GPU scheduling enabled.
[Death Stranding]: Texture corruption may be observed during gameplay on GeForce GTX 16/RTX 20 series GPUs
NVIDIA Control Panel does not display the native resolution of some HDTVs with invalid timings
Some games may exhibit random freezes that lasts for a few seconds during gameplay.
Some displays may show a green tint when Windows Night Light is enabled
[Forza Motorsport 7]: Game starts to stutter after racing a few laps
[G-Sync Compatible] Adds support for the Samsung 27" Odyssey G7 gaming monitor

GeForce RTX 20 Series:

GeForce RTX 2080 Ti, GeForce RTX 2080 (Super), GeForce RTX 2070 (Super), GeForce 2060 (Super), Titan RTX

GeForce 16 Series:

GeForce GTX 1660 SUPER/Ti, GeForce GTX 1660, GeForce GTX 1650, GeForce GTX 1650 Super

NVIDIA TITAN Series
NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN, GeForce GTX TITAN X, GeForce GTX TITAN Black, GeForce GTX TITAN Z

GeForce 10 Series
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1660 Ti, GeForce GTX 1060, GeForce GTX 1650, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030

GeForce 900 Series
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950

GeForce 700 Series
GeForce GTX 780 Ti, GeForce GTX 780, GeForce GTX 770, GeForce GTX 760, GeForce GTX 760 Ti (OEM), GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745, GeForce GT 740, GeForce GT 730, GeForce GT 720, GeForce GT 710, GeForce GT 705

GeForce 600 Series
GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 645, GeForce GT 645, GeForce GT 640, GeForce GT 635, GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce 605

Have you read our MSI GeForce GTX 1650 SUPER GAMING X review already?

Download Locations

Download Windows 10 64-bit [ 15876 downloads ]

Download Windows 10 64-bit DCH [ 4167 downloads ]

4 pages 1 2 3 4

Neo Cyrus
Senior Member
Posts: 9554
Joined: 2006-02-14

#5812531 Posted on: 07/27/2020 01:24 AM

no it wasn't.

CEMU's async caching works fine with that driver and doesn't spit back an error saying that specific extension is missing. The whole "it's required and it's working" thing makes me think it's in there.

Astyanax
Senior Member
Posts: 8332
Joined: 2018-03-21

#5812537 Posted on: 07/27/2020 02:46 AM

CEMU's async caching works fine with that driver

No, it doesn't.

and doesn't spit back an error saying that specific extension is missing. The whole "it's required and it's working" thing makes me think it's in there.

You should do that thing everyone is able to and verify your claims.

- extensions: 103
  1/ VK_KHR_16bit_storage (ver:1)
  2/ VK_KHR_8bit_storage (ver:1)
  3/ VK_KHR_bind_memory2 (ver:1)
  4/ VK_KHR_buffer_device_address (ver:1)
  5/ VK_KHR_create_renderpass2 (ver:1)
  6/ VK_KHR_dedicated_allocation (ver:3)
  7/ VK_KHR_depth_stencil_resolve (ver:1)
  8/ VK_KHR_descriptor_update_template (ver:1)
  9/ VK_KHR_device_group (ver:4)
  10/ VK_KHR_draw_indirect_count (ver:1)
  11/ VK_KHR_driver_properties (ver:1)
  12/ VK_KHR_external_fence (ver:1)
  13/ VK_KHR_external_fence_win32 (ver:1)
  14/ VK_KHR_external_memory (ver:1)
  15/ VK_KHR_external_memory_win32 (ver:1)
  16/ VK_KHR_external_semaphore (ver:1)
  17/ VK_KHR_external_semaphore_win32 (ver:1)
  18/ VK_KHR_get_memory_requirements2 (ver:1)
  19/ VK_KHR_image_format_list (ver:1)
  20/ VK_KHR_imageless_framebuffer (ver:1)
  21/ VK_KHR_maintenance1 (ver:2)
  22/ VK_KHR_maintenance2 (ver:1)
  23/ VK_KHR_maintenance3 (ver:1)
  24/ VK_KHR_multiview (ver:1)
  25/ VK_KHR_pipeline_executable_properties (ver:1)
  26/ VK_KHR_push_descriptor (ver:2)
  27/ VK_KHR_relaxed_block_layout (ver:1)
  28/ VK_KHR_sampler_mirror_clamp_to_edge (ver:3)
  29/ VK_KHR_sampler_ycbcr_conversion (ver:14)
  30/ VK_KHR_separate_depth_stencil_layouts (ver:1)
  31/ VK_KHR_shader_atomic_int64 (ver:1)
  32/ VK_KHR_shader_clock (ver:1)
  33/ VK_KHR_shader_draw_parameters (ver:1)
  34/ VK_KHR_shader_float16_int8 (ver:1)
  35/ VK_KHR_shader_float_controls (ver:4)
  36/ VK_KHR_shader_non_semantic_info (ver:1)
  37/ VK_KHR_shader_subgroup_extended_types (ver:1)
  38/ VK_KHR_spirv_1_4 (ver:1)
  39/ VK_KHR_storage_buffer_storage_class (ver:1)
  40/ VK_KHR_swapchain (ver:70)
  41/ VK_KHR_swapchain_mutable_format (ver:1)
  42/ VK_KHR_timeline_semaphore (ver:2)
  43/ VK_KHR_uniform_buffer_standard_layout (ver:1)
  44/ VK_KHR_variable_pointers (ver:1)
  45/ VK_KHR_vulkan_memory_model (ver:3)
  46/ VK_KHR_win32_keyed_mutex (ver:1)
  47/ VK_EXT_blend_operation_advanced (ver:2)
  48/ VK_EXT_buffer_device_address (ver:2)
  49/ VK_EXT_calibrated_timestamps (ver:1)
  50/ VK_EXT_conditional_rendering (ver:2)
  51/ VK_EXT_conservative_rasterization (ver:1)
  52/ VK_EXT_custom_border_color (ver:11)
  53/ VK_EXT_depth_clip_enable (ver:1)
  54/ VK_EXT_depth_range_unrestricted (ver:1)
  55/ VK_EXT_descriptor_indexing (ver:2)
  56/ VK_EXT_discard_rectangles (ver:1)
  57/ VK_EXT_external_memory_host (ver:1)
  58/ VK_EXT_fragment_shader_interlock (ver:1)
  59/ VK_EXT_full_screen_exclusive (ver:4)
  60/ VK_EXT_hdr_metadata (ver:2)
  61/ VK_EXT_host_query_reset (ver:1)
  62/ VK_EXT_index_type_uint8 (ver:1)
  63/ VK_EXT_inline_uniform_block (ver:1)
  64/ VK_EXT_line_rasterization (ver:1)
  65/ VK_EXT_memory_budget (ver:1)
  66/ VK_EXT_memory_priority (ver:1)
  67/ VK_EXT_pci_bus_info (ver:2)
  68/ VK_EXT_pipeline_creation_feedback (ver:1)
  69/ VK_EXT_post_depth_coverage (ver:1)
  70/ VK_EXT_sample_locations (ver:1)
  71/ VK_EXT_sampler_filter_minmax (ver:2)
  72/ VK_EXT_scalar_block_layout (ver:1)
  73/ VK_EXT_separate_stencil_usage (ver:1)
  74/ VK_EXT_shader_demote_to_helper_invocation (ver:1)
  75/ VK_EXT_shader_subgroup_ballot (ver:1)
  76/ VK_EXT_shader_subgroup_vote (ver:1)
  77/ VK_EXT_shader_viewport_index_layer (ver:1)
  78/ VK_EXT_subgroup_size_control (ver:2)
  79/ VK_EXT_texel_buffer_alignment (ver:1)
  80/ VK_EXT_tooling_info (ver:1)
  81/ VK_EXT_transform_feedback (ver:1)
  82/ VK_EXT_vertex_attribute_divisor (ver:3)
  83/ VK_EXT_ycbcr_image_arrays (ver:1)
  84/ VK_NV_clip_space_w_scaling (ver:1)
  85/ VK_NV_coverage_reduction_mode (ver:1)
  86/ VK_NV_dedicated_allocation (ver:1)
  87/ VK_NV_dedicated_allocation_image_aliasing (ver:1)
  88/ VK_NV_device_diagnostic_checkpoints (ver:2)
  89/ VK_NV_device_diagnostics_config (ver:1)
  90/ VK_NV_external_memory (ver:1)
  91/ VK_NV_external_memory_win32 (ver:1)
  92/ VK_NV_fill_rectangle (ver:1)
  93/ VK_NV_fragment_coverage_to_color (ver:1)
  94/ VK_NV_framebuffer_mixed_samples (ver:1)
  95/ VK_NV_geometry_shader_passthrough (ver:1)
  96/ VK_NV_sample_mask_override_coverage (ver:1)
  97/ VK_NV_shader_sm_builtins (ver:1)
  98/ VK_NV_shader_subgroup_partitioned (ver:1)
  99/ VK_NV_viewport_array2 (ver:1)
  100/ VK_NV_viewport_swizzle (ver:1)
  101/ VK_NV_win32_keyed_mutex (ver:2)
  102/ VK_NVX_device_generated_commands (ver:3)
  103/ VK_NVX_multiview_per_view_attributes (ver:1)

Find VK_EXT_pipeline_creation_cache_control

and has been in the Vulkan branch for around a ballpark estimate of roughly 14,000 years, give or take a millennium.

March 17th, 2020, 442.75.

it has till september to clear 6 months of validation.

Neo Cyrus
Senior Member
Posts: 9554
Joined: 2006-02-14

#5812540 Posted on: 07/27/2020 03:28 AM

No, it doesn't.
You should do that thing everyone is able to and verify your claims.

Well you're so insistent on it, so I did, and...... it doesn't work, same error, yikes. I was absolutely sure my driver version showed as 451.48 and I had installed it. I was on the Vulkan branch for quite a while and was waiting for the GR driver, so I remember switching to that distinctly. My guess is I must have tried to directly install it over the beta Vulkan driver and it didn't work, but showed 451.48 anyway in the control panel, which is what just happened when I tested that with 451.48 on 451.85 to see if that happens. The problem with that is it literally says a newer driver is already installed when you do that, so if that happened that would mean I'm about 99% blind.

So... thanks for the correction. Is it possible something wacky happened when directly installing the GR driver the beta Vulkan driver aside from the version number shown? I can't believe I missed the "newer version" message.

Edit: And even that's a no go, 451.48 was posted June 24 and the Vulkan branch driver was 443.41 on June 23. Shouldn't give the "newer driver" message... and install? If you have any theories I'd like to know because the alternative of Alzheimer's doesn't sound great.

Astyanax
Senior Member
Posts: 8332
Joined: 2018-03-21

#5812542 Posted on: 07/27/2020 03:52 AM

brainfarts are a thing during this world crisis

NewTRUMP Order
Senior Member
Posts: 495
Joined: 2017-02-04

#5813244 Posted on: 07/29/2020 01:14 PM

Theres a thing called a support scope, when you do this it increases exponentially until nothing gets fixed and cards are just left unsupported upon the release of your next one.

Aka, Intel.

Now that I re-read my post, I failed to explain my self clearly, how rare. What I meant was, keep the support for the status quo cards under the cover all drivers, but make it a policy to make specific drivers for 3000 series gpu and beyond. Instead of having one large driver for 40 different gpu's. I don't know if it's easier to make drivers for 40 different gpu's at once, or make a driver for each series of gpu's from now on.

4 pages 1 2 3 4

Post New Comment

Click here to post a comment for this file on the message forum.