Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
USE AT YOUR OWN RISK :
1. Go to c,windows, system32.
2. Search for nvapi64.dll
3. Rename it to nvapi64_.dll
4. You might need to rename all of them if there is more than one. But start only with one and test.
Please note that after this change you nvidia controll panel,gfexperience and shadowplay might not work unless you rename files back and reboot pc.
I am also recommend using last driver version because i tested 441.41 vs latest and the latest has 15% more fpa and less input lag on rtx series gpus.
I've been running 537.34 with absolutely *zero* issues.
At overclock.net you can find a thread how amd agesa bios updates could flash certain set of instructions straight to your cpu increasing security but decreasing performance for 1-3%.
No wonder if nvidia doing the same with driver updates because it is proven to be real.
People even proved that newr nvidia drivers perform worse on GTX gpus.
Update your drivers and carry on with your day.
This issue has been covered by several large reliable websites, at least in the Japanese-speaking world.
https://www.gamespark.jp/article/2023/07/21/132286.html
https://www.nichepcgamer.com/archives/geforce-driver-issue-537-42.html
These websites suggest that blackouts occur in versions 536.40 and later.
The second website says that once this problem occurs, it may not be fixed by rolling back the driver, so it is suspected that the driver is causing hardware damage.
I have not read the content, but according to another page on the second website, the problem report is made in the Geforce thread. (This report is in English)
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/521773/geforce-grd-53640-feedback-thread-released-62923/
A detailed personal blog also addresses this information. His graphics board was actually physically destroyed by parts being scorched.
https://moshi-nara.com/21595/
According to him, the Diablo 4 blackout phenomenon reported on Twitter and Reddit actually turned out to be caused by a driver, not a game error, and this is what led to the discovery of this bug. You might want to translate the bullet points in the comments section at the bottom.
All of this information was released around mid-July to early August, and none of it has been followed up. Within Japan, this information is known among people with some Internet literacy. If this is not a malicious hoax, the information should be available in the English-speaking world.
Yeah, an overclock might actually happen.It is noted in the comments that there are no images of evidence, but according to him on the third website, these drivers have been shown to force overclocking.