Windows 7: Multiple BSOD 116

Hello, thanks for taking the time to view my thread.
First id like to say that my system restore does not function. It returns some sort of error saying it was unsuccessful, every time i try it.



The BSODs error code ends in 116, which im told is graphics related.
Last year i began receiving these BSODs, and they gradually got more frequent to the point where i couldn't stay in Windows very long before it crashed, and eventually my computer wouldn't turn on. I was talking with someone on another forum and he advised me to rma the motherboard, after i tryed putting in a different graphics card which didn't help. The manufacturer found it faulty and sent replacement, which was around May/August time.

Everything seemed fine for a little while and i noticed one-two crashes, and checked event viewer which told me they where 116. I was kind of frustrated but since they where not frequent i put it out of my mind. Now though they are happening more frequently. I decided to check my graphics card in furmark, and it was running at 95C under load, so i got rma for it, and they said there was a lot of dust clogging it, but they said it worked fine after they cleaned it out. They sent it back to me. Iv had it just over a year now, so the warrenty was just about to run out when i sent it.

Im still receiving blue screens though unfortunately. Infact im not even sure if they are blue screens, since often im not at the computer when it happens, and i come back to find windows error message, saying error 116 occured. I have been at the computer when the thing froze up a couple of times and im wondering if it just freezes up and resets itself after a few mins, rather than displaying a blue screen.

Anyway, i don't know what to do, iv been getting a couple every few days recently, and i rely on my computer for my job. Any advice would be appreciated, and thanks very much for taking the time to read this.


System spec:
PSU: Corsair 850W TX Series
GPU: EVGA 470GTX
Mobo: Asus M4A89GTD PRO
Ram: 2x2GB G. Skill DDR3 1600mhz
CPU: AMD Phenom II X4 965 Black Edition
OS: Win 7 Home Premium x64 Full retail
Sound card: Auzentech Prelude
Harddrives: Seagate baracuda 320mb; Samsung 1TB 7,200rpm 32mb cache; WD My Book 1TB.
Optical drives: LG GGC-H20L Super Multi Blue Blu-ray Disc and HD DVD-Rom; LG-GH22NS30 22x Super multi.
Monitors: Dell UltraSharp U2412M 61cm (24''); Samsung SyncMaster 204B
Case: Antec900 Ultimate gamer

Hi and welcome to SF


In this order,

Remove kaspersky from your system for testing purposes.


For the moment download and install Microsoft Security Essentials with windows firewall enable.


Download and install the Driver Sweeper.

Download the most recent software\driver for your NVIDIA .

Uninstall nvidia software\driver,restart in safe mode,run driver sweeper,choose only NVIDIA-Display and clean,restart in normal mode.

Install the new nvidia software\driver,restart.

Update DirectX.

Run SFC /SCANNOW Command - System File Checker
You may need to run it 2-3 times to "fix" everything.


Run the nvidia-video-card-test post here the results.


Run RAM - Test with Memtest86+
Let it run until at least 7 passes are completed, or errors are found (whichever comes first). The longer you run it, the better.

Getting a nvidia tdr graphics failure from your debug results.

To be honest there's several things to try to clean this one up and I don't have any indication that any one of them is going to be more likely to fix things.
First two things I want to do is make sure your directx and .net framework are at least partially up to date.
Download: .NET Framework 3.5 Service pack 1 - Microsoft Download Center - Download Details
http://www.microsoft.com/download/en...s.aspx?id=9033
(this is to make sure we have all the basic windows components the video driver will want there)

After that is done reinstall the display driver package again.

looks like my friend beat me to it there. The driver scrub method is the second thing I was going to mention so you can just toss up the order in which to follow our advice, either or is likely to have an effect.

Thanks a lot for the tips. I will try all these and reply back.

Sry for delay in replying, decided to wait till i had few days off before attempting this.

@panais: Which driver sweeper did u want me to download? Is it neccessary? Since Nvidia has an option to clear old driver before installing new..

my directx is version 11, and it says version 9 in both your links..

I just tested system restore after removing Kaspersky and it worked fine. It seems Kaspersky was blocking system restore, what a huge security flaw for such a well known program.

I was actually just having a chat about this very thing
here - Why so long to delete files from external HDD?

Did you had\have any new problems after removing Kaspersky?

Hmm, i think blocking the ability to system restore is a different thing to causing file deletion to be slower, but thnx for the link anyway.

Actually yer, about 5 mins after rebooting from uninstalling it, the system had one of it's freeze ups. I waited a few mins to see if anything happened but got bored and hit the reset button.

Oh also, i double clicked to install .net framework, but nothing happened after i clicked run in the security warning box. I tryed again a bit later, but still nothing. Think i need to reboot again.

It says in the .net framework 3.5 page: "Supported Operating Systems: Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP"

Iv rebooted, and also re-downloaded the file from the link, but nothing happens once i double click, and click run on the security warning.

From what Magus saw, I did notice that the NTSTATUS error code for all the 0x116 bugchecks (Arg2 of the bugcheck) was the same: c000009a, which means "Insufficient system resources exist to complete the API." This means either that a request was sent to the video drivers that required more resources than was allocated to the drivers, or that the amount allocated to the drivers was smaller than what was requested. This sounds like the same thing mentioned both ways, but it means the request was either set too large, or the resources allocated was set too small. There's also a third possibility in that whatever resources allocated were sufficient, but were inaccessible at the time (most likely due to hardware failure). Either way, the driver as a result caved in, couldn't handle the request, and bugged out. Most likely we won't be able to figure out more details from just these minidumps.

You will want to first ensure that you aren't running out of neither virtual memory (paging file) nor physical memory (RAM). Second, to ensure that the VRAM on your GPU isn't whacking out, you should run MemtestCL on it a few times. I am aware that you got the video card sent back to you, but honestly, I think if your card has been permitted to run several times at that high of temperature, that I wouldn't doubt there'd be some manor of permanent damage wrought on it.

In addition to the previous Memtest, you'll want to run regular Memtest86+ on your RAM to ensure it's not that resource it's talking about that was bugging out.