TechSpot

BSoD upon non safe mode booting

By patricia016
Apr 25, 2015
Post New Reply
  1. Good day! Can you help me with my problem? Whenever I start up my laptop I will get Blue Screen. The only new applications/drivers I consciously installed are the mouse I borrowed from my friend and a copy of a game that I did not even install. I used up an online minidump reader and here is its analysis... I'm running a Sony Vaio S Series Windows 7 Home Premium (64-bit) THANKS!

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`03445890
    Debug session time: Sat Apr 25 01:45:51.379 2015 (UTC - 4:00)
    System Uptime: 0 days 0:00:46.800
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8009611260, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004253a2c, 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:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    FAULTING_IP:
    atikmpag+7a2c
    fffff880`04253a2c 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`0472f888 fffff880`042fa134 : 00000000`00000116 fffffa80`09611260 fffff880`04253a2c 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0472f890 fffff880`042f9e3e : fffff880`04253a2c fffffa80`09611260 fffffa80`08528d50 fffffa80`08784410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`0472f8d0 fffff880`04a0ff13 : fffffa80`09611260 00000000`00000000 fffffa80`08528d50 fffffa80`08784410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`0472f900 fffff880`04a39cf1 : 00000000`ffffffff 00000000`00000870 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0472f9e0 fffff880`04a38437 : 00000000`00000102 00000000`00000000 00000000`00000870 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`0472fa10 fffff880`04a0b2d2 : ffffffff`ff676980 fffffa80`08784410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`0472fab0 fffff880`04a37ff6 : 00000000`00000000 fffffa80`08528d50 00000000`00000080 fffffa80`08784410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`0472fbc0 fffff800`03514b8a : 00000000`037e3cf0 fffffa80`08445a00 fffffa80`042ceb30 fffffa80`08445a00 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0472fc00 fffff800`032678e6 : fffff800`033f2e80 fffffa80`08445a00 fffff800`03400cc0 77636c57`7477594a : nt!PspSystemThreadStartup+0x5a
    fffff880`0472fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    atikmpag+7a2c
    fffff880`04253a2c 4883ec28 sub rsp,28h

    SYMBOL_NAME: atikmpag+7a2c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atikmpag

    IMAGE_NAME: atikmpag.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4ef2ca56

    FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

    BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

    Followup: MachineOwner
    ---------
     
  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Your ATI graphics video driver is the cause of the BSOD's
     
    patricia016 likes this.
  3. patricia016

    patricia016 TS Member Topic Starter

    Thanks for this! Good thing my laptop has another video driver so I can just disable this one.

    The problem now is my laptop performs slower in this mode (Stamina vs Speed mode) and I want to install a newer update on this problematic ati graphics video driver. So I downloaded the one that suites mine which is AMD Catalyst Software Suite Omega (14.12) (for Radeon HD 6000 series) and during installation is says "Failed to load detect driver" and stops. Now I don't know what to do.

    This is my first time downloading this so there are no programs like this in my "currently installed programs". I tried uninstalling the driver in the Device Manager but it just reinstalls back. Thanks for the reply! Will make another thread for this separate problem too :) THANKS!
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...