Modern motherboards will also not include any chipset drivers for XP on their own website. Thankfully, a lot of motherboard components are actually from third parties (i.e., Realtek HD / AC97 audio) so you can look up the device hardware IDs and seek out XP drivers that way. It becomes a trade-off of how much time are you willing to spend chasing chipset drivers down or modifying existing drivers to work; if the system is functioning well enough for you to do everything you need then you probably don't need to worry about installing specific chipset drivers for the legacy XP install. For audio, if you cannot find drivers for your particular sound card and are not using on-board sound, consider purchasing simple USB-powered desktop speakers to alleviate the need of hacking together your own drivers for a modern sound card. Another option would be to embrace the HDMI/DisplayPort audio out if your display supports sound; the driver will be installed during the NVIDIA driver installation.
nVidia GeForce 64-bit Desktop Display Driver 340.52 (2014) download pc
@ john and anyone elseI too downloaded that file as it is for XP 64-bit. In the directory \\368.81-desktop-winxp-64bit-international\Display.Driver nv4_dispi.inf file does NOT have a [NVIDIA_Devices.NTamd64.5.1] section.
I'm troubleshooting why my 980ti will not display a refresh higher than 144hz on my asus 240hz monitor that works well on a windows 10 machine with same card. I thought display cable, but after switching the issues remain. My card is seeing my monitor in the nvidia control panel as TV? because it has "TV format" options as well as "Connector" with S or Composite standard settings under PC only 3 resolutions are seen. The options for all refresh rate choices exist, but selection of higher than 144hz results in a black screen. So, is this a driver issue? If so how to fix?
1.) After you have uninstalled the old graphics driver from "Add or Remove Programs" in WinXP Control Panel, it is goodfor AA quality to manually remove old driver remains from registry from at least 2 (3) key positions:a) HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Class/4D36E968-... (display adapter key), here you delete all the sub keys/directories, but the 4D36968-... key itself (it will come in handy for the new driver of course).b)HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/nv (nvidia display driver service), here you delete all the sub keys/directories, but the nv key itself (same as above).c)Optionally, if you want to have less clutter in the registry you can delete the grf. driver user key. Its name and location is contained within HKLM/Hardware/DeviceMap/Video: \Device\Video0, that points you toHKLM/System/CurrentControlSet/Control/Video. Delete only 1 key with the given name, leave 23A77..., 8B6D7... and DEB039CC... keys alone.d) Look in your WinNT (or Windows)/System32 directory - if there are any "nvmodes" (.whatever) files, delete them, leave others as they are.
2.) Install the modified display driver, restart the computer and then install monitor driver (for the right color management). Opening nvidia control panel only comes later, read on.Here I should mention that you can check if any other monitor color profiles (besides default sRGB) are present and making a mess by installing an old MS Control Panel addon WinColorSetup.exe.
Then you set your monitor resolution to the lowest (800x600, 32bit color) and Apply.Next, PruningMode has to be set (makes AA look good instead of sausage-like).You go to "Display Properties", "Settings" (we're already here from the previous step), "Advanced", "Monitor",you un-tick "Hide modes that this monitor cannot display", "Apply" and again tick the same and click "Apply".This way nvidia driver puts PruningMode = 0x00000001 into registry which it doesn't do by itself.
A nvidia disponibilizou dois driver de correção, um extra oficial que só se encontra no fórum da nivida (337.61) e a 320.18 e serve para crash quando a tela apaga de repente e volta e o windows diz (driver nvidia parou e se recuperou sem problemas). A microsoft disponibilizou a versão 347.52 para corrigir o erro(é o que eu uso), vi nesse driver que a microsoft excluiu o geforce experience, suporte a cuda cores e physx. Eu aqui instalei manualmente a physx e não tenho problemas com isso. 2ff7e9595c
Comments