black screen

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 2,259
    W7 Professional x64
       #11

    I am absolutely no good with minidumps, but perhaps someone else can decipher them :)
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #12

    Your crashes are being caused by a faulty graphics driver... Completly remove it with Driver Sweeper, then download the latest version from ATIs' website... Graphics Drivers & Software

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arguments:
    Arg1: 85f84a48, Pointer to a stuck thread object.  Do .thread then kb on it to find
    	the hung location.
    Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: 00000000, Pointer to offending driver name.
    Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
    
    Debugging Details:
    ------------------
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    
    FAULTING_THREAD:  85f84a48
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0xEA
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 9069fbbc to 8291ed10
    
    STACK_TEXT:  
    8e813944 9069fbbc 000000ea 85f84a48 00000000 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8e813988 9069834d 8e8139d4 00000000 90692673 dxgkrnl+0x11bbc
    8e8139b0 9025e420 8e8139d4 00000000 00000000 dxgkrnl+0xa34d
    8e813a00 9025bdae 9034be13 8e813a94 00000bb8 atikmdag+0x24420
    8e813a1c 90354f85 84fc8000 8e813a34 84ff3120 atikmdag+0x21dae
    8e813a74 9034c0e5 84ff3008 9034be13 8e813a94 atikmdag+0x11af85
    8e813aa4 9035c34d 84ff3008 00000000 00000000 atikmdag+0x1120e5
    8e813ad4 9035d2ad 00000000 84ff3008 8e813b08 atikmdag+0x12234d
    00000000 00000000 00000000 00000000 00000000 atikmdag+0x1232ad
    
    
    STACK_COMMAND:  .thread 0xffffffff85f84a48 ; kb
    
    FOLLOWUP_IP: 
    dxgkrnl+11bbc
    9069fbbc ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  dxgkrnl+11bbc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ac54de1
    
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys
    
    BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 24
    Windows 7 Home Premium 32bit
    Thread Starter
       #13

    Tews said:
    Your crashes are being caused by a faulty graphics driver... Completly remove it with Driver Sweeper, then download the latest version from ATIs' website... Graphics Drivers & Software

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arguments:
    Arg1: 85f84a48, Pointer to a stuck thread object.  Do .thread then kb on it to find
        the hung location.
    Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: 00000000, Pointer to offending driver name.
    Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
    
    Debugging Details:
    ------------------
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    
    FAULTING_THREAD:  85f84a48
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0xEA
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 9069fbbc to 8291ed10
    
    STACK_TEXT:  
    8e813944 9069fbbc 000000ea 85f84a48 00000000 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8e813988 9069834d 8e8139d4 00000000 90692673 dxgkrnl+0x11bbc
    8e8139b0 9025e420 8e8139d4 00000000 00000000 dxgkrnl+0xa34d
    8e813a00 9025bdae 9034be13 8e813a94 00000bb8 atikmdag+0x24420
    8e813a1c 90354f85 84fc8000 8e813a34 84ff3120 atikmdag+0x21dae
    8e813a74 9034c0e5 84ff3008 9034be13 8e813a94 atikmdag+0x11af85
    8e813aa4 9035c34d 84ff3008 00000000 00000000 atikmdag+0x1120e5
    8e813ad4 9035d2ad 00000000 84ff3008 8e813b08 atikmdag+0x12234d
    00000000 00000000 00000000 00000000 00000000 atikmdag+0x1232ad
    
    
    STACK_COMMAND:  .thread 0xffffffff85f84a48 ; kb
    
    FOLLOWUP_IP: 
    dxgkrnl+11bbc
    9069fbbc ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  dxgkrnl+11bbc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ac54de1
    
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys
    
    BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys
    
    Followup: MachineOwner
    ---------
    When I clean and after this I install drivers latest this didn't install, and when install complete then see,had didn't install ATI Display drivers... What I do bad?
    When install complete see this:
    Download Untitled.jpg
    and when see view logo:
    Download see_this.jpg
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #14

    Please fill in your system specs... It will make helping you a lot easier...
      My Computer


  5. Posts : 24
    Windows 7 Home Premium 32bit
    Thread Starter
       #15

    MSI GX623 Gaming Series Notebook
    ATI Radeon HD4670
    what more?
      My Computer


  6. Posts : 11,840
    64-bit Windows 8.1 Pro
       #16

    Download the drivers --> Here

    Once you download the drivers, try booting into safe mode, then install the new drivers..
      My Computer


  7. Posts : 2,259
    W7 Professional x64
       #17

    Run the drive sweeper as instructed by their page, then click this link:

    https://a248.e.akamai.net/f/674/9206...2-bit_util.exe

    download and run the program.
      My Computer


  8. Posts : 24
    Windows 7 Home Premium 32bit
    Thread Starter
       #18

    when download what do?
      My Computer


  9. Posts : 2,259
    W7 Professional x64
       #19

    it is an application, so just open it/run it
      My Computer


  10. Posts : 24
    Windows 7 Home Premium 32bit
    Thread Starter
       #20

    Tews said:
    Download the drivers --> Here

    Once you download the drivers, try booting into safe mode, then install the new drivers..
    Ok. I try and write what result of this
      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 19:18.
Find Us