PC randomly restarts, goes into "coma" THREAD_STUCK_IN_DEVICE_DRIVER

  1. Posts : 9
    Win 10

    PC randomly restarts, goes into "coma" THREAD_STUCK_IN_DEVICE_DRIVER

    PC Specs:
    16GB RAM (8GB @ 1600, 8GB @ 2400 --> both set to run @ 1600 in BIOS)
    AMD 7950 3GB
    Sabertooth Z77
    2 SSDs + multiple HDDs
    EVGA 850w PSU

    If I leave my PC idle for about 15 minutes, I'll hear the motherboard-beep, meaning it's restarted, and then it'll go into this weird vegetable mode, where the only thing I can do is press the power button and it instantly turns off. No idea why. It's set to never sleep in power options.

    I run ccleaner a lot so I've accidentally got rid of a lot of log files and minidumps, but I have the most recent one. I think the other minidumps (I checked using bluescreenview) were also down to "asstahci64.sys".

    ZIP/dump link - DESKTOP-N2M7V27-22_08_2015_165420_18.zip - Google Drive


    EDIT: Had this problem before with Windows 8. Can't remember what fixed it, but I think it was either something to do with USBs, or my graphics card. Never occurred with 8.1. Pretty sure I remember going into device manager and unticking the box that says "allow the computer to turn off this device to save power" in the past, can't remember if that fixed it, but it's not working atm.

    Edit2: Attachment 33449
    Last edited by edd1234; 23 Aug 2015 at 16:25.
      My Computer

  2. Posts : 12,735
    Windows 11 Pro

    Edd1234, please run the Log collector again and upload the files here. This will tell you how. https://www.tenforums.com/tutorials/1...en-forums.html
      My Computer

  3. Posts : 9
    Win 10
    Thread Starter

    essenbe said:
    Edd1234, please run the Log collector again and upload the files here. This will tell you how. https://www.tenforums.com/tutorials/1...en-forums.html
      My Computer

  4. Posts : 12,735
    Windows 11 Pro

    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arg1: ffffe000679c6040, Pointer to a stuck thread object.  Do .thread then kb on it to find
     the hung location.
    Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: 0000000000000000, Pointer to offending driver name.
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
    ffffd000`e73ea7b8  fffff801`aa60465bUnable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Please go to your last post and in the bottom left corner click 'My System Specs'. there is a link there to update your system specs, click it and fill them all out in as much detail as possible. Please list Manufacturer and Model, and list Desktop or Laptop. If it is an OEM, please list the Manufacturer and Model number. Please be sure to list your PSU and CPU cooler. If you would like to know what we would like, please click 'My System Specs' at the bottom left of this post and see mine.
      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 16:52.
Find Us

Windows 10 Forums