BSOD on Desktop Computer

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Master64, Mar 29, 2012.

  1. Master64

    Master64 New Member

    Joined:
    Feb 7, 2011
    Messages:
    10
    Likes Received:
    0
    Hello

    So, I got this BSOD on a desktop that's almost two years old, first time happening, I'm leaving the DMP file, I hope someone can help me =)View attachment DMP eMachines.zip
     
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    I would first suggest that you take care of this pre-Windows7 RTM driver.
    anodlwfx.sys 3/6/2009 update, uninstall or rename. Alpha Networks Filter Driver
    Then I would suggest that you consider updating your installation to Windows 7 Service Pack 1 x86.exe or x64.exe depending on your architecture after first having downloaded and installed the proper Update Readiness Tool
    System Update Readiness Tool for 32bit (x86)
    System Update Readiness Tool for 64bit (x64)
    Your single dump file:
    Code:
    [COLOR=#ff0000][U][B]BugCheck 116[/B][/U][/COLOR], {fffffa800696a010, fffff8800ff889c8, 0, 2}
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** 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+1759c8 )
    [COLOR=#ff0000][U][B]VIDEO_TDR_FAILURE (116)[/B][/U][/COLOR]
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800696a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800ff889c8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0ff889c8 4883ec28        sub     rsp,28h
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    CUSTOMER_CRASH_COUNT:  1
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff880`02db59c8 fffff880`10ae9000 : 00000000`00000116 fffffa80`0696a010 fffff880`0ff889c8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02db59d0 fffff880`10ae8d0a : fffff880`0ff889c8 fffffa80`0696a010 fffffa80`06249c00 fffffa80`0662d010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02db5a10 fffff880`10b8ff07 : fffffa80`0696a010 00000000`00000000 fffffa80`06249c00 fffffa80`0662d010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`02db5a40 fffff880`10bb9b75 : 00000000`ffffffff 00000000`00000792 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02db5b20 fffff880`10bb82bb : 00000000`00000102 00000000`00000000 00000000`00000792 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02db5b50 fffff880`10b8b2c6 : ffffffff`ff676980 fffffa80`0662d010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02db5bf0 fffff880`10bb7e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`06067738 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02db5d00 fffff800`02f776fa : 00000000`0450a96c fffffa80`06732770 fffffa80`03669890 fffffa80`06732770 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02db5d40 fffff800`02cb5b46 : fffff800`02e51e80 fffffa80`06732770 fffff800`02e5fc40 fffff880`0121b2b4 : nt!PspSystemThreadStartup+0x5a
    fffff880`02db5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0ff889c8 4883ec28        sub     rsp,28h
    SYMBOL_NAME:  nvlddmkm+1759c8
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Some information from NVIDIA regarding that TDR Failure NVIDIA Statement on TDR Errors - NVIDIA Forums
    And then if Blue Screens Persist
    First make sure your machine is configured properly to facilitate the collection of .dmp files.
    Then:
    Please read the first post in this sticky thread here How to ask for help with a BSOD problem
    Do your best to accumulate the data required.
    Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
    Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
    Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
    Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7-support/72212-help-us-help-you-filling-your-system-specs.html#post235529 .
    Good luck
    Randy
     
    #2 Trouble, Mar 29, 2012
    Last edited: Mar 29, 2012

Share This Page

Loading...