30 Replies Latest reply on Oct 31, 2017 11:25 AM by ysor123

    THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3

    ysor123
      • RX 480 (MSI gaming 8GB - NO OC)
      • Desktop
      • Windows 7 x64
      • Crimson 17.9.3
      • Display:
        • LG 34UC98-W 3440x1440 75hz over DP
      • Motherboard:
      • FX 8350 (NO OC)
      • PSU: Pure Power BQT L7 630W (88%)
      • RAM: 24GB (NO OC)

       

      All games randomly hang. It can happen after 5 minutes. It can happen after 3 hours. When lucky, it sometimes does not happen at all. The rendered content of window becomes black and nothing happens. You need to terminate the app. Sometimes it terminates by itself. There is also no BSOD, but windows notifies that it had to reset the display because it went into an infinite loop.

       

      After such a crash, when I try to open Radeon Settings, it crashes too. I checked windows events and it is always an 0xc0000005 exception code (access violation).

      An exaxmple of an event rom the radeon settings crash attached as "exception1.xml". I think it just expected something in memory area, that was freed and located elsewhere by windows, when it did the reset, hence the 0x5 crash.

       

      It does not seem to be related to GPU load. It even happen with very old games, where the GPU is not at heavy load and has 62° and ~100W consumption (chip only, but com on, even if the whole consumption is twice that much or even more it is still safe with the 630W). The highest the GPU even reach in temepratur is 73° for a moment. Usually it around is 69-71°.

       

      I do not have any kind of crashes, when not running 3D applications. With RX480 and previously the HD7870 (same issues), I had dozens of iterations of "DDU, clean install", over multiple crimson major versions without any changes. Recently I bought an SSD drive and therefore had a fresh windows installation with everything up to date (patches, drivers) and it did not fix the problem in any way.

       

      I initially had the FC bios version which is the last non-beta. Checking out the latest beta did also not resolve the problem (with default optimized settings too).

       

      I wanted to find out, if it also crashes when I run, lets say 3dmark11. The fist run did cause a BSOD. The second two runs did not.
      Initially I checked it myself via event monitor, but later found it easied with "whocrashed" tool, which confirmed my info:

      -----------------------------------------------------------------------------

      On Fri 13.10.2017 18:01:05 your computer crashed

      crash dump file: C:\Windows\Minidump\101317-12573-01.dmp

      This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)

      Bugcheck code: 0x100000EA (0xFFFFFA8019D61060, 0x0, 0x0, 0x0)

      Error: THREAD_STUCK_IN_DEVICE_DRIVER_M

      file path: C:\Windows\system32\drivers\dxgkrnl.sys

      product: Microsoft® Windows® Operating System

      company: Microsoft Corporation

      description: DirectX Graphics Kernel

      Bug check description: This indicates that a thread in a device driver is endlessly spinning.

      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

      The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

      -----------------------------------------------------------------------------

      On Fri 13.10.2017 18:01:05 your computer crashed

      crash dump file: C:\Windows\memory.dmp

      This was probably caused by the following module: atikmdag.sys (atikmdag+0x5A800)

      Bugcheck code: 0xEA (0xFFFFFA8019D61060, 0x0, 0x0, 0x0)

      Error: THREAD_STUCK_IN_DEVICE_DRIVER

      file path: C:\Windows\system32\drivers\atikmdag.sys

      product: ATI Radeon Family

      company: Advanced Micro Devices, Inc.

      description: ATI Radeon Kernel Mode Driver

      Bug check description: This indicates that a thread in a device driver is endlessly spinning.

      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).

      Google query: Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER

      -----------------------------------------------------------------------------

       

      Over the long period of troubles I can for certain tell, that it does not have anything to do with power draw or temperatur, because it happens random with measurements I did in background. They show no relation from crash moment to power or temperature. As said above, it can even crash on crapy old games. I would blame the game but the crash is the same type of crash as in new games.


      I did run memtest86+ for 5 hours without any issues detected. HDD damage is excluded, as it continues to hang/crash even with the new SSD I just recently installed.
      Not sure how "safe" it is, but any tools I used for V-readings did show it does not exceed the 5% neither negative, nor positive on load.

       

      Also tried run on 60hz, disable freesync and 1000 other things, which would blow up the post here.


      I had this kind of problem once - long time ago - which made me prefer nvidia cards. At some poin ATI/AMD managed to solve the driver problem (at least for me) and this made me like the products. Even though I kind of hate Nvidia and its policy for everything, I'm so annoyed by this now that even though I bought an freesync monitor, I think I will send the card back to amazon (~1 year warranty left) and replace it with an NVIDIA, when this isn't going to be solved soon.

       

      Kind of the last attempt for me here :-(

       

      Message was edited by: Matt B We have updated the title of this discussion with relevant details to better describe your issue.

        • Re: THREAD_STUCK_IN_DEVICE_DRIVER
          elstaci

          Try using the latest AMD driver from AMD Support. Its version 17.10.1 here: Desktop .

           

          This post from Windows Forum : Thread stuck in device driver - RX480 | Windows Forum indicated a conflict with another .sys driver on the computer. It also makes one or two suggestions to correct it.

           

          Here is a slightly older thread from this AMD Forum about the same issue with a RX-480. It also gives suggestions on how to correct the issue you are having. RX 480 BSOD and Driver Crash . This will probably be more of help than the link above from Windows Forum.

          1 of 1 people found this helpful
            • Re: THREAD_STUCK_IN_DEVICE_DRIVER
              ysor123

              As I said I have DDU & clean install over multiple MAJOR versions and the first thing you propose is try latest drivers ^^. Well I install them anyway, but I do not believe it will change much. Nothing in patch notes, that seem to be related to my problem.

               

              None of the apps and drivers on my system running, which were mentioned conflicting in the discussions.

               

              I'm not entirely sure what they mean by 150W max on PCIE and 6 pins. I have a 8 pin PCIE connector on the RX 480 (MSI gaming 8GB).

                • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                  kingfish

                  ** Windows 7 and Windows 8.1 must be fully updated before attempting to install any AMD driver. All 'critical', 'recommended', and 'optional' (no language packs,etc) updates as well as any Service Packs (SP) must be installed before any attempt to install graphics drivers. If you do not get this message .... keep installing until you do:

                  Screenshot_31.png

                  • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                    elstaci

                    Sometimes updating to the latest driver, even though it seems to not have anything to do with your issue, may fix the problem you are having with your GPU card.

                     

                    Also by taking an Attitude with post that you feel are not helpful isn't going to help your cause with future posts in this forum. 

                      • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                        ysor123

                        If you talk about the post with optional updates:

                         

                        I personaly never give someone hints to do something, when I do not know why it should help him. Although I very like to help people and explain why something is the way it is. I don't like to introduce "damage" to others though. The hint obviously looks like "no matter what there is -  I have no clue, - just install it all" - I argued why the post was such one.

                         

                        This method does not only not help fix the issue, it even increase entropy. This in turn can result in other issues, by adding up unnecessary changes. Many people are just unaware of this. The internet is full of "hints" like that. From the right point of view it looks like people suggest sorcery. Like dance around a pot of brew made of substances you don't know the effect of and it will heal you. Or propose exorcism as a solution for a health problem.

                         

                        In your post I agreed its a good point to install update, even though it is goind to unlikely fix it, since I did it for over a year now ;P Nothing of "attitude" there. It just takes a while to see if the problem is gone or not. And the other poins were good to check and useful. They actually might have been my issue, but sadly not .

                    • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                      ysor123

                      So after driver update yestereday for 3 hours no crashes. But only a coincidence. Today it crashed harder than ever. Usually windows manages to recover, but this time I got a BSOD (which I could not see, even though autorestart is off, but I know from dump and event monitor).

                       

                      -------------------------------------------------------------

                      On Tue 17.10.2017 19:49:13 your computer crashed
                      crash dump file: C:\Windows\Minidump\101717-12823-01.dmp
                      This was probably caused by the following module: atikmpag.sys (atikmpag+0xF818)
                      Bugcheck code: 0x116 (0xFFFFFA801CDE04E0, 0xFFFFF8800420F818, 0x0, 0x2)
                      Error: VIDEO_TDR_ERROR
                      file path: C:\Windows\system32\drivers\atikmpag.sys
                      product: AMD driver
                      company: Advanced Micro Devices, Inc.
                      description: AMD multi-vendor Miniport Driver
                      Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
                      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
                      Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
                      -------------------------------------------------------------

                      On Tue 17.10.2017 19:49:13 your computer crashed
                      crash dump file: C:\Windows\memory.dmp
                      This was probably caused by the following module: atikmpag.sys (0xFFFFF8800420F818)
                      Bugcheck code: 0x116 (0xFFFFFA801CDE04E0, 0xFFFFF8800420F818, 0x0, 0x2)
                      Error: VIDEO_TDR_ERROR
                      file path: C:\Windows\system32\drivers\atikmpag.sys
                      product: AMD driver
                      company: Advanced Micro Devices, Inc.
                      description: AMD multi-vendor Miniport Driver
                      Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
                      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
                      Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

                      -----------------------------------------------------------

                       

                          • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                            ysor123

                            Yep, they did not install important updates, and now? As you sure read I did. So what?

                              • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                                kingfish

                                Yeah I read what you said.

                                 

                                "I personaly never give someone hints to do something, when I do not know why it should help him. Although I very like to help people and explain why something is the way it is. I don't like to introduce "damage" to others though. The hint obviously looks like "no matter what there is -  I have no clue, - just install it all" - I argued why the post was such one.

                                 

                                This method does not only not help fix the issue, it even increase entropy. This in turn can result in other issues, by adding up unnecessary changes. Many people are just unaware of this. The internet is full of "hints" like that. From the right point of view it looks like people suggest sorcery. Like dance around a pot of brew made of substances you don't know the effect of and it will heal you. Or propose exorcism as a solution for a health problem."

                                 

                                Why did you even post a question looking for help? People try and suggest things to help, and you come back with third rate sarcasm 'because that won't work'.

                                 

                                So what? Go pound some sand...People like you should stick to Xbox.

                                • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                                  elstaci

                                  Seems like MSI upgraded your GPU card. According to this website ( PSU REQUIREMENTS - RealHardTechX ) all RX-480 are connected with a "6" Pin PCIe connector instead of an "8" pin PCIe connector. The 8 pin is a higher wattage usage than the 6 pin. Maybe you should contact MSI Support and see why they boosted the power requirement on your card. If its due to Overclocking, that could be a reason why you are having problems. This is only a suggestion.

                                   

                                  Also, as Kingfish mentioned, it is vital that your OS is totally updated via Windows Update. The latest drivers won't work correctly if it isn't. As you mentioned, some update doesn't seem to have anything to do with the AMD driver or GPU and see no reason to update. I can't answer you because I am not an IT specialist or programmer. But the AMD Software Engineers (RAY-M & AMD-MATT) both agree with Kingfish.

                                  If it is that important NOT to install some Optional Windows Update, Why don't you do a Restore point or System image of your computer, Totally update the OS and see if the problem is fixed. If it isn't, than restore your computer back before the updates or use the System Image (my personal best option) to restore it back to the way it was. BTW, Kingfish is somewhat of an expert on Windows 7 since that is the OS he uses to troubleshoot many of the problems posted on this Forum.

                                   

                                  I do agree that many "optional" windows updates are, to put it mildly, not perfect and adversely affects your computer. You can always uninstall the update that you believe is causing problems.

                                   

                                  By any chance, since you have a MSI GPU card, Do you have installed or using MSI Afterburner?

                                  1 of 1 people found this helpful
                                    • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                                      ysor123

                                      Thanks.

                                      I usually go the "safe" approach and try to exclude even the unlikelly things, but they still have some connection to the problem when I do so. I know well the issue with "but that is unlikelly going to help" myself by profession. This is why I anyway installed the driver updates (because its anyway a good Idea to have them up to date). I also did check many other things, that are rather unlikely but not impossible to be the issue.

                                       

                                      The thing is, that the only optional updates there are for more recent remote desktop protokoll, remote desktop service, connection and support for transport layer security on those remote desktop connection version 1.1 and 1.2. If you do not use remote desktop, you don't need it and fore sure a graphics card should have nothing to do with RDS, it would be a shame if it did. Installing them to fix the problem would be like fullfilling a dance around a pot of brew. I can guarantee you that this has not even a 0,00000001% relation to it. The service is not even running to cause some unexpected trouble. So in that case the dead binaries lying around there must be jumped into or executed by the driver, which would be totaly abnormal.

                                       

                                      Regarding the 6 pins. It looks like tests were made on the RX480 reference card and many have noticed, that it consumes more then spec max 75W from the PCIE slot, and it could potentially cause problems, especially when on CrossFire. I think that is why some custom cards have extended the 6 pins to 8 to take away load from PCIE/Board.

                                       

                                      Additionally, it looks like the card has an "out of the box" OC, at least when I compare to reference data. on max utilization, RAM runs on 2.000mhz and GPU ~1.305mhz.

                                       

                                      So the issue might be, that the PSU has enough power, but the GPU takes to much out of PCIE and the board makes troubles? Can it happen on low load though? Because it also crashes on very low load sometimes. I do not know how the power management manages (VRM?) where the power is drained from in which proportions (PCIE slot, pr PSU PCIE extension).

                                       

                                      I do not have MSI Afterburner installed. I thought about installing something (heavy benchmark) that can - for test purposes - maybe trigger the hang so that tests can be fullfilled faster and not random, but When the issue is with power consumption and in the case the above is true, I do not know if that is a good idea.

                                       

                                      Is The Radeon RX 480 Pulling Too Much PCIe Power And Killing Motherboards? - Legit Reviews (it is kind of open without a "resolution" feedback from AMD added in)

                                      AMD Radeon RX 480 8GB Power Consumption Results

                                      But also this, looks like it should have been fixed via software updated limitations: https://www.pcworld.com/article/3091128/components-graphics/amd-promises-fix-for-radeon-rx-480s-controversial-spec-excee…

                                        • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                                          elstaci

                                          You have posted some valid questions. Unfortunately, I don't have the technical background to answer them. Hopefully, one of the AMD Software Engineers (Ray-m or AMD -matt) who moderate this forum can answer you. Others  seems to have an IT background or are heavily involved with computers like Kingfish, Black Zion, or Redfury among others

                                           

                                          Redfury at this AMD Forum thread suggested downclocking the RX480 to see if it stops crashing : RX 480 give me this error "atikmpag.sys VIDEO_TDR_ERROR" , Try using AMD Wattman to underclock your GPU and see if it makes any difference.

                                          • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                            elstaci

                                            This OP mentioned about crashes on his MSI Rx480 card. I posted a link to this post. Maybe the two of you can get together to find a fix for the crashes that are occurring. Here is his reply from Latest AMD driver deletes all printers (17.10.1)!! . This is what he posted on an unrelated issue. :

                                             

                                            Re: Latest AMD driver deletes all printers (17.10.1)!!

                                            alleyviper

                                            Hi amdmatt, I've sent you a PM with a link to the DxDiag.txt file (under 16299.19 and latest Fall Update drivers, a combo that exhibits the problem). I've previously reported the issue with the web form.

                                            The new Beta Fall Update driver uninstaller also removes my printers (default MS Fax, Print to PDF, Microsoft XPS Printer, and Adobe PDF if present), both under current 16299.19 and previous 15063.674 W10.

                                            If there's any other driver install log file that could help to find this issue please tell me.

                                             

                                             

                                            I also have an unrelated problem to report related to 17.7.2 until 17.10.1 (all inclusive), they all cause issues on my MSI RX480 Gaming X when OC is applied either via Wattman or a reliable 3rd party tool like MSI AB (latest betas). If even a +1MHz OC is applied, when the card plays a video or similar non-3D loads that requires full clocks, voltage will be set constantly to 1.150-1.175V. Because this is a High ASIC card that runs only up to 1.043V under 3D stock (staying at ~1.032V under load), the GPU doesn't like it and ends up artifacting and then crashing the driver or BSOD with garbled screen on deskop/chrome/video use, even if it's stable on 3D (because the correct 1.043V will be used). For most regular ASIC card shouldn't have a problem, but for the few low voltage GPUs it hinders any sort of OC due to unexpectedly high values being applied under certain loads.

                                             

                                            The latest WDDM 2.3 drivers like the Fall Update don't suffer this, except if voltage is set to manual under Wattman. These latest drivers branch also have another small issue where applied memory clocks won't stay/show in the wattman respective slider that will always show default 2000, nor will they revert to default when resetting them. When I have time, I'll make a thread or report about it. Thanks!

                                              • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                alleyviper

                                                Unfortunately it seems an unrelated issue even if the card is the same model (1303/2000 8GB MSI Gaming X, .154 bios on mine). The issue I pointed only happens when a OC is applied in the affected drivers (via wattman, msi ab or msi gaming app), and under desktop/video use on a less common high asic card (low voltage). Even then gaming will run ok, because then card won't be overvolted on 3D loads. Still, to be sure that it isn't OC software related, please try to uninstall the MSI Gaming app if present.

                                                 

                                                Regarding slot power, custom cards like these should draw more from the 8pin PCI-E connector than the slot, unlike reference models. I'm using an old 790FX AM3 board that has Slot Power limit options on bios for each slot. Default is limited to standard 75W, but even if I don't touch it, I've never had what seems like a GPU power related crash while under load, setting it to max (255W) doesn't seem to affect the card.

                                                  • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                    alleyviper

                                                    Also, memtes86+ isn't really great to test for system stability or harder to find IMC errors that can make a game crash, 24GB can be a lot of load if some extra adjustments aren't done (could required more IMC voltage, relaxing timings or command rate, etc). Please try instead something like prime95 in blend mode, under a custom ~20GB of ram usage, and let it run for 4-8h, with special care to monitor temps to exclude your mb+cpu+ram as the main problem. Try also with only 16GB (8+8GB) according to ram specs and a 2T command rate.

                                                      • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                        ysor123

                                                        Going to do both. Might even be error in ram or maybe an issue with 4x chips configuration (did not know it is a problem, timings did auto sync when I checked after inserting and I thought that is enough as an "ok"). I currently have 2x4gb + 2x8gb. Actually I bought the 2x8gb all together with the RX480... But after some testing and only crashes in 3d context, not regular in system I thought ram is not a problem.

                                                         

                                                        Sometimes assumptions by symptoms, that two issues (hd7870 and now rx480) both have the same cause might lead to false exclusion of possible causes. For example if it is the same issue, the two new 8gb can be excluded as a problem. But as I found the problem I have might have dozens of different causes. And when you separate both from each another suddenly options like the 2x8gb which coincidentally were bought and inserted together with the RX480 to be the problem emerge: being "broken" or causing troubles because of the combo with the 2x4gb and timings.

                                                        • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                          ysor123

                                                          The first thing I did is to remove the 2x4gb. The 2x8gb are 2T. Yesterday nothing happened. Today something interessting happened for the very first time EVER on this system. Game crashed without any trace to amd drivers. It was an windows 0x5 (access violation). Shortly after that (~45min) a BSOD follwed on the same game:

                                                           

                                                          -------------------------------------------------------------------------

                                                          On Thu 19.10.2017 20:21:22 your computer crashed
                                                          crash dump file: C:\Windows\Minidump\101917-12604-01.dmp
                                                          This was probably caused by the following module: atikmdag.sys (atikmdag+0x72FD4)
                                                          Bugcheck code: 0xC2 (0x7, 0x109B, 0x40B0094, 0xFFFFFA8011CF3950)
                                                          Error: BAD_POOL_CALLER
                                                          file path: C:\Windows\system32\drivers\atikmdag.sys
                                                          product: ATI Radeon Family
                                                          company: Advanced Micro Devices, Inc.
                                                          description: ATI Radeon Kernel Mode Driver
                                                          Bug check description: This indicates that the current thread is making a bad pool request.
                                                          This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
                                                          A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
                                                          Google query: Advanced Micro Devices, Inc. BAD_POOL_CALLER


                                                          On Thu 19.10.2017 20:21:22 your computer crashed
                                                          crash dump file: C:\Windows\memory.dmp
                                                          This was probably caused by the following module: atikmdag.sys (atikmdag+0x50564)
                                                          Bugcheck code: 0xC2 (0x7, 0x109B, 0x40B0094, 0xFFFFFA8011CF3950)
                                                          Error: BAD_POOL_CALLER
                                                          file path: C:\Windows\system32\drivers\atikmdag.sys
                                                          product: ATI Radeon Family
                                                          company: Advanced Micro Devices, Inc.
                                                          description: ATI Radeon Kernel Mode Driver
                                                          Bug check description: This indicates that the current thread is making a bad pool request.
                                                          This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
                                                          A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
                                                          Google query: Advanced Micro Devices, Inc. BAD_POOL_CALLER

                                                          ---------------------------------------------------------------------------

                                                           

                                                          This is interessting, because 0x7 indicates it is a read after freed from memory. This could happen when data or code loaded into memory is corrupted (incorrect read or write). Maybe I just increased chance to hit an memory error by removing the other 8gb? The next two things I will do is switche the ram (down to the 2x4gb) and when that does not help (maybe both mailfunctioning) go prime95 test at WE when I have time to do it.

                                                          • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                            ysor123

                                                            No errors running prime95 for 10 hours... Going to switch to comparable nvidia GPU and see if that fixes it. If it function without any crashes I think almost certain it is driver issue on AMD's side then or manufacturing error on msi side. Either way, second card with similar type of issues (previous from XFX). If nvidia works without problems (still not sure) its a reason to avoid then amd for a while.

                                                          • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                            ysor123

                                                            Isn't the MSI card a modified version of the reference card with OC "out of the box" and OC being the "default settings"? When you tell "issue only on OC" you mean OC on top of this defaults, right? Just so there is no missunderstanding on my side.

                                                             

                                                             

                                                            I have the minimal installation, without any gaming app, etc.

                                                              • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                                alleyviper

                                                                When I wrote OC, it meant anything over the stock clock for the max p-state on bios which is 1303/2000 that needs to be applied via software. This is why my described issue on the other thread shouldn't apply in your situation.

                                                                 

                                                                On a side note: The MSI card has a completely different power delivery vs the reference model, and a higher available TDP (150W or 180W +50% power usage and other enhanced >A settings, depending on bios before or after .153 where limits where reduced a bit, while having the possibility to draw >225W via connectors, vs 120W +50% TDP on the reference model that shouldn't draw over 150W via slot+pci-e plug). This is so the MSI premium model doesn't throttle at the higher clock its sold at (the reference model can throttle even at 1266), while still having OC room. Other difference from most other RX480 cards are vram timing bootstraps on these MSI. If your vram seems to OC a bit less than most other cards reviewed, its because timings are tighter at >2000 than usual (same as the previous 1750 strap instead of being more relaxed). Depending on usage, this could be more effective than a higher OC margin available.

                                                          • Re: THREAD_STUCK_IN_DEVICE_DRIVER
                                                            alleyviper

                                                            The software fix on drivers for slot power consumption is only available for reference models, else the option won't appear on the global options.

                                                            If you missed, on my MB even if I set a 75W limit for the pci-e slot it sits on, the card won't crash stock or at 1316/2025 (MSI guaranteed OC for the model). Unless the setting is defective, it should clear this card from a slot power starvation (no problem running stuff like furmark).

                                                            I remember some reviews on custom boards where only a few phases were draining power from the slot, to avoid the reference model problem.

                                                • Re: THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3
                                                  ysor123

                                                  So it looks like only the BSOD dumps are place in minidumps folder. Most of the time I do not have BSOD. Only the game stops rendering and windows resets the display. Those dumps are written in a different folder I found. Now I added them up and that is the picture after my fresh system install:

                                                   

                                                  crash-list.png

                                                   

                                                  INTERNAL_POWER_ERROR is nothing special, even though it sounds like that. It was me running memory test in windows taking up to much RAM and windows going to sleep while I was AFK. The hibernate file size was to small for the ~22gb of memory allocate to wake up. This is a known bug in windows 7, which everyone can reproduce on perfectly working system. The corresponding thread:

                                                   

                                                  hibernate-bug-bsod.png

                                                   

                                                  The two BAD_POOL_CALLER dumps are the same crash, one user dump and kernel dump in a different location. (it was after the memory removal, but coincidentally - why? see below)

                                                  Notice: it happened 3 seconds after the VIDEO_TDR_TIMEOUT_DETECTED. The bad call happened from thread owned by the firefox process running at the same time. What happened is basically: Windows did reset the display driver (TDR), which includes releasing and reallocating memory (probably at different location). The BAD_POOL_CALLER then was a chain reaction by another process (firefox) attempting to free memory which was already freed. So it is not another error, but just random side effect of the TDR. RadeonSettings also crash when you try to open them after such a TDR. It does so with an 0x5 exception code (windows kernel) which is simply "access violation". It also attempts to read/write from memory, which windows probably released on recovery. The corresponding thread:

                                                   

                                                  bad_pool_caller.png

                                                   

                                                  The THREAD_STUCK_IN_DEVICE_DRIVER was the 1. test run in 3dmark11 which BSODed. The only one BSOD that is "different". corresponding thread:

                                                   

                                                  3dmark11_thread_stuck.png


                                                  So with one exception (THREAD_STUCK), all errors are always the same: TDR. Most of the time recover succeeded.

                                                  Note one interessting thing:

                                                  All the TDR errors happen always at the same location in atimpag module. The absolute addr is different just because the module is loaded at different offset at different boots. But otherwise the exception points to always the same offset in atimpag module, which is +0xf818.

                                                  Example the dump from 26.10.2017 has loaded the modules as follows (bugcheck arg 2):

                                                   

                                                  loaded-modules-1.png

                                                   

                                                  It is true for all the TDR errors, even those first to happen and the one failure to recover. And that includes at least two driver updates since then, when I recall correct. For me it does not look like some random error it would happen at totally random places.

                                                   

                                                  I kind of don't want to increase TDR timeout, because it does not feel like a solution for me. 2 seconds of not responding and artifacts on rendered surface does seem like not just "not enough time" but some error.

                                                   

                                                  * After update to 17.10.3 the offset shifted to (atikmpag+0xF948).