BSODs at random times atikmdag.sys THREAD STUCK IN DEVICE DRIVER

Page 1 of 6 123 ... LastLast

  1. Posts : 39
    Windows 10 Pro
       #1

    BSODs at random times atikmdag.sys THREAD STUCK IN DEVICE DRIVER


    Hi,

    I have had BSODs for quite a long time now (before Crimson ReLive edition) and they all say THREAD STUCK IN DEVICE DRIVER. (I haven't done anything about it in a long time as I started using it less and my laptop more)

    I have taken quite a few steps to try to fix it:


    • I am using latest versions of AMD Crimson (16.2.2)
    • I have used DDU in recommended modes
    • I have cleared and updated motherboard BIOS
    • I have turned off the iGPU in BIOS
    • I have tried to find atikmdag.sy_ so I can expand it (but it is not found even when using the app, "Everything")
    • I have took apart my PC then rebuilt it (paying careful attention to GPU)
    • I have run DISM and sfc scannow now (no problems)
    • I have run Windows Memory Diagnostic tools (no problems)
    • I checked that the firmware of my OCZ ARC 100 240GB SSD was up to date (it was)


    I found out that the driver causing problems is atikmdag.sys from using BlueScreenView, these are the common things:
    • THREAD_STUCK_IN_DEVICE_DRIVER
    • 0x100000ea
    • dxgkrnl.sys
    • atikmdag.sys


    Here is a part list of what is inside my PC:
    CPU Intel Core i7-4790K 4.0GHz Quad-Core Processor
    CPU Cooler Cooler Master Nepton 140XL 122.5 CFM Liquid CPU Cooler
    Motherboard Gigabyte GA-G1.SNIPER Z97 ATX LGA1150 Motherboard
    Memory Kingston HyperX Fury Red 8GB (1 x 8GB) DDR3-1866 Memory
    Storage OCZ ARC 100 240GB 2.5" Solid State Drive
    Video Card MSI Radeon R9 390 8GB Video Card
    Case NZXT H440 (Black/Red) ATX Mid Tower Case
    Power Supply EVGA SuperNOVA GS 650W 80+ Gold Certified Fully-Modular ATX Power Supply
    Operating System Microsoft Windows 10 Pro OEM 64-bit

    Thanks,
    Alvie

    EDIT: It just had a BSOD again, here's the updated logs: Attachment 117125
    Last edited by Alvie; 14 Jan 2017 at 13:43.
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    The log files still point to the graphics driver. Did you try DDU to uninstall everything and then just reinstall the driver only?

    Have you tried running the memory in a different slot - no reason to believe it is a problem but you never know.
      My Computers


  3. Posts : 39
    Windows 10 Pro
    Thread Starter
       #3

    I tried that the first time I used DDU, but I haven't done the driver only the last time I did it. I'll try doing it again.

    I'll try running the memory in a different slot and report back :)
      My Computer


  4. Posts : 39
    Windows 10 Pro
    Thread Starter
       #4

    philc43 said:
    The log files still point to the graphics driver. Did you try DDU to uninstall everything and then just reinstall the driver only?

    Have you tried running the memory in a different slot - no reason to believe it is a problem but you never know.
    Just saw this:
    Attachment 117506
    Stays even after closing and reopening HWMonitor - faulty GPU?

    I haven't had a BSOD yet but I was only running the system for a few minutes.
      My Computer


  5. Posts : 39
    Windows 10 Pro
    Thread Starter
       #5

    philc43 said:
    The log files still point to the graphics driver. Did you try DDU to uninstall everything and then just reinstall the driver only?

    Have you tried running the memory in a different slot - no reason to believe it is a problem but you never know.
    I've done everything you said above, but it happened again:
      My Computer


  6. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #6

    There is no further information from the crash dump file that I can extract. You could try running a different hardware monitor program (e.g. speccy) to see if you get the same values.
      My Computers


  7. Posts : 39
    Windows 10 Pro
    Thread Starter
       #7

    Ok, I'll try that later.

    Thanks for helping by the way.
      My Computer


  8. Posts : 39
    Windows 10 Pro
    Thread Starter
       #8

    philc43 said:
    There is no further information from the crash dump file that I can extract. You could try running a different hardware monitor program (e.g. speccy) to see if you get the same values.
    Hi,

    I rolled back to AMD Catalyst 15.11.1 Beta drivers, and then expanded the atikmdag.sy_ file and replaced the old driver in Windows\System32\Drivers

    Is it safe to go back to Crimson now?

    Also, speccy is not telling me the voltage and HWMonitor is no longer telling it to me either. However, GPU-Z is and it seems to be normal (~0.8V to 1V on idle)
      My Computer


  9. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #9

    I would give it some more time to verify that you have eliminated the BSOD. IF you try and update and start getting the BSODs again you will know what to do and can then periodically test the newer drivers as they become available.
      My Computers


  10. Posts : 39
    Windows 10 Pro
    Thread Starter
       #10

    Ok thanks

    I'll give it some more time to ensure I don't have BSODs
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:51.
Find Us




Windows 10 Forums