Blue Screen BCCode 116

I have the solution! Download and install "Windows Kit WinDBG" go to file tab than Symbole file path, write down this command "SRV * c:\localsymbols* http://msdl.microsoft.com/download/symbols" (note that you might to change the C:\ to your hard drive letter where windows is install, i have 3 hard drive, E:, F:, C: and my windows is in C:) After that. go you here C"\Windows you will find the file "MEMORY.DMP" file, copy it to your desktop. Than go back to WinDBG file tab, than click "Open Crash Drumb" and open the "MEMORY.DMP" a bunch of text will appear, Find the text line "Use !analyze -v to get detailed debugging information." Click on !analyze -v more text will appear. Than look for the line "DEFAULT_BUCKET_ID: [...]" for me it was "DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT" that will help you get a very good idea of causing the computer problems. Mine was a Driver! Also!!! also look for the line "MODULE_NAME: [...]" Mine says "MODULE_NAME: nvlddmkm" The file nvlddmkm was corrupte, broken, KABOOM! witch was creating a bluescreen (tip: if a bleu screen stays, its most probably a hardware problem, if you see a bluescreen and it reboot right away its a computer configuration problem!) To fix my problem i followed these steps here: http://us.battle.net/d3/en/forum/topic/15700040439

Hope it was helpfull!

I have been experiencing 116 BSODs - 38 in 2015.  I have an nVIDIA graphics card, and I have tried various graphics drivers.  I even re-seated the card and installed a new card.  I have run each of my dumps (I have full dumps and minidumps for most of the BSODs) through WInDBG, and all have "MODULE_NAME: nvlddmkm".  I installed the latest driver 340.81 on 10/07, and two days later I experienced a 116 BSOD.  Today I copied the 341.81 nviddmkm.sy_ to \temp and then ran "expand -r".  The resulting file was identical to the Windows\system32\drivers\nvlddmkm.sys file.  THis seems to imply that my nvlddmkm.sys file is not corrupted.  All but one of the BSODs have occurred when I was not at the computer.  The one time when I was at the computer I was looking at a Windows Update window.  The window was not wide enough to see all of the information, so I went to make the window wider.  The system hung for one second and then rebooted with the 116 BSOD.  I would have thought that I would have experienced a longer "hang" time before the BSOD.

I have all of the dumps; I have a script that renames the MEMORY.DMP file to MEMORY.yymmdd.hhmm.DMP.  The nVIDIA support staff do not know what is happening.  Would there be anything in the dump (either full or mini) that would give more information as to what is happening?  I do not know enough about Windows 7 Professional (32-bit) internals to be able to determine anything from the dumps.

--Barry Finkel

I have been experiencing 116 BSODs - 38 in 2015.  I have an nVIDIA graphics card, and I have tried various graphics drivers.  I even re-seated the card and installed a new card.  I have run each of my dumps (I have full dumps and minidumps for most of the BSODs) through WInDBG, and all have "MODULE_NAME: nvlddmkm".  I installed the latest driver 340.81 on 10/07, and two days later I experienced a 116 BSOD.  Today I copied the 341.81 nviddmkm.sy_ to \temp and then ran "expand -r".  The resulting file was identical to the Windows\system32\drivers\nvlddmkm.sys file.  THis seems to imply that my nvlddmkm.sys file is not corrupted.  All but one of the BSODs have occurred when I was not at the computer.  The one time when I was at the computer I was looking at a Windows Update window.  The window was not wide enough to see all of the information, so I went to make the window wider.  The system hung for one second and then rebooted with the 116 BSOD.  I would have thought that I would have experienced a longer "hang" time before the BSOD.

I have all of the dumps; I have a script that renames the MEMORY.DMP file to MEMORY.yymmdd.hhmm.DMP.  The nVIDIA support staff do not know what is happening.  Would there be anything in the dump (either full or mini) that would give more information as to what is happening?  I do not know enough about Windows 7 Professional (32-bit) internals to be able to determine anything from the dumps.

--Barry Finkel

Barry - you noted that you have reseated, reinstalled, and swapped cards; thus, I would suggest that it may be a hardware problem unrelated to the card and driver. 

It could be a problem with the motherboard (e.g., the PCI slot or related circuitry). 

It could also be a problem with the power supply (PSU).  Do you have a brand-named PSU or a generic one and how old is it.  PSUs often die a slow death - they just don't quit working but rather sporatically create voltage problems caused by wear and tear of the PSU.  When this happens, you get the BSOD; but since the PSU is not consistently failing, it will still work. 

To test this, try to borrow a PSU and swap it out with the one you have.  Make sure the PSU has enough power to run your system (graphic cards can use a lot of power and the manufacturer will state the power requirements to run the card). If this solves the problem, get a new PSU. 

If it was me, if it wasn't the PSU then I would swap the mother board out but that can be a lot of work.

Here is an update.  I am looking for software that will log the motherboard voltages.  I have yet to find one that works.  But I am not sure that any software will be able to log successfully a voltage event, when that voltage event causes a 116 BSOD.  The software I have tested either 1) does not have a logging facility, or 2) the voltages logged in a test were not correct, or 3) I could not determine how to get the values logged.

My motherboard is an Intel DP965LT that I installed May, 2013 when my previous motherboard failed.  One of my brothers also suggested a PCI bus problem.

The power supply dates from December, 2009 and is a Thermaltake TT W0070RUC 430W.

I do not know the average lifetime of a power supply.

Back on 07/19/2013 I added HKLM\System\CurrentControlSet\Control\GraphicsDrivers\TdrDdiDelay with a value of decimal 10.  Two days later I added TdrDelay with the same decimal 10 value.  I just ran regedit, and I see that HKLM has been renamed to HKEY_LOCAL_MACHINE, and in the GraphicsDrivers level  I see five sub-levels:

     AdditionalModelLists

     Configuration

     Connectivity

     DCI

     UserNewKey

I do not see the items I added in July, 2013.  Do they still pertain to the timeout problem?  Should I re-add the entries?  If so, where - in the GraphicsDrivers level or a lower level?

Thanks.

--Barry Finkel