CyberPowerPC - Unleash The Power

I purchased my PC in decentber 2010 and all has been fine since then, it has been regularly cleaned and updated with most recent drivers, has not received any overclocking aside from the initial overclock.

My origional Order Number was 73979

I am using a Watercolled 580.

The only Hardware added to the rig is a SSD drive to which i added the Windows 7 OS provided with the purchase.

On Friday 20th I turned off the pc as usual overnight, upon loading the pc the next day and logging into my game as normal the screen froze with an audible brrrrr and refused to do anything.

Forcing a reset i loaded up again to which it would not get passed the windows loading logo, i reset again and loaded in Safe Mode, to which i recieved an Error Report (which i no longer have) quoting Error#116.

The BSOD quotes the driver nvlddmkm.sys.

First i removed the nVidia driver by uninstalling it using cCleaner and then removing any drivers via Driver Sweeper. Rebooting and then adding the most recent driver.

This had no effect, so i retraced my steps and used an older driver from 2011, issue still persisted.

From there i tried only installing the Graphics and not the 3d Vision/HD Audio drivers, this also had no effect.

I then went on to perform a fresh install of Windows 7, barebones instalation, no other programmes, fresh install of nvidia driver.

Still same issue.

Is there anything i can do rectify this issue? anyone had and fixed a similar problem? or am i SoL.

Just tried to load a game again, SW:TOR, and after removing a programme called nVidia Inspector (which i used to override Biowares poor AA handling, it seems to work again.

Can a programme which alters game handling cause a 116 error? (taking into account ive used it for the past 4 months with zero issues)

Edited by billy341 - 22/Apr/2012 at 23:36

Originally posted by Cyber_Tech I've seen 116 from cards with excessive over clocks so take it easy and consider adding some GPU voltage as you crank up the clocks.

Thats the thing, ive not overclocked it, still running standard clocks that match the website specs.

Seems to be running ok, will see how it goes tomorrow.