BSOD after suspension, error 0x0000007e on Atikmdag.sys


  1. Posts : 2
    Windows 7 Ultimate x64
       #1

    BSOD after suspension, error 0x0000007e on Atikmdag.sys


    Hi, i think it's a driver problem.
      My Computer


  2. Posts : 1,810
    Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
       #2

    Code:
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff880058f2160, fffff88008b77c68, fffff88008b774c0}
    
    Probably caused by : atikmdag.sys ( atikmdag+cd160 )
    
    Followup: MachineOwner
    ---------
    
    Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
    0: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880058f2160, The address that the exception occurred at
    Arg3: fffff88008b77c68, Exception Record Address
    Arg4: fffff88008b774c0, Context Record Address
    Code:
    *** WARNING: Unable to verify timestamp for VirtuWDDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys
    Your bugcheck is indeed referencing a driver. It is your video card driver. I would uninstall VirtuWDDM.sys and update your videocard drivers. Im not quite sure but it seems like these two drivers may be conflicting with eachother.

    Update your Video card, if there is an update available, download that. If you have the most current try to redownload/install it. If that doesn't work, go down to the previous update and test

    AMD Radeon

    It appears that you have a BIOS update available, that may help

    Motherboards - P8B75-M LE - ASUS

    Sometimes this bugcheck can occur when you are running low on disk space, ensure this is not the case

    Try disabling Memory caching or shadowing in your BIOS. Try updating your BIOS first, if it doesn't work, try disabling this option if its present.
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks, i uninstalled Vitual VMP, reinstalled last video card drivers, updated Bios.
    I have plenty disk space available..

    The BSOD didn't appeared again...
      My Computer


  4. Posts : 1,810
    Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
       #4

    Great, give it a few days to a week and see if it happens again. If it doesn't happen again in that time frame, mark this thread as solved :)
      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 15:15.
Find Us