locked
Blue Screen RRS feed

  • Question

  • 

    Hello There, I got a Blue Screen Problem, i Got The Dumb Files and Reported Files

    Can you check them and tell me, What caused this Problem ?

    Windows 7 Ultimate 32bit

    2 GB Ram

    Processor Core 2 Due

    Here is the Link for Dumb

    https://www.mediafire.com/?ea7b1xp0w8w5mxo


    Mohamed Mahmoud IT Specialist

    Wednesday, August 6, 2014 11:16 AM

Answers

  • ME

    You need to update to Service Pack 1 and I would replace McAfee with Microsoft security essentials

    These are called BCC116 and are video related.  To start you should install the newest driver available even if windows says you have the most current as drivers do become corrupt

    *

    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\Blue Screen\Minidump\080514-23961-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.x86fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0x8403b000 PsLoadedModuleList = 0x84183810
    Debug session time: Tue Aug  5 09:53:59.257 2014 (UTC - 4:00)
    System Uptime: 0 days 0:23:49.896
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .....
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {86332008, 906139b0, 0, 2}
    
    *** WARNING: Unable to verify timestamp for igdkmd32.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
    Probably caused by : igdkmd32.sys ( igdkmd32+119b0 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 86332008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 906139b0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    igdkmd32+119b0
    906139b0 55              push    ebp
    
    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.17029 (debuggers(dbg).140219-1702) amd64fre
    
    STACK_TEXT:  
    8be38b74 90b8badb 00000116 86332008 906139b0 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8be38b98 90b8c8fa 906139b0 00000000 00000002 dxgkrnl+0x8cadb
    8be38bbc 90bbc92c 00000000 00000102 87494788 dxgkrnl+0x8d8fa
    8be38c34 90be6a32 fffffcfb 00016535 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8be38c5c 90be7153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    8be38c98 90bc38f0 8be38c90 8739b4e0 872c37c0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    8be38d28 90be84b7 87494788 840766b1 87494788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    8be38d3c 90be8573 87494788 00000000 8750ed48 dxgmms1!VidSchiRun_PriorityTable+0xf
    8be38d50 84249b6f 87494788 a23d8e2e 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8be38d90 840fb299 90be84f4 87494788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    igdkmd32+119b0
    906139b0 55              push    ebp
    
    SYMBOL_NAME:  igdkmd32+119b0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: igdkmd32
    
    IMAGE_NAME:  igdkmd32.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a01d354
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
    BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x116_image_igdkmd32.sys
    
    FAILURE_ID_HASH:  {362d5027-3776-41be-95a6-4b6ffb51bdf2}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm igdkmd32
    start    end        module name
    90602000 90aff000   igdkmd32 T (no symbols)           
        Loaded symbol image file: igdkmd32.sys
        Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
        Image name: igdkmd32.sys
        Timestamp:        Wed May 06 14:13:40 2009 (4A01D354)
        CheckSum:         0048DF97
        ImageSize:        004FD000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Yolanda Zhu Thursday, August 7, 2014 2:21 AM
    • Marked as answer by ZigZag3143x Saturday, August 9, 2014 12:18 PM
    Wednesday, August 6, 2014 11:48 AM