Nvidia Registry / Reverse Engineering

[dsktherula]

Hello, recently some tweakers unveiled a new sauce called nvidia hidden dwords, how is it possible to reverse engineer nvidia, I'd like to know more if anyone knows anything about it, because either they keep it to themselves or they make people pay for it.

Screenshot_3.png (216.44 KiB) Viewed 13924 times

Screenshot_2.png (206.86 KiB) Viewed 13924 times

Screenshot_1.png (11.55 KiB) Viewed 13924 times

[thizito]

Thats not a New sauce, Just someone that is larping.
Now you know what is the term larp.

Start YOURSELF with ida pro, windbg and researchs.

Cause Who really know and found stuff Will never share.

What u Will see is ppl trying to larp and monetize
When its literally 1/20 or even 1/100 of the value of real things

[ahead]

Ida plus understanding assembler

[bleya99]

Hello, recently some tweakers unveiled a new sauce called nvidia hidden dwords, how is it possible to reverse engineer nvidia, I'd like to know more if anyone knows anything about it, because either they keep it to themselves or they make people pay for it.

Screenshot_3.pngScreenshot_2.pngScreenshot_1.png

Instead of me making a new post and having a "solution" I will just post this nugget here, perhaps someone can see it and hopefully test it. This was done on a fresh install. Try changing the setting in NVIDIA Profile Inspector called Memory Allocation Policy. The default is 0x00000000, test each setting (I restarted my pc, not sure if it is needed). On 0x00000001 and 0x00000002 the sensitivity is significantly faster. Perhaps this setting is often changed when importing various optimization profiles. This could "fix" the ice skating feeling.