It could be but I very much doubt it, most NVidia users have it working perfectly. As the drivers are for ranges of cards I cannot see how more would not be affected. I tend to suspect SimConnect and the dll.xml which places items on the file menu. If this has been corrupted (more than likely) then here is your problem. Here is mine as an example of a working version......
Launch
dll.xml
False
False
Traffic Toolbox
False
False
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
Visual Effects Tool
False
False
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll
Level-D Simulations
False
False
Modules\LVLD.dll
FSUIPC 4
False
Modules\FSUIPC4.dll
PMDG Options
False
PMDG\DLLs\PMDGOptions.dll
PMDG Events
False
PMDG\DLLs\PMDGEvents.dll
PMDG Sounds
False
PMDG\DLLs\PMDGSounds.dll
Object Placement Tool
False
False
..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll
For the SDK file structure, I initially used SDK, SP1a and then SDK SP2, I now use SDK, SP1a and Acceleration only as items were missing from the file menu when used the other way. This information is only for FSX Deluxe and/or Acceleration users and fixes some problems between SimConnect and the file menu, namely missing features like the tools. The structure of the file still has to be correct in the first place, mine was achieved with a totally clean and orderly install of all parts. FSX, Acceleration for SP1 and SP2 inclusion, SDK, SDK SP1a, then Acceleration SDK. Result: one clean and working file menu in FSX and no problems.
Reider