Recurring BSOD and computer failure over the last few months.


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

    Recurring BSOD and computer failure over the last few months.


    I have had recurring blue screens for about 3 months now. They used to be rare and would only appear once every week or so. I was lazy and didn't pay much attention.
    In the last month they have occurred all the time.

    They can appear due to:
    a) Playing a video game - the computer usually shuts down within 5 minutes of playing.
    b) normal usage of the laptop - They can happen every 4 hours, or every 30 minutes.

    Things i have to done to try and fix the problem:
    a) re applied thermal paste
    b) cleaned fans
    c) reinstalled drivers
    d) factory reset
    e) ran memtest86, CHKDSK, and CPU diagnostic tools, with no errors.
    f) scanned my computer for malware or viruses.

    After factory resetting the computer, the blue screens have become constant, and as a side issue my computer can not shut down/sleep and becomes unresponsive after 20 minutes ( I am unsure if this is due to the factory reset or to the ongoing problem). When it is unresponsive, CPU usage is near 0.

    My laptop is an Alienware m17x r4.

    I admit, I was pretty stupid to let the blue screens go on for this long :)

    Any help would be hugely appreciated.
      My Computer


  2. Posts : 21,004
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #2

    Hello and welcome JReyn mate some basic queries first is the machine a laptop or desktop as the Alienware is listed as a laptop and your specs which need to be filled in please say a desktop.

    System Info - See Your System Specs

    Now how old is the machine/ and what do you do with it OC?? The last bug check comes up with a graphics issue but we need to know just what machine you mean and the memtest how many passes did you run it for because it requires at least 8 passes to get any results - good or bad.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800d705010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f584034, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000a, Optional internal context dependent data.
    Debugging Details:
    ------------------
    
    FAULTING_IP: 
    nvlddmkm+153034
    fffff880`0f584034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fcb5b29)],0
    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`069ab888 fffff880`0532a134 : 00000000`00000116 fffffa80`0d705010 fffff880`0f584034 ffffffff`c00000b5 : nt!KeBugCheckEx
    fffff880`069ab890 fffff880`05329f0f : fffff880`0f584034 fffffa80`0d705010 fffffa80`0ebad610 fffffa80`0c16f410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`069ab8d0 fffff880`0520ff13 : fffffa80`0d705010 00000000`c00000b5 fffffa80`0ebad610 fffffa80`0c16f410 : dxgkrnl!TdrIsRecoveryRequired+0x273
    fffff880`069ab900 fffff880`05239cf1 : 00000000`ffffffff 00000000`000045b9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`069ab9e0 fffff880`05238437 : 00000000`00000102 00000000`00000000 00000000`000045b9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`069aba10 fffff880`0520b2d2 : ffffffff`ff676980 fffffa80`0c16f410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`069abab0 fffff880`05237ff6 : 00000000`00000000 fffffa80`0ebad610 00000000`00000080 fffffa80`0c16f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`069abbc0 fffff800`03162456 : 00000000`023e523a fffffa80`0c19f760 fffffa80`05a5d9c0 fffffa80`0c19f760 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`069abc00 fffff800`02eba2c6 : fffff800`03047e80 fffffa80`0c19f760 fffff800`03055cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`069abc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nvlddmkm+153034
    fffff880`0f584034 803dee1a730000  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fcb5b29)],0
    SYMBOL_NAME:  nvlddmkm+153034
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe
    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


 

  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 01:08.
Find Us