hans_glans Posted July 11, 2022 Share Posted July 11, 2022 On 9/6/2019 at 3:56 PM, halohalo said: Finally, I modified nvlddmkm.sys to prevent the unloading process. It also needs to be test-signed. To prevent the drastic performance decrease, I disabled driver signature enforcement before installation. FurMark test result: http://www.ozone3d.net/gpudb/score.php?which=787187 What do you mean by performance decrease? Caused by what? Link to comment Share on other sites More sharing options...
Ten2O Posted August 6, 2023 Share Posted August 6, 2023 (edited) How exactly would I find the hex value by kernel debugging? I try it but I don't understand what I need to do in order to find the memory address of the hex value that needs to be changed. I've been at it for a couple days straight and I still can't seem to figure out how I'm supposed to find it. I can pinpoint the moment that nvlddmkm unloads (the windows logo goes black) but I can't get it to happen without letting the OS load, meaning I can't find the exact point that it happens, despite trying for a really long time. I can't set a breakpoint there since there's no symbols and I don't know the address of the function that contains the version check... I also found this Edited August 6, 2023 by Ten2O Link to comment Share on other sites More sharing options...
halohalo Posted October 26, 2023 Author Share Posted October 26, 2023 Driver Release Branch 545 and later no longer support Version 1709 and earlier versions of Windows 10, so NVIDIA RTX and Quadro graphics cards will need INF modding. Besides, it seems that latest nvlddmkm.sys is still compatible with earlier versions of Windows 10. Link to comment Share on other sites More sharing options...
halohalo Posted February 6 Author Share Posted February 6 Starting with R530, the INF file of NVIDIA HDA driver no longer supports 32-bit version of Windows 10. Link to comment Share on other sites More sharing options...
halohalo Posted April 26 Author Share Posted April 26 (edited) On 10/26/2023 at 10:00 AM, halohalo said: Driver Release Branch 545 and later no longer support Version 1709 and earlier versions of Windows 10, so NVIDIA RTX and Quadro graphics cards will need INF modding. Besides, it seems that latest nvlddmkm.sys is still compatible with earlier versions of Windows 10. R545 and later no longer work on 1607. I've tried modifying R545 and R550 by overwriting OS version in nvlddmkm.sys, but only got error code 37. Now I am using 538.49. Because 1607 is too old to support latest DX12, I can't start Persona 3 Reload on Steam. So I have to use vkd3d-proton 2.12 and dxvk 2.2 to start the game. However, I can access digital art book and OST without converting to Vulkan. I think the game crashed because 1607 does not support ray tracing. Besides, latest OBS Studio 30.1.2 no longer works on 1607 because obs.dll uses isWOW64process2 function instead of isWOW64process, so obs.dll can't work without modification. Edited April 30 by halohalo Link to comment Share on other sites More sharing options...
halohalo Posted April 27 Author Share Posted April 27 Latest Nier: Automata on Steam offered two EXE files. One for old Windows without Windows HDR, the other one only works on Windows with Windows HDR. Without dxvk, the Windows HDR version only shows black screen with BGM. Although the Windows HDR version works with dxvk, Windows HDR can't be activated on 1607. Persona 5 Royal on Steam requires SetThreadDescription. Unfortunately the kernel32.dll of 1607 does not support the function and there is no utility like VxKex. So the game can't run on 1607 without modification. Link to comment Share on other sites More sharing options...
halohalo Posted May 4 Author Share Posted May 4 (edited) It seems that latest dxvk 2.3.1 and Vulkan driver 1.3.280 from R550 solved the performance hit issue in P3R on Steam when I use 538.49. I also tried using 474.82 but R470 is not compatible with Vulkan 1.3 so replacing Vulkan driver didn't work on DX 12 games like P3R. Intel's graphics driver for 7th-10th Core processors also supports Vulkan 1.3. Unlike NVIDIA, Intel and AMD have 8 driver files related with Vulkan. Edited May 4 by halohalo Link to comment Share on other sites More sharing options...
halohalo Posted May 5 Author Share Posted May 5 OBS Studio 30.1.2 can do Vulkan game capture with FrameView enabled by using display capture instead of windows capture. But February security update of NVIDIA driver still resulted in performance hit when playing P3R. Link to comment Share on other sites More sharing options...
hans_glans Posted May 12 Share Posted May 12 @halohalo I got the 3070 working on 1709 (472.12 and 466.77). Now for the 4070, the same hex tweaks don't work and the minimum supported driver is DCH only now (531.41). Which values do I modify for the driver to run with the 4070 on 1709 (16299)? Link to comment Share on other sites More sharing options...
halohalo Posted May 13 Author Share Posted May 13 Did you make 3070 working with R510 and later? Take 538.49 as example, I checked 385CB40h and added new codes to overwrite the information before comparing begins, then I broke the compatibility of adaptive G-sync on later version of Windows 10 like 21H2 by deleting useless codes. Finally I took time to correct the mess I made and completed modification. If you still can't make 3070 and 4070 work by such kind of modification, I will guess NVIDIA uses different way to prevent GeForce from working on old version of Windows. Good luck. Link to comment Share on other sites More sharing options...
hans_glans Posted May 13 Share Posted May 13 Thank you! I made 3070 work on driver 466.77 on Windows 1709 (build 16299). Here, this combination worked: 1. 00 7C 3F 00 (16252) replaced with 00 0F 3A 00 (14863) and 2. 00 AD 42 00 (17069) with 00 AB 3F 00 (16299)) For 4070 and driver 531.61 (531.41 is the earliest driver supporting 4070) on 1709, I don't know what to modify. I'm not experienced with WinDbg to find the new hex values to modify via debugging. This is especially difficult because "1803" being the minimum Ampere/Lovelace winver requirement could mean beta builds from 17069 to 17763. So this would be a lot of trial and error without proper debugging. How do I debug the .sys file to nail down the values to change? 1 Link to comment Share on other sites More sharing options...
halohalo Posted May 13 Author Share Posted May 13 (edited) What I've told you has nothing to do with debugging, I can't teach you the answer you need because I am not a programmer. Instead I told you the solution I used, so you can run IDA and hex editor to modify the driver. Officially the minimum requirement of Quadro DCH driver is 17098. That is why 1803(17134) is required. But old minimum requirement in standard driver still works so Tuning GPUs still work on 1709 with DCH driver. If GeForce DCH driver requires 1803, I think 1803 should be enough for Ada Lovelace GPUs. Edited May 13 by halohalo Link to comment Share on other sites More sharing options...
D.Draker Posted Sunday at 07:11 AM Share Posted Sunday at 07:11 AM On 5/13/2024 at 5:45 PM, hans_glans said: How do I debug the .sys file to nail down the values to change? Nvidia driver debugging (full instructions, very rare!) Huge PDF file, 44mb. https://neowutran.ovh/qubes/articles/nvidia.pdf 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now