BSOD 0x00000116 windows 8.1 64 bit

It may also be a faulty card. I would open the case and look and see if anything is damaged on it. It may also be overheating

I would perform a re-install of the OS then. A clean install would solve the issue if it's software-related.
If the BSOD still appears afterwards, it must be a hardware issue.
It's not necessary the problem to be in the card itself, it may lie in the RAM or the mobo as well. So I'd recommend to check them as well.
I'd suggest to make sure that everything is cleaned and there's no dust in the PC components, check all the fans, if everything is spinning freely. There are cases when the fix is a simple reseating of all components.

I hope this helps you.
Keep me posted!

the error indicates that graphics driver stopped responding to windows.
There can be many reasons for this. Hardware and software reasons.

most common software reason would be a deadlock between the various (3) threads of the graphics driver
two threads waiting for another thread to release a lock on memory and the last thread never releases the lock.
Most of the time it is a driver bug that has to do with timing, the faster the card the biger the timing gaps that allow the condition to happen.

you can change the timing several ways, use a tool to slow down your memory clock speed in your graphics card by 100 MHz
might reduce the timing windows. You can also eliminate one of the threads work. in particular if you don't use sound in your monitor you can go to
control panel, device manager, find the graphics card high definition audio device and disable it. It will change the timing window and allow the other 2 threads to work better because the last one does not have to process sound you may not be actually using via your video cable (hdmi, display port)

if you actually want to prove the cause is software related. you change your memory dump type to kernel dump,
set your system to do a memory dump via keyboard (in case you get a hang and no bugcheck) (google how to force a memory dump with the keyboard)
then run verifier.exe and set some debug flags to detect deadlocks and reboot. If windows detects a deadlock it will bugcheck and dump all the required info to the hard drive in a kernel memory.dmp file.

problem is you still have to wait to get a driver update from the vendor or underclock your GPU to work around the bug in the driver.
but you will know it is a driver failure or a bug in the BIOS of the graphics card.

verifier.exe is comes with windows. you start cmd.exe as a admin
then run verifier.exe and It will come up with a menu.

see http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
to see how to run/set it up.

when done be sure to turn verifier .exe off
verifier.exe /reset
otherwise windows will run slower because it is checking a bunch of device drivers for bugs.

verify debug settings check for common driver errors and bugcheck the system when the errors are made and tells you what driver made the error. Rather than a second driver bugchecking because the first driver corrupted its memory.
the normal bugcheck points to the victim of the corruption rather than the root cause of the corrpution.

With a system that stops responding or locks up, verifier forces a bunch of debugging information to be saved in then kernel dump that allows a person to use the debugger to dump the cause of why the system is not responding.
for example, deadlocks in code. One piece of code waiting for the other to finish but the other is waiting for the first to finish so nothing gets done and you wait until windows decides it has waited too long and bugchecks.

Just run your system as you normally would. If it locks ups and does not bugcheck, force it to bugcheck via the keyboard.
otherwise just wait for the next bugcheck to happen and provide the memory .dmp file.

if you have a usb mouse make sure it is running on a port directly connected to the back of the machine on the mother board. make sure it is connected to a USB 2.0 port and make sure your BIOS is set to wake the computer via the mouse.
the standard default will be to wake the computer via the space bar on the keyboard.
also, if it is a USB mouse, confirm that your BIOS does not have a setting that turns the USB ports fully off.
I had a old system and it was called a EU setting, added because to comply with new European union regulations to have computers save power. (not nice to turn off the USB ports to save power if you have a USB keyboard and Mouse you want to wake the system up with)

if you can't find a setting in BIOS that is turning off your USB port, then go to windows power management advance settings and find one for the driver and block it from going to sleep.

I would wake my machine, put it to sleep and do that for a few cycles and confirm it works ok before I started to overclock again.
You should also see if there are any low power link settings (sleep) settings for your graphics card. It could be that the card is put to sleep and there is a bug in the driver or hardware that is exposed when you try to wake the system up again.
if there are bugs in the driver or in the BIOS or BIOS of the GPU, windows 8.x will tend to expose them because the more advanced sleep states are enable by default. Window 7 has them off by default so many windows 7 users would not hit the various bugs in the driver/hardware.

- microsoft added that bugcheck to help people find the cause of their machine hangs (the display driver)
you only get the bugcheck if windows can get control and windows has detected a problem with the driver. The screen will refuse to update if window does not detect a problem and the driver responds( but does not update).

-the AMD driver is blanking the screen this is a low power link transition (sleep) and it does not unblank the screen and you need to find out why or if this is the direct cause of your problem.
I would tell windows to blank my screen after 1 or 2 minutes of idle and see if it will wake up. if it does not wake up then you know they have a bug in their hardware (circuit or BIOS on the GPU) or in the driver.

-I guess this assumes that the monitor's sleep functions are not kicking in after a timeout (depends on the monitor)
enter the monitor menus and make sure the monitor is not putting itself to sleep on a timer. my monitor has a energy smart setting that I turn off and give full sleep control to windows.

to test: You can also do this if it is the monitor. When the system is hung and will not wake up, power cycle the monitor
if it recovers then your GPU most likely is in a full power state and the signal to wake the monitor was not received by the monitor. this can happen with video cable setups. (combinations of video adapters and cables)

if you do get a bugcheck 116, it should not be the monitor's internal power saving features.
blank screen that will not turn back on could be either the monitor or gpu (drivers or hardware)

if the LLP low link power states are messed up in the driver, you can tell windows not to blank the screen and just power down the monitor to work around the problem until you get a fix.

There are ways to debug this if it is not your monitor or monitor cables.
you have to set windows to do a manually initiated memory dump via keyboard,
set your memory dump type to kernel memory dump.
run verifier.exe and set debugging flags to save special tracking info in the memory

then the next time the screen is blank and the system seems to be running but will not wake up,
you force a memory dump via the keyboard and look at it with a debugger.

I think your problem is going to be in the monitor not responding to the graphics signal. IE firmware/electronics problem with the monitor. I had a older samsung monitor that did this and I had to power cycle the monitor or unplug the cables and plug it back in to get it to come back on. The monitor was out of warranty and I ended up getting tired of unplugging cables to get it to work and got another monitor.

you might check the firmware in the monitor and make sure it is not set to go to sleep or a low power mode.
otherwise the circuit might have failed. (assumes that your cables are good from your monitor to your GPU)