Solved BSOD After closing out of some games.

[R34P3R]

When I close out of some games my monitor goes black and I stop hearing audio but the PC keeps running. After I restart the PC I get this error.

 

[essenbe]

Hello, R34P3R. I will try to help you with this. First it is important for you to fill out your system specs in as much detail as possible including your PSU and CPU Cooler. We have to look up components often and Manufacturer and Model are necessary.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

I have looked at your dump files and they are all the same. Please install utilities which will let you know your GPU temps and CPU temps at all times and let me know what they are.
+ Also, any additional information you have that could help pinpoint this would be very helpful. Does it happen only in one game or while running certain apps?

The dump files list

BugCheck 116, {fffffa8013326010, fffff8800f96451c, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=red]Probably caused by : nvlddmkm.sys[/COLOR] ( nvlddmkm+91951c )

Which of course is you graphics driver

[COLOR=red]VIDEO_TDR_FAILURE[/COLOR] (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8013326010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f96451c, 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.

This lists what type failure it is. A TDR failure (Time Delay and Response) basically means your drivers crashed and did not recover in the time allotted by Windows. Therefore Windows assumes it is a video failure and basically shuts down.

nvlddmkm
start             end                 module name
fffff880`0f05b000 fffff880`0fd2f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=red]Sat Sep 13 14:59:50 2014[/COLOR] (5414A236)
    CheckSum:         00C8E3A6
    ImageSize:        00CD4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This basically lists the driver you are running.

Please reinstall the latest WHQL driver using this method http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html. It should give you a clean install with nothing you don't use which can conflict with other drivers.

 

[R34P3R]

I re installed the driver using that guide and updated the specs. I turned on Far Cry 4 played for a bit 10-20 min then closed out of it. Monitor turns off and audio goes away but the fans keep running it does make that noise I hear every time I turn of my pc so it might be shutting down each time.
Additional info: It happens anytime I close out of Far Cry 4 and Assassins Creed Black Flag. I has happened one time when while playing Heroes of the Storm. And it happens at the ending credits on Far Cry 4.

 

[essenbe]

Post the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2 again. We'll see if it created a dump file.

 

[R34P3R]

Oh and I forgot to say anytime I would click Check for solution it would search for a few seconds then close...

 

[essenbe]

It's still the same thing

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

nvlddmkm
start             end                 module name
fffff880`048ec000 fffff880`052fe000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 05 12:01:37 2015 (54D3B001)
    CheckSum:         009D4DDE
    ImageSize:        00A12000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

From some of the error reporting, it appears that the games are crashing. Far Cry 4 and don't starve are showing quite a few crashes. Try going to the Steam Games folder, and verifying the game caches. If you are running a lot of mods, stop using them. Also, if you are overclocking anything, please set everything back to defaults.

 

[R34P3R]

It happened again while playing Heroes of the Storm. I cant verify the game cache for both those games I deleted them with quite a few others thinking it might have been my almost full HDD. The Graphics card is pre-overclocked and I don't know how to undo it.
I found this at the site I got it from.

 

[essenbe]

You can verify the games you do have installed. Far Cry 4 was installed as of the 28th. If you uninstalled the game, then just do the games you do have installed. Looking at your Windows error reporting it looks like you are getting an awful lot of errors from several games. I don't know if they are critical errors though. If they are critical errors it may be the game crashing and not the graphics driver. If a game crashed while you are playing it, the graphics driver will also crash by default.

To the best of my knowledge, you should not be able to install drivers for the integrated graphics if you have a dedicated card. All boards will by default, disable integrated graphics when it detects a dedicated card. The only exception I am aware of is if LucidLogix is enabled in bios and the program and drivers are installed. But you are getting some errors from the integrated graphics, it looks like. Some of those errors are hard to read.

 

[R34P3R]

Since I deleted Black Flag and Far Cry 4 I haven't been having any issues I forced myself to play Heroes of the Storm from 1 am to now and I exited twice during that time just to see if my pc would blue screen it didn't . I verified all the games on steam i left installed and none had anything wrong with them. I did the repair thing on Heroes of the Storm but It didn't say if there were any changes made it just finished and let me continue playing. I did have problems with Don't Starve Together it was just the game crashing a few times but I think that was because it had many mods + it is a beta. Black Flag, Far Cry 4, and Heroes of the Storm are the only ones I've had BSOD with. Is it really possible to have blue screened just because of one or two games? even when I wasn't on them?

 

[essenbe]

I really wouldn't think so, unless the games installed wrong or the mods were conflicting with some other drivers or files.

 

[R34P3R]

It happened again last night when I closed out of a game. The last two or three times it would give me a black screen and audio would go out like always but when turning on my PC it wouldn't give me the same "Windows has recovered from an unexpected shutdown." When using the dm log I noticed it said there were 8 dmp files which I think was the same amount as before.

 

[R34P3R]

It happened again just a bit ago this time I did get a blue screen msg after the restart. I was playing a game then alt + tabbed out of it and clicked a video.

Edit: I was looking through my control panel to see if there were useless things I could uninstall and I saw one of the things i have on my pc is Intel(R) Graphics Driver installed on 1/7/2015. I don't remember installing other graphics drivers and I was reminded about your earlier post about it having errors do i get rid of it or leave it alone? D: could that cause the problems i'm having?

 

[essenbe]

I'll look at your dumps in just a second, but you would be taking a little chance, but if it were mine, I would uninstall it. It should not be being used at all.

 

[essenbe]

Both of the dumps are the same
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8013326010, fffff8800f96451c, ffffffffc000009a, 4}
*** 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+91951c )
Followup: MachineOwner

 

[R34P3R]

Use !analyze -v???

 

[essenbe]

Did I or should you? It says graphics driver fault.

 

[essenbe]

Here's what I put and the output from analyze -v

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80114114e0, fffff88004fa4f38, ffffffffc000009a, 4}
*** 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+7a3f38 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80114114e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004fa4f38, 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+7a3f38
fffff880`04fa4f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`04e7e230)]
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.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`087cea48 fffff880`05270134 : 00000000`00000116 fffffa80`114114e0 fffff880`04fa4f38 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`087cea50 fffff880`05243867 : fffff880`04fa4f38 fffffa80`0f5e4000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`087cea90 fffff880`0526ff43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`114114e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`087ceb40 fffff880`0534003d : fffffa80`10b9fd50 00000000`00000080 00000000`00000000 fffffa80`0f56a410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`087cebc0 fffff800`03516b8a : 00000000`01f1b818 fffffa80`0f5df610 fffffa80`0cd69890 fffffa80`0f5df610 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`087cec00 fffff800`032698e6 : fffff880`02f65180 fffffa80`0f5df610 fffff880`02f6ffc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`087cec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+7a3f38
fffff880`04fa4f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`04e7e230)]
SYMBOL_NAME:  nvlddmkm+7a3f38
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001
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

 

[essenbe]

1. Keep close watch on CPU and GPU temps at all times

2. When you close the game out, try to close the game and then shut it down.

3. Kepp very close watch on your GPU temps and run Furmark (http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html) run it until the temps level out and stop increasing. Watch for artifacts while it is running.

4. Go into BIOS and tell me the values of you +12V, +5V and +3.3V.

5. If you have any Gigabyte utilities, uninstall every one of them.

 

[R34P3R]

I tried out the Funmark and used the steps given in your link. Ran it for 21 min the temp mostly stayed at 76°C then I pressed Esc to end it. The pc stoped working like it has been doing I got no blue screen error after restarting. My brother showed me this link Setting "Power management mode" from Adaptive to Maximum Performance and I did what it said and used Funmark again. Ran it for 21 min again the temp mostly stayed at 77°C then I pressed Esc and my PC kept working. o.o In there it says it can improve performance in certain applications when the GPU is throttling the clock speeds incorrectly so wouldn't that mean my GPU is messed up?
12.168v 5.070v 3.304
I would never have enough time to shut down the PC when I closed the game.

 

[essenbe]

That setting is a preference and shouldn't affect how it shows your clock speed. I use that setting too when I am running benchmarks. It can change your clock speed somewhat, but it should show it correctly.

I wouldn't think it would have anything to do with your PC shutting down the way I understand it is. If you think it is your GPU, the best bet is to ask your brother to swap GPUs with you for a couple of days and see how it does on his computer and how his does on yours.