BSOD Thread stuck In Device Driver


  1. Posts : 94
    Microsoft Windows 10 Home 64-bit
       #1

    BSOD Thread stuck In Device Driver


    Every so often (once every two or three weeks) it's quite random, normally when playing games. The game normally freezes and then the BSOD occurs.

    I am quite good with computers on the basic side of things but all this BSOD solving seems quite complicated so I might get a bit confused sometimes .

    Here is the log from the collector and I filled in the specs from the program to the best of my ability.

    Hope you have enough info.

    Thanks in advance
    Attachment 67245
      My Computer


  2. Posts : 14,904
    Windows 10 Pro
       #2

    The crash was caused by your AMD display drivers, however I noticed you´re running version 10240.
    I would suggest to install Windows 10586 and see if that resolves the crash :)
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck EA, {ffffe0006e3b3800, 0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24 )
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff800`ae260000 fffff800`af9a7000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Dec 04 18:14:28 2015 (5661C9F4)
        CheckSum:         016E6BC5
        ImageSize:        01747000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


  3. Posts : 94
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #3

    I checked my build number and It said I am up to date. I also checked my system and I am running 10586 like you suggested. What should I do know?
      My Computer


  4. Posts : 14,904
    Windows 10 Pro
       #4

    Please run the tool again and upload a new zip, either the collected data is incorrect or your system is having bugs.
    Code:
    OS Version:                10.0.10240 N/A Build 10240
    I would suggest to run a System File Check if you haven't yet



    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  5. Posts : 94
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #5

    I am afriad I stupidly deleted the original minidump file and I only have that one zip collected from the DM collector. If I recieve another BSOD I will upload to here with the DM collector. I now know not to delete Minidumps!

    I ran sfc/scannow twice with a restart in between and they both said "Windows did not find any problem with integrity" or something like that. There is a CBS log though so If you want that I can upload it.

    BTW, My About system screen 100% says that I am running OS Build 10586. I don't understand why It says different.

    I hope you have enough info. Thanks again for helping me with my problem.
      My Computer


  6. Posts : 14,904
    Windows 10 Pro
       #6

    No log is needed :)

    Let me know how it goes, in case of another BSOD follow BSOD - Posting Instructions - Windows 10 Forums again with some description of what happened before the crash
      My Computers


  7. Posts : 94
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #7

    Thanks for replying Axe. I will carry on and if I recieve another BSOD in the next couple weeks I will post here. If I do not I will mark as solved. Thanks
      My Computer


  8. Posts : 94
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #8

    I have not had a crash since the time I posted so I am going to mark this as solved however if I recieve another BSOD can I reopen this thread or do I have to start another one.
      My Computer


  9. Posts : 14,904
    Windows 10 Pro
       #9



    It is better to start a new one.
      My Computers


  10. Posts : 94
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #10

    Ok I will
      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 23:45.
Find Us




Windows 10 Forums