BSOD after getting a new monitor (Acer XB270H Abprz)


  1. Posts : 2
    Windows 7 Home Premium 64 bit
       #1

    BSOD after getting a new monitor (Acer XB270H Abprz)


    I have been experiencing a ton of computer crashes since I had gotten a new monitor. I know it is not due to a virus as my Kaspersky said there wasn't any. Sometimes when I am playing a game the GPU will get very loud then the computer will BSOD. I don't know very much about computers so any help is appreciated.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Update the display driver from Drivers - Download NVIDIA Drivers.

    When done, Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Let us know how the test went.

    Also, let us know for any further BSOD.
    _______________________________________
    Code:
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800c91a4e0, fffff8801001c7a0, 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+9a57a0 )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800c91a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8801001c7a0, 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+9a57a0
    fffff880`1001c7a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0fef16a0)]
    
    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.17237 (debuggers(dbg).140716-0327) amd64fre
    
    STACK_TEXT:  
    fffff880`05732b88 fffff880`10362134 : 00000000`00000116 fffffa80`0c91a4e0 fffff880`1001c7a0 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`05732b90 fffff880`10335867 : fffff880`1001c7a0 fffffa80`08034000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05732bd0 fffff880`10361f43 : fffffa80`ffffd846 00000000`00000000 fffffa80`0c91a4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`05732c80 fffff880`0f63803d : fffffa80`05ff3010 00000000`00000080 00000000`00000000 fffffa80`07bd9410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`05732d00 fffff800`0351cb8a : 00000000`02794d80 fffffa80`07882b50 fffffa80`054fb040 fffffa80`07882b50 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`05732d40 fffff800`0326f8e6 : fffff800`033fae80 fffffa80`07882b50 fffff800`03408cc0 fffff880`05732e40 : nt!PspSystemThreadStartup+0x5a
    fffff880`05732d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9a57a0
    fffff880`1001c7a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0fef16a0)]
    
    SYMBOL_NAME:  nvlddmkm+9a57a0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    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
    ---------
    
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f677000 fffff880`10305000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
        CheckSum:         00C4C7C9
        ImageSize:        00C8E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    Thanks Arc, I updated the Nvidia drivers and done the stress test. I didn't notice anything out of the ordinary but a low fps of 21.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    OK then. Now observe how it runs with the latest driver. Let us know for any further BSOD.
      My Computer


 

  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 14:54.
Find Us