No BSOD - just a crash when playing Prince of Persia :(


  1. Posts : 11
    Win 7 HP 64 bit
       #1

    No BSOD - just a crash when playing Prince of Persia :(


    DMP file attached. I've had issues with my system crashing at completely random times. I posted here before and got the recommendation that it could be vid card drivers. I updated those and thought I was out of the woods as I haven't had the random crashes. But I still get them when playing Prince of Persia, Sands of Time. Sad!

    Any help/suggestions are appreciated - thanks!!!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    menoseficaz said:
    DMP file attached. I've had issues with my system crashing at completely random times. I posted here before and got the recommendation that it could be vid card drivers. I updated those and thought I was out of the woods as I haven't had the random crashes. But I still get them when playing Prince of Persia, Sands of Time. Sad!

    Any help/suggestions are appreciated - thanks!!!

    this one was caused by you video driver. I suggest you compeletly uninstall all of the ati things and download and install a fresh copy

    Would also run a system file check
    type cmd in search>right click and run as admin>SFC /SCANNOW

    Let us know the results

    Ken



    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\012010-32557-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
    Debug session time: Wed Jan 20 15:49:36.009 2010 (GMT-5)
    System Uptime: 0 days 0:25:10.570
    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, {fffffa80047d9010, fffff88003a9bf68, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+12f68 )
    
    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: fffffa80047d9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003a9bf68, 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.
    
    Debugging Details:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'atikmdag' and 'atikmdag.sys' overlap
    
    FAULTING_IP: 
    atikmdag+12f68
    fffff880`03a9bf68 48895c2408      mov     qword ptr [rsp+8],rbx
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`066e49c8 fffff880`042b4ef8 : 00000000`00000116 fffffa80`047d9010 fffff880`03a9bf68 00000000`00000000 : nt!KeBugCheckEx
    fffff880`066e49d0 00000000`00000116 : fffffa80`047d9010 fffff880`03a9bf68 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
    fffff880`066e49d8 fffffa80`047d9010 : fffff880`03a9bf68 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
    fffff880`066e49e0 fffff880`03a9bf68 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`047d9010
    fffff880`066e49e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`042b4c02 : atikmdag+0x12f68
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+12f68
    fffff880`03a9bf68 48895c2408      mov     qword ptr [rsp+8],rbx
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  atikmdag+12f68
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b0447a4
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 202
    Windows 7 x64
       #3

    Just a little trick, use Driver Sweeper available throught guru3d website. When yours ATI drivers have been uninstalled throught the device manager in the configuration panel, right after run Driver Sweeper and select everything related to ATI.

    Do that before you reboot after uninstalling your ATI drivers.

    Pretty sure this can help sove any conflict betweens files.
      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 17:13.
Find Us