Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD After closing out of some games.

03 Mar 2015   #11
R34P3R

Windows 7 Home Premium 64 bit
 
 

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.


My System SpecsSystem Spec
.
03 Mar 2015   #12
R34P3R

Windows 7 Home Premium 64 bit
 
 

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?
My System SpecsSystem Spec
03 Mar 2015   #13
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.
My System SpecsSystem Spec
.

03 Mar 2015   #14
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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

My System SpecsSystem Spec
03 Mar 2015   #15
R34P3R

Windows 7 Home Premium 64 bit
 
 

Use !analyze -v???
My System SpecsSystem Spec
03 Mar 2015   #16
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Did I or should you? It says graphics driver fault.
My System SpecsSystem Spec
03 Mar 2015   #17
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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

Code:
*******************************************************************************
*                                                                             *
*                        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
My System SpecsSystem Spec
03 Mar 2015   #18
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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 (Video Card - Stress Test with Furmark) 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.
My System SpecsSystem Spec
04 Mar 2015   #19
R34P3R

Windows 7 Home Premium 64 bit
 
 

I tried out the Funmark and used the steps given in your link. Ran it for 21 min the temp mostly stayed at 76C 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 77C 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.
My System SpecsSystem Spec
04 Mar 2015   #20
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.
My System SpecsSystem Spec
Reply

 BSOD After closing out of some games.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD when closing my games
hello I am new here and im not very familiar with how to post properly and im not very good at computers so can anyone please help me? ive read a thread telling me to get my "dump"? and upload it here. Im new to these forums things im not really sure if im doing it right so please bear with me....
BSOD Help and Support
BSOD Playing various games, closing games, no overheating.
Hello, first time poster looking for help as I can't diagnose my issue after trying numerous things. Currently when I play a game the BSOD happens randomly, I can go a whole day without it, or it can happen frequently. It happens the most when I close or exit a game, then it'll kick to a blue...
BSOD Help and Support
BSOD while closing the PC or closing some games, CDD.dll error
I need some help , sometimes when i try close the PC my screen gets error and it doesn't shut down, and when i start or close some games it gets me the BSOD error saying that there is a problem with cdd.dll Adress 972CB768 base at 872C0000 date stamp 4a5bd922
BSOD Help and Support
BSOD when closing games.
As said in the title, my BSODs happen AFTER I close my games, this includes Minecraft, Battlefield: Bad company 2, sometimes Starcraft 2, and Elder Scrolls: Oblivion... I usually get a "3B" BCCode, but i have gotten both "3B" and "1E". I recently reinstalled Windows 7, via a partition on my HP for...
BSOD Help and Support
BSOD when closing games
Hi! I had this problem about a month ago and I thought it was solved I last played Dragon Age: Origins but when I close it (not only this particular game) when the desktop shows up I got a BSOD The last problem was the cdd.dll and i replaced it with an uncorrupted one. But now it's at it...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App