BSOD 116 just started

I just had another crash while playing The Elder Scrolls V: Skyrim via Steam, trying to reproduce the crash (which I can't seem to, it appears random but happens a lot while playing this particular game).

No Phone plugged in
No External Hard drive plugged in


Uploaded to SkyDrive: https://onedrive.live.com/?cid=F6349...14D867BA%21115

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80552DF010
BCP2: FFFFF880067686AC
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040814-38501-01.dmp
C:\Users\A5ASIN\AppData\Local\Temp\WER-70621-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

ICit2lol said:

Windows Sniper said:

My PC has crashed more times with the phone unplugged over the last week since it's started, i have not had any issues recently with the phone being plugged in since I stopped Windows Auto updating quite a few months ago now, when I was having all the issues with BSODs related to USB 3.0 host controller and both 2.0 and 3.0 USB ports.

I do remember the last 4 or more crashes happened without my phone being plugged though.

I sometimes plug in an external hard drive (Western Digital 2 TB Passport) which I keep all my movies and backup files on and come to think of it, I used it recently was about a week ago when I downloaded a few movies.

Other than that I am trying to think what else would be storage other than my Samsung SSD 840 Pro 256, that is pretty much the only 3 things that I use with my PC regularly.

Hmm, ok then it was worth checking. But as you stated there is no error message on the shutdown event, which means it's not able to write it when it crashes.

I'll have a think and revisit this when I get in from work. But unless there is a circuit issue with the power, as in it's abruptly stopping for a few seconds, it looks to be a device issue.

Speaking of which, my machine only started playing this game after i changed the PSU....

Anyway i'll go have another think and get back with results.

well seeing as this started after the PSU was changed maybe it is worth looking at the PSU even though it is new..
Now I just know this will cause an outcry of not needed but I would be testing the via HW Info and a multimeter using these
HWiNFO, HWiNFO32/64 - Download

PSU - Jump Start and this for volts references especially the Power_Good at pin 8 on the 24 pin (grey cable)
Voltage Rails - Power Supply 101: A Reference Of Specifications
if it comes up ok at least it is eliminated.




















p[/QUOTE]

My power supply has never been changed in this PC, it is around 12 months old and everything was shipped from Dell and was a full Alienware package, it is all legit parts the only thing I have added to this PC is the Samsung 840 Pro 256 SSD a few months ago as a secondary storage for games, my main C drive is the factory 7200 3 TB seagate HDD which is where my OS is located.

When I tested the power supply initially, it came up ok and passed all scan tests and stress tests, it is the stock 850 PSU from Dell for this machine.

I can't figure out why the event viewer has gaps and misses the whole reason for the shut down in the first place, does anyone know why this happens?

Also, this WMI Application error shows up a lot too, usually after a crash when the PC is loading windows or possibly when the desktop it loading.


Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Arc said:

Hi ProdigyGamer.

A stop 0x116 is a display/graphics related issue.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Run Furmark on both the GPU, one by one.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the computer. It must be sufficient as I guess, still.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Install the NVIDIA DRIVERS 314.22WHQL only, at least as a test about how the computer is running with this driver. This test is needed to determine whether it is a hardware or a software related issue.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.
______________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8023cc9010, fffff8801029ce2c, ffffffffc000009a, 4}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9bbe2c )

Followup: MachineOwner
---------

11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8023cc9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801029ce2c, 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.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+9bbe2c
fffff880`1029ce2c ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0416ea48 fffff880`058f8140 : 00000000`00000116 fffffa80`23cc9010 fffff880`1029ce2c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0416ea50 fffff880`058cb867 : fffff880`1029ce2c fffffa80`24cc3000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0416ea90 fffff880`058f7f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`23cc9010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0416eb40 fffff880`059c703d : fffffa80`23d9a740 00000000`00000080 00000000`00000000 fffffa80`24cc2410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0416ebc0 fffff800`033162ea : 00000000`07bc0e71 fffffa80`23931060 fffffa80`19409b30 fffffa80`23931060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0416ec00 fffff800`0306a8e6 : fffff880`03b42180 fffffa80`23931060 fffff880`03b4d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0416ec40 00000000`00000000 : fffff880`0416f000 fffff880`04169000 fffff880`0416e480 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9bbe2c
fffff880`1029ce2c ??              ???

SYMBOL_NAME:  nvlddmkm+9bbe2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner
---------

11: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f8e1000 fffff880`10539000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This was the 3rd power test I did on the first page and it was showing well within the 850 limits for the stock PSU.

As I said, my PC isn't modified at all other than adding an SSD a few months ago.