BSOD After closing out of some games.

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    Windows 7 Home Premium 64 bit
    Thread Starter
       #11

    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 Computer


  2. Posts : 11
    Windows 7 Home Premium 64 bit
    Thread Starter
       #12

    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?
    Last edited by R34P3R; 03 Mar 2015 at 13:18.
      My Computer


  3. Posts : 26,863
    Windows 11 Pro
       #13

    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 Computer


  4. Posts : 26,863
    Windows 11 Pro
       #14

    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 Computer


  5. Posts : 11
    Windows 7 Home Premium 64 bit
    Thread Starter
       #15

    Use !analyze -v???
      My Computer


  6. Posts : 26,863
    Windows 11 Pro
       #16

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


  7. Posts : 26,863
    Windows 11 Pro
       #17

    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 Computer


  8. Posts : 26,863
    Windows 11 Pro
       #18

    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 Computer


  9. Posts : 11
    Windows 7 Home Premium 64 bit
    Thread Starter
       #19

    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.
      My Computer


  10. Posts : 26,863
    Windows 11 Pro
       #20

    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 Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 07:28.
Find Us