BSOD 116 Error

Nthan · Dec 6, 2012

Hey, I'm just wondering whether you could help me with my problem. Approximately one month ago, I started having a BSOD error, in particular whilst playing games. It happens randomly, which is why I haven't been able to pin-point the problem. When it happens, the computer screen goes black (no signal message appears), looping crashing sound (even if there is no sound playing at the time of the crash) and the system would reboot again. When on the desktop, I have a 'Windows has recovered from an unexpected shutdown' which is where I got the BCCode 116 error. This is the rest of the information I am getting on this page:

Problem signature:

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:

BCCode: 116
BCP1: FFFFFA8007759010
BCP2: FFFFF8800FD56630
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Here are my system specifications (nothing is OC'ed):

Motherboard: MSI P67A-G45 (B3)
Processor: Intel i5-2500K
Graphics: nVidia 550ti (just purchased)
RAM: 4GB Mushkin
Sound: XONAR DG
HDD: WDC WD10EARX ATA
NIC: TP-Link Wireless N Adapter
Case: Coolermaster HAF

I purchased the computer sometime last year from a computer shop, it was the Gladiator Warbird V2 Intel Core i5-2500K.

So after much research, I was told it was generally to do with my graphics card - either overheating, corrupt drivers, broken graphics card etc. I initially made a clean install of the latest nVidia drivers, and even resorted to a new install of Windows 7 - still had the crash. I monitored the temperature of the graphic card, never went over 60c under full load. I tested both the memory and the HDD, no faults came up. When stress testing in particular, it was strange how software such as Furmark and IntelBurn didn't crash my computer, but a simple game such as League Of Legends that requires 2 GHz CPU and 1GB RAM does.

As it was still under warranty, I phoned up the computer shop and was able to RMA (return) for fault testing - it was a broken graphics card so I decided to upgrade to the nVidia GTX 670 and pay the difference. I've had it back for just over a week now, and I'm still having the exact same crash. I today even flashed my BIOS to the latest version (using MSI Live Update) and I'm still getting random crashes.

I have attached part of the dump file highlighted red (assuming there's where the problem lies) to the bottom of this post, hopefully someone can take a quick look and decipher it - as I have not got a clue! Thanks in advance for any help you are able to give, hope to hear off you soon,

Nathan

dxgkrnl.sys dxgkrnl.sys+5d000 fffff880`02c8e000 fffff880`02d82000 0x000f4000 0x4ce799fa 20/11/2010 09:50:50
dxgmms1.sys dxgmms1.sys+37dc0 fffff880`0f000000 fffff880`0f046000 0x00046000 0x4ce799c1 20/11/2010 09:49:53
nvlddmkm.sys nvlddmkm.sys+ade630 fffff880`0f0ed000 fffff880`0fde1000 0x00cf4000 0x506b3099 02/10/2012 18:21:13

zigzag3143 · Dec 6, 2012

Nathan

Can you follow the instructions here as we really need the actual DMP files. https://www.sysnative.com/forums/sh...D)-Posting-Instructions-Windows-8-7-amp-Vista

Thanks for the pre-work.

Nthan · Dec 7, 2012

Thanks for your help. I have followed those instructions. This is the information you wanted (including the jcgriff2 and Perfmon report which is attached) and will look at running Driver Verifier, HDD Diagnostics and Memory Test.

OS - Windows 7 x64, always used on this machine
OEM or retail - It is a full retail version that I purchased from the shop
Age of hardware - The hardware is one year old. I changed the graphics card from a 550ti to GTX670 so that is one week old
Age of OS - I've installed it once or twice recently to see if that would solve my problems. One week old

CPU - Intel i5-2500K
Video Card - nVidia GTX 670
MB - MSI P67A-G45 (B3)
PSU - Corsair CX600
Case - Coolermaster HAF
NIC - TP-Link Wireless N Adapter
Sound card - Xonar DG

Thanks for your help, hope to hear off you soon,

Nathan

writhziden · Dec 7, 2012

Recommendations:

MSI Afterburner is known to cause problems with Windows 7 and has been seen associated with the crash you are having. Remove the following programs:

NTIOLib_X64.sys Wed Oct 20 00:45:49 2010 (4CBE901D)
MSI Afterburner driver (known BSOD issues with Windows 7)
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys

dtsoftbus01.sys Fri Jan 13 06:45:46 2012 (4F10358A)
Daemon Tools driver
Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys

I also recommend you update/replace/remove the following driver:

xnacc.sys Mon Jul 13 18:01:05 2009 (4A5BCAC1)
XNA Common Controller Driver [XBox]
http://www.carrona.org/drivers/driver.php?id=xnacc.sys

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if possible.

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

[font=lucida console]**************************Thu Dec  6 18:27:28.623 2012 (UTC - 7:00)**************************
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
MBfilt64.sys                Thu Jul 30 21:40:32 2009 (4A7267B0)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
msibios64_100507.sys        Fri May  7 03:17:12 2010 (4BE3DA98)
HECIx64.sys                 Tue Oct 19 17:33:43 2010 (4CBE2AD7)
[COLOR=RED][B]NTIOLib_X64.sys             Wed Oct 20 00:45:49 2010 (4CBE901D)[/B][/COLOR]
athrx.sys                   Tue Nov 23 17:11:58 2010 (4CEC584E)
nusb3hub.sys                Wed Feb  9 22:52:32 2011 (4D537D20)
nusb3xhc.sys                Wed Feb  9 22:52:33 2011 (4D537D21)
cmudaxp.sys                 Thu Mar 10 00:44:15 2011 (4D78814F)
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 06:45:46 2012 (4F10358A)[/B][/COLOR]
Rt64win7.sys                Wed Feb 15 22:39:50 2012 (4F3C96A6)
GEARAspiWDM.sys             Thu May  3 13:56:17 2012 (4FA2E2E1)
nvhda64v.sys                Tue Jul  3 09:25:04 2012 (4FF30ED0)
RTKVHD64.sys                Tue Sep 25 06:06:24 2012 (50619E40)
nvlddmkm.sys                Tue Oct  2 12:21:13 2012 (506B3099)
aswrdr2.sys                 Mon Oct  8 02:23:43 2012 (50728D8F)
aswFsBlk.SYS                Tue Oct 30 16:43:04 2012 (509057F8)
aswMonFlt.sys               Tue Oct 30 16:43:09 2012 (509057FD)
aswTdi.SYS                  Tue Oct 30 16:43:16 2012 (50905804)
aswSP.SYS                   Tue Oct 30 16:44:06 2012 (50905836)
aswSnx.SYS                  Tue Oct 30 16:44:08 2012 (50905838)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec  5 17:38:54.179 2012 (UTC - 7:00)**************************
[COLOR=RED][B]xnacc.sys                   Mon Jul 13 18:01:05 2009 (4A5BCAC1)[/B][/COLOR]
[/font]

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

[font=lucida console]**************************Thu Dec  6 18:27:28.623 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\Nthan\Fault Research\Windows7_Vista_jcgriff2\120712-18345-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 8:30:24.825[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+ade630 )[/B]
BugCheck [B]116, {fffffa8007759010, fffff8800fd56630, ffffffffc000009a, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Arguments: 
Arg1: fffffa8007759010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd56630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.19
  BIOS Release Date             08/01/2012
  Manufacturer                  MSI
  Product Name                  MS-7673
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec  6 09:07:48.383 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\Nthan\Fault Research\Windows7_Vista_jcgriff2\120612-15116-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:26:31.226[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+ade630 )[/B]
BugCheck [B]116, {fffffa800b88e010, fffff8800fb10630, ffffffffc000009a, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Arguments: 
Arg1: fffffa800b88e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb10630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.11
  BIOS Release Date             04/14/2011
  Manufacturer                  MSI
  Product Name                  MS-7673
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec  5 17:38:54.179 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\Nthan\Fault Research\Windows7_Vista_jcgriff2\120612-19094-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:08:18.381[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+ade630 )[/B]
BugCheck [B]116, {fffffa8007b154e0, fffff8800fbcb630, ffffffffc000009a, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Arguments: 
Arg1: fffffa8007b154e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fbcb630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.11
  BIOS Release Date             04/14/2011
  Manufacturer                  MSI
  Product Name                  MS-7673
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec  5 15:30:02.018 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\Nthan\Fault Research\Windows7_Vista_jcgriff2\120512-19094-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:21:57.220[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+ade630 )[/B]
BugCheck [B]116, {fffffa800b5a1010, fffff8800fb07630, ffffffffc000009a, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Arguments: 
Arg1: fffffa800b5a1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb07630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.11
  BIOS Release Date             04/14/2011
  Manufacturer                  MSI
  Product Name                  MS-7673
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec  5 12:07:04.208 2012 (UTC - 7:00)**************************
Loading Dump File [D:\BSODDmpFiles\Nthan\Fault Research\Windows7_Vista_jcgriff2\120512-19078-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:07:08.425[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+ade630 )[/B]
BugCheck [B]116, {fffffa8006f68010, fffff8800faf0630, ffffffffc000009a, 4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Arguments: 
Arg1: fffffa8006f68010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800faf0630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.11
  BIOS Release Date             04/14/2011
  Manufacturer                  MSI
  Product Name                  MS-7673
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

Nthan · Dec 7, 2012

How would I go about getting rid of NTIOLIB_X64 if I haven't got MSI Afterburner installed? Thanks for your help.

EDIT: I uninstalled Windows Live For Games, Daemon Tools and MSI Liveupdate/Control Center. Hopefully this will help.

writhziden · Dec 7, 2012

It may be part of MSI CoreCenter or other MSI software installed on the system. See if removing MSI CoreCenter provides more stability.

Vir Gnarus · Dec 10, 2012

As a reference to other analysts, make sure to check 3rd bugcheck argument for any possible error code that the driver (or DirectX?) may have reported. In this case, it's c000009a, or insufficient resources to complete the request API call, which is a common problem with 0x116 bugchecks. It could mean either a driver is leaking memory (pool memory), insufficient RAM, or some resource contention issue.

I recommend if you find the latest crash a client experienced has this error code in the 3rd arg, ask them for a kernel dump. It'll contain the info you'll need to do most memory management analysis tasks, like !vm and !poolused.

Nthan · Dec 12, 2012

Hey Writh, I'm unsure whether you search this forum more actively than the Tech Support one seeing as your administrator on here. Here is my latest scan using the jcgriff2 utility - as I thought I got rid of anything related to MSI off my computer. Thanks for your help mate,

Nathan

Vir Gnarus · Dec 12, 2012

Can you provide a kernel dump for your latest crash? It's the MEMORY.DMP file in Windows directory. Archive it with zip, 7z, rar, whatever you prefer, and upload to some site like Mirrorcreator.com.

Nthan · Dec 12, 2012

Hey Vir, I've uploaded the memory .dmp file to my Sky Drive. Here is the link: https://skydrive.live.com/redir?resid=AAE1CD81F3CB07C4!198&authkey=!AI8bY7N66Dpt2WM

Also, as reference, this is what I have done so far with no resolve...

I was told it could be driver related. I used Driver Sweeper to uninstall the current nVidia drivers. I installed older drivers and error still happened. I done the exact same again with Driver Sweeper, but installed the latest beta nVidia drivers and the problem still occurs. This is bearing in mind I have used the most current nVidia drivers for public use also - no luck.
I was also told it could be something to do with DirectX. From what I know, you can't really repair or re-install DirectX, it's just part of the Windows OS. So with this in mind, I decided to install a fresh copy of Windows 7, but the BSOD error still kept cropping up.
To see the legitimacy of my hardware, I decided to run a few tests myself. I ran MEMtest which came back 100% pass. I also ran Furmark and IntelBurn for approximately 1 hour under 100% stress and there was no BSOD error.
I flashed the BIOS to the latest version after someone told me that could be the problem - problem still happened.
I was also advised that it could be something to do with my power settings - "I would suspect that your machine was idle and had changed sleep states, or low power states. I would also suspect that there is a bug in your electronics/firmware that is not handling your low power states correctly. video card not waking up, PCI bus at the wrong speed after wakeup, could be a lot of causes." With this in mind, I changed power-saving options to high performance in control panel and I went into the MSI BIOS and disabled anything related to their green power options (something many people had problems with whilst overclocking). BSOD 116 error still persists.
I've ran a CHKDSK - no error was found. I also reset my Pagefile size.

Again, thanks so much for your help,

~ Nathan

Vir Gnarus · Dec 12, 2012

Initial analysis has me finding avast being involved, the virtualization driver for it, and the driver is dated Oct 30, which seems to correlate with your predicament. Test that out, perhaps by disabling the virtualization portion of Avast or to just forgo using it at this time and using something like Microsoft Security Essentials for the meantime. I'll look into it further but that's what I found so far.

Nthan · Dec 12, 2012

Thanks so much for your help mate. I will uninstall Avast and will use another anti-virus for the time being. I will use the computer tonight - possibly have a few games - and post back tomorrow with my results so far. Again, thanks,

Nathan

Nthan · Dec 13, 2012

After removing Avast! and making sure the registry entries - in particular for the virtualisation feature - were fully removed, I had a good few games last night and early today with no problems. Then all of a sudden, bam, it happened again. I have posted the latest .dmp from five minutes ago.

Vir Gnarus · Dec 13, 2012

I'm still looking through the kernel dump. I'm trying to backtrace where originally the no resource error came from that's causing the held up driver, but I'm running into a bit of a snag. Suffice to say, though, your newest crash is identical to previous ones, except avast is no longer present.

I've read through your OP, and I think this actually may be either a bad motherboard, or you actually ran into a rare case where your replacement GPU ended up being bad, too! Either way, we're definitely dealing with some bad hardware here, but it's a matter of figuring just what.

You mentioned you ran Memtest. How many passes of it did you actually try? It should be at least 7 consecutive passes, one is simply not enough. I also recommend Prime95. Run that on Torture Test on Blend settings overnight, then another overnight run on Large FFTs. Report back on what crashed/errored and what didn't, and make sure that your CPU doesn't overheat when running this since Prime95 runs at max load!

Of course, there's also the potential your PSU could be bad, and is only bugging out when during higher load operations, especially when the GPU is involved. Unfortunately there's no definitive testing for it besides taking it to the shop or buying a diagnostic kit.

Analysts:

Nothing so far software-wise appears unusual. First I checked the TDR_RECOVERY_CONTEXT on Arg1 of the bugcheck. While I don't have any symbols for this, I decided to go dirty and just dump raw memory:

Code:

3: kd> dps fffffa80085ff4e0;dc fffffa80085ff4e0
fffffa80`085ff4e0  00000000`52445476
fffffa80`085ff4e8  fffffa80`09b72be8
fffffa80`085ff4f0  00000000`00000002
fffffa80`085ff4f8  00000000`00000080
fffffa80`085ff500  fffffa80`09b87000
fffffa80`085ff508  fffffa80`073f34c0
fffffa80`085ff510  00000000`00000000
fffffa80`085ff518  00000000`00038dfd
fffffa80`085ff520  00000000`00038dfd
fffffa80`085ff528  00000000`ffffffff
fffffa80`085ff530  fffff880`0520cb10 nvlddmkm!nvDumpConfig+0x2cdc38
fffffa80`085ff538  00000000`52445476
fffffa80`085ff540  00000000`00042caa
fffffa80`085ff548  00000117`00000010
fffffa80`085ff550  00040000`00000001
fffffa80`085ff558  00002005`00000007
fffffa80`085ff4e0  52445476 00000000 09b72be8 fffffa80  [COLOR=#0000cd]vTDR[/COLOR].....+......
fffffa80`085ff4f0  00000002 00000000 00000080 00000000  ................
fffffa80`085ff500  09b87000 fffffa80 073f34c0 fffffa80  .p.......4?.....
fffffa80`085ff510  00000000 00000000 00038dfd 00000000  ................
fffffa80`085ff520  00038dfd 00000000 ffffffff 00000000  ................
fffffa80`085ff530  0520cb10 fffff880 52445476 00000000  .. .....[COLOR=#0000cd]vTDR[/COLOR]....
fffffa80`085ff540  00042caa 00000000 00000010 00000117  .,..............
fffffa80`085ff550  00000001 00040000 00000007 00002005  ............. ..

While dpsdidn't show anything much worthwhile besides the nvidia driver doing a dump config, what I did notice was that this memory allocation starts with some ASCII characters that looks very much like a pool tag! As you know, kernel/driver memory resides a part of RAM reserved for them called pool memory. To my understanding all pool allocations by drivers are required to have an associated pool tag to identify itself, which typically come in 4 alphanumerics. In our case it's vTDR. So obviously we're looking at pool memory here, which we can get more details on via !pool, using the address we used to dump the contents with:

Code:

3: kd> !pool fffffa80085ff4e0
Pool page fffffa80085ff4e0 region is Nonpaged pool
 fffffa80085ff000 size:  170 previous size:    0  (Free )  CcPL
 fffffa80085ff170 size:   90 previous size:  170  (Allocated)  WfpH
 fffffa80085ff200 size:  210 previous size:   90  (Free)       CcSc
 fffffa80085ff410 size:   c0 previous size:  210  (Allocated)  WfpL
*fffffa80085ff4d0 size:  b30 previous size:   c0  (Allocated) [COLOR=#0000cd]*vTDR[/COLOR]
       [COLOR=#0000cd] Pooltag vTDR : Video timeout detection/recovery, Binary : dxgkrnl.sys[/COLOR]

So it is indeed, and as was hinted by the TDR_RECOVERY_CONTEXT name, the tag says it's associated with the video TDR, so this allocation of pool memory contains the recovery context, which is kinda hinted by Nvidia's nvDumpConfig function being present, which I assume part of the context has contents from the card's configuration. When checking the entire allocation, I didn't find anything of note other than it's a somewhat larger allocation (nothing unusual to my understanding) and has a large range of zeroed data, but that may just be to ensure whatever data needs to be dumped by the card can fit inside the allocation. Overall nothing I can personally find odd. However, I would like to know if perhaps the video card is running out of RAM to use, so I'll check with !vm:

Code:

3: kd> !vm

*** Virtual Memory Usage ***
    Physical Memory:     2089506 (   8358024 Kb)
    Page File: \??\C:\pagefile.sys
      Current:   8358024 Kb  Free Space:   8358020 Kb
      Minimum:   8358024 Kb  Maximum:     25074072 Kb
    Available Pages:     1314351 (   5257404 Kb)
    ResAvail Pages:      1950874 (   7803496 Kb)
    Locked IO Pages:           0 (         0 Kb)
    Free System PTEs:   33512065 ( 134048260 Kb)
    Modified Pages:        46961 (    187844 Kb)
    Modified PF Pages:     46827 (    187308 Kb)
    NonPagedPool Usage:    14816 (     59264 Kb)
    NonPagedPool Max:    1552404 (   6209616 Kb)
    PagedPool 0 Usage:     32245 (    128980 Kb)
    PagedPool 1 Usage:      6766 (     27064 Kb)
    PagedPool 2 Usage:      1624 (      6496 Kb)
    PagedPool 3 Usage:      1720 (      6880 Kb)
    PagedPool 4 Usage:      1698 (      6792 Kb)
    PagedPool Usage:       44053 (    176212 Kb)
    PagedPool Maximum:  33554432 ( 134217728 Kb)
    Session Commit:         7049 (     28196 Kb)
    Shared Commit:        108163 (    432652 Kb)
    Special Pool:              0 (         0 Kb)
    Shared Process:         7205 (     28820 Kb)
    PagedPool Commit:      44103 (    176412 Kb)
    Driver Commit:          8262 (     33048 Kb)
    Committed pages:      866927 (   3467708 Kb)
    Commit limit:        4178549 (  16714196 Kb)

    Total Private:        587401 (   2349604 Kb)
         0fe4 League of Lege  311834 (   1247336 Kb)
         0ae4 LolClient.exe   100257 (    401028 Kb)
         0074 svchost.exe      33119 (    132476 Kb)
         097c Skype.exe        32174 (    128696 Kb)
         0a18 explorer.exe      9597 (     38388 Kb)
         08bc svchost.exe       9340 (     37360 Kb)
         0db0 LoLLauncher.ex    8526 (     34104 Kb)
         09f8 dwm.exe           8091 (     32364 Kb)
         0518 AvastSvc.exe      8048 (     32192 Kb)
         0630 audiodg.exe       7374 (     29496 Kb)
         03d8 svchost.exe       5607 (     22428 Kb)
         0c1c SearchIndexer.    5217 (     20868 Kb)
         0230 csrss.exe         4533 (     18132 Kb)
         0164 svchost.exe       3952 (     15808 Kb)
         05b8 svchost.exe       2891 (     11564 Kb)
         0488 svchost.exe       2868 (     11472 Kb)
         0a50 nvxdsync.exe      2070 (      8280 Kb)
         042c svchost.exe       1988 (      7952 Kb)
         0c58 nvtray.exe        1854 (      7416 Kb)
         09d4 AvastUI.exe       1641 (      6564 Kb)
         059c spoolsv.exe       1517 (      6068 Kb)
         0a74 nvvsvc.exe        1448 (      5792 Kb)
         0dcc svchost.exe       1369 (      5476 Kb)
         0e8c wmpnetwk.exe      1338 (      5352 Kb)
         025c services.exe      1308 (      5232 Kb)
         0304 svchost.exe       1199 (      4796 Kb)
         0390 svchost.exe       1163 (      4652 Kb)
         07a4 iTunesHelper.e    1150 (      4600 Kb)
         0264 lsass.exe         1073 (      4292 Kb)
         0768 AppleMobileDev     917 (      3668 Kb)
         11a0 WmiPrvSE.exe       891 (      3564 Kb)
         07e4 rads_user_kern     872 (      3488 Kb)
         096c iPodService.ex     854 (      3416 Kb)
         0a80 taskhost.exe       836 (      3344 Kb)
         09a8 HsMgr64.exe        806 (      3224 Kb)
         0150 daemonu.exe        764 (      3056 Kb)
         078c mDNSResponder.     754 (      3016 Kb)
         0e9c wuauclt.exe        724 (      2896 Kb)
         034c nvvsvc.exe         723 (      2892 Kb)
         02a8 winlogon.exe       719 (      2876 Kb)
         09a0 rundll32.exe       711 (      2844 Kb)
         07f4 svchost.exe        709 (      2836 Kb)
         0270 lsm.exe            683 (      2732 Kb)
         0364 nvSCPAPISvr.ex     660 (      2640 Kb)
         01dc csrss.exe          549 (      2196 Kb)
         0380 svchost.exe        548 (      2192 Kb)
         0b74 jusched.exe        518 (      2072 Kb)
         07a0 nusb3mon.exe       511 (      2044 Kb)
         094c HsMgr.exe          500 (      2000 Kb)
         0218 wininit.exe        429 (      1716 Kb)
         0144 smss.exe           139 (       556 Kb)
         0004 System              38 (       152 Kb)
         0f98 chrome.exe           0 (         0 Kb)
         0eac SndVol.exe           0 (         0 Kb)
         0c68 ielowutil.exe        0 (         0 Kb)
         0440 PMB.exe              0 (         0 Kb)

All healthy, so there must be some oddity about the driver not having enough space. Perhaps it's looking for a contiguous memory region to use that it can't find, but while I doubt that, I can't prove or disprove it either with my current knowledge. Right now I just think we're dealing with some hardware fluke causing unusual behavior in an otherwise stable environment.

Nthan · Dec 13, 2012

Thanks for your help and time Vir Gnarus, I've really appreciated it. :smile9: Would it be worth taking the graphics card out and changing it to my second PCI-express slot - or wouldn't this make much of a difference?

Vir Gnarus · Dec 13, 2012

Well, you can try, and if it works great, if not, oh well, but regardless, if it does somehow work, then it just means your mobo is bad anyways and needs replacing, and that the bad slot is just conducive of that.

BSOD 116 Error

Nthan

Member

zigzag3143

Contributor, Sysnative Staff Emeritus

Nthan

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

Nthan

Member

writhziden

Administrator, .NET/UWP Developer

Vir Gnarus

BSOD Kernel Dump Expert

Nthan

Member

Attachments

Vir Gnarus

BSOD Kernel Dump Expert

Nthan

Member

Vir Gnarus

BSOD Kernel Dump Expert

Nthan

Member

Nthan

Member

Attachments

Vir Gnarus

BSOD Kernel Dump Expert

Nthan

Member

Vir Gnarus

BSOD Kernel Dump Expert