At least yours is semi working.. I have the GTS 450 ( uses the same drivers ) and mine doesn't work at all.. Stuck with the regular on-board driver atm and cant play any games... Microsoft tells me to wait a couple of weeks and to call back and Nvida says 10 ways to uninstall and re-install the same drivers. Hopefully someone with get a fix for this soon.
Hi guys,
Seems like it's not just me.
Just an update, I can't confirm it as a fix, but I haven't run into any problems (apart from a little screenlag) since installing the beta drivers. For me, the beta driver version is 310.33, R130. The only other change made to my system is updating the Adobe Flash version packaged with Google Chrome from 11.4.31X to 11.4.402 to eliminate severe problems when watching video in fullscreen.
System Info;
**Operating System:**Windows 8 Pro with Media Center 64-bit, Build 9200
CPU: AMD FX-8150 Eight physical cores
GPU: ASUS NVIDIA GeForce GTX 560 TI
Primary hard disk: OCZ Vertex 3 120GB
Hope it helps
Edit: Still no crashes, 02/11/12, 4 days
Further edit;
If you still receive the error message, try the following steps;
A. Try performing a clean install of the driver.
Download the latest drivers for your graphics card. Run the downloaded file and select 'Custom Installation'. On the next screen you'll see a tick box or similar labelled 'Clean Install'.
You can do this by visiting nVidia Driver Downloads (www.nvidia.com/Drivers). Either automatically detect the correct driver or download using the form. The best way in my opinion is to use GeForce Experience, which will do everything for you with two clicks and a restart.
B. Close all other programs
It's possible that the error was caused by too many programs needing to use the resources provided by the graphics card/chip. It is also possible that a certain program caused a conflict which crashed the drivers.
You can either try closing some currently open programs one by one and see if the error persists or reboot your system with startup programs disabled and enable them one by one to find the culprit. If the error is too persistent to do the above, an easier option would be to boot into safe mode.
More information can be found below