|This is an interesting issue on an XP box, having to do with the NVidia driver (current 3.01??). The situation is this. I installed a GTX 260 card and the NVidia drivers, checked the frame rates for the kids, removed the 260 and installed a GTX 460 (Galaxie board) and compared framerates (virtually identical). Then I pulled in a second GTX 460 (EVGA board) and after boot into low res. mode so the new hardware driver discovery can take place and a reboot, when I login, I get a single instance of:|
The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll
Mind you, I'm sure there is a slight difference in the configuration and registry entries for 2 different vender versions of the same GTX 460 config, but both use the same/standard NVidia driver, and use it well. There is no notable problem that results from this error message, but it literally just appeared after I removed the NVidia GTX460 by Galaxy and install the NVidia NVidia GTX460. The cards are virtually identical.
In switching 3 cards in the last week, it is apparent that even if it is the same type of board, there is an individual registry data created for each individual card, as if it queues off some internal firmware or model no.
The 'entry point' complaint is nothing but a complaint that the kernel cannot find it's desired point to pick up processing for the code being run (either the NVidia driver or NVidia experience software). That would seem that there is a bad call address, but generated by what?? If each of these cards have somewhat separate set of registry entries that set the load environment for the NVidia code, where would that difference be?. There were no problems switching between the 260->460, but it seems to not have liked going from 460->460 cards.
That points me to one of the pieces of the registry config for the second card. I'll have to look in more detail, but I wonder if as the same type card was being replaced the load drivers/load audio/etc... may only create a partial config which is causing the second card to trip this error when the NVidia software loads.
I'm open for any suggestions as how to further diagnose, I can put the previous 460 back in and see if that solves the dialog error issue, but I would value thoughts any one else may have. Thanks.
message edited by Drankinatty