minidump

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Abzolute, Jun 7, 2016.

  1. Abzolute

    Abzolute New Member

    Joined:
    Jun 7, 2016
    Messages:
    1
    Likes Received:
    0
    Hello, my computer only BSOD when I play Path of Exile.
    It's fine when it plays any other game or any other task, but only when playing this specific game do I have issues.
    Before it was an issue of my display driver constantly stop responding while playing the game, and now it became a BSOD issue.

    Here is the minidump file.
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,837
    Likes Received:
    1,566
    Hi Abzolute,
    just debugging your dump file now will post back shortly.
     
  3. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,837
    Likes Received:
    1,566
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8a018d61000, 1, fffff8801133d792, 0}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    
    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : atikmdag.sys ( atikmdag+115792 )
    
    Followup: MachineOwner
    
    Hi,
    bugcheck 50 means invalid system memory has been referenced and is usually caused by drivers although hardware (RAM) as well as AV suites can also be involved.
    The dump file says it could not read the faulting drivers name although I can see in the Call stack the the gpu driver was indeed involved.
    Code:
    FAILURE_ID_HASH_STRING:  km:x64_0x50_atikmdag+115792
    Please use this application to remove your current AMD driver as it will also remove anything else left behind by previous driver installs
    Display Driver Uninstaller

    AMD released a new driver today:
    AMD Radeon Software Crimson Edition 16.6.1 Release Notes

    As you had a bugcheck 50 please uninstall AVG and just use MSE for now:
    Microsoft Security Essentials - Microsoft Windows

    Please run a malware scan (it's free):
    Malwarebytes Anti-Malware Premium



    I also found this driver:
    ajtykt2l.SYS Thu Nov 27 12:14:42 2014: Any ideas?

    dtsoftbus01.sys Thu Jun 20 08:22:51 2013: Daemon Tools driver Possible BSOD issues in Win7 remove to test.

    Your device drivers could do with updating and you also have Bios updates relating to stability. Please don't attempt to update the bios unless you know what your doing.
    You can use your motherboard support for drivers:
    M5A78L-M/USB3 - Support

    Try the above changes and see if the bsod continues.

    Post any new dump files.
     

Share This Page

Loading...