Originally Posted by born2bwild
Well I tried out both benchmarks, and my GPUs go through them easily with PhysX on or off.
But the problem persists; Metro, 3dMark Vantage and 3dmark 11 freeze with PhysX on and I have to quit the application with CTRL+ALT+del. When I turn PhysX off, I have no problems with any of the applications.
So I got a new idea; what if my overclock is stable for normal GPU purposes but is unstable with PhysX (though that would be pretty wierd)?
No. Overclocking of your cards being the culprit is very slim. It has to do with the Physx itself.
Also, when looking at EventViewer, the cause of the problem is identified as PhysXCore.dll... but what is interesting is that the faulting module path refers to a folder that isn't there (AGEIA Technologies)... I mean my PhysX engine is installed in the default NVIDIA folder.
This sheds some light into your problem.
You have no problem at all with Fluids and Star Tales benchmarks is because those are Nvidia-specific applications which know exactly where to find the PhysxCore.dll.
But when other applications (eg Metro 2033, 3DMark Vantage, 3DMark 11...especially if they were installed when you still had an AMD card) try to run Physx and have to access PhysxCore.dll, they are pointed to the wrong path.
They should be directed to: C:\\Program Files (x86)\\NVIDIA Corporation\\PhysX\\Engine\\v2.7.3\\PhysXCore.dll
(where v2.7.3 is the current version number of PhysxCore.dll file
Instead, they are directed to the Aegia file. Example below:
Faulting application name: Launcher.exe_Game Launcher, version: 126.96.36.199, time stamp: 0x4b0c1d66
Faulting module name: PhysXCore.dll, version: 188.8.131.52, time stamp: 0x4a84f7c4
Exception code: 0xc0000005
Fault offset: 0x001856c5
Faulting process id: 0x21e0
Faulting application start time: 0x01ca6e4b04c114ff
Faulting application path: c:\\program files (x86)\\steam\\steamapps\\common\\king arthur - the role-playing wargame\\Launcher.exe
Faulting module path: C:\\Program Files (x86)\\AGEIA Technologies\\v2.8.1\\PhysXCore.dll
Report Id: 9a6325de-da3e-11de-8042-0026185bc1e5
If this theory is correct, I think you might need to do a registry clean.
Let's see if anyone comes up with other ideas.