This is also my feeling.
@Circinae:
>You can even monitor the clock speeds to watch when it triggers.
This is normal and happens also in 15.12. The clock speeds are supposed to change based on the GPU load.
Windows 10 Frequent, Semi-random BSODs (Thread stuck in device driver)
- Thread starter SpaceKitkat
- Start date
@Circinae:
>You can even monitor the clock speeds to watch when it triggers.
This is normal and happens also in 15.12. The clock speeds are supposed to change based on the GPU load.
SpaceKitkat
Member
@sven31415 I use.. whatever the latest version is. I'm not sure. And whatever the default settings are, I haven't messed around with it yet. lol
Lol. There is already a new one ? I can continue like this forever. This is not efficient. AMD has to analyze now the change that broke it.
It is quite simple. The use their version control system make a diff of the changes and then make suspicous changes optional.
Best would be to make them optional by using a special registry key.
Then we could test the single changes by switching them on/off and find the change that breaks it..
I doubt they will do. I spend already too much time with this. I should just buy a new video card and thats it.
15.12 is also not too bad for the time being. At least it does not crash.
It is quite simple. The use their version control system make a diff of the changes and then make suspicous changes optional.
Best would be to make them optional by using a special registry key.
Then we could test the single changes by switching them on/off and find the change that breaks it..
I doubt they will do. I spend already too much time with this. I should just buy a new video card and thats it.
15.12 is also not too bad for the time being. At least it does not crash.
SpaceKitkat
Member
So.. I'm still getting BSODs.
In my DREAMS!
Lol almost every night I've had a dream of getting a BSOD.
I find it kind of funny, tbh.
That said, I haven't gotten a single BSOD since running Clockblocker, and it's been.. 5 days? Fingers crossed, I suppose.
So far, I've never had the issue where my GPU is running at max. My fans are all normal, I assume my clock speeds are normal (I haven't actually checked tbh).
Again, could just be entirely coincidence (I've gone over a week without BSODs before, with nothing having changed).
@kemical I know you mentioned an update that fixes media playback, but (at least in my case) half the time there's no video being played when I was getting BSODs. It was purely just from alt tabbing between things. Usually between a video game and another application.
In my DREAMS!
Lol almost every night I've had a dream of getting a BSOD.
I find it kind of funny, tbh.
That said, I haven't gotten a single BSOD since running Clockblocker, and it's been.. 5 days? Fingers crossed, I suppose.
So far, I've never had the issue where my GPU is running at max. My fans are all normal, I assume my clock speeds are normal (I haven't actually checked tbh).
Again, could just be entirely coincidence (I've gone over a week without BSODs before, with nothing having changed).
@kemical I know you mentioned an update that fixes media playback, but (at least in my case) half the time there's no video being played when I was getting BSODs. It was purely just from alt tabbing between things. Usually between a video game and another application.
SpaceKitkat
Member
Hmmmmmmmm.
Woke up, turned on my monitors, and it BSOD'd. Weird.
Went 8 days without a BSOD while using Clockblocker.
Woke up, turned on my monitors, and it BSOD'd. Weird.
Went 8 days without a BSOD while using Clockblocker.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EA, {ffff868ad8dc0080, 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+3f )
Followup: MachineOwner
--------- Code:
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULTHi Kitkat,
it does look like the gpu driver is at fault.
Try removing using the DDU and installing the latest driver released last week:
Radeon Software Crimson Edition 16.11.4 Release Notes
cmudaxp.sys Tue Dec 20 03:23:23 2011: ASUS Xonar DG Audio Interface driver. This driver needs updating as it might be indirectly involved with the crash. I did a quick check and there are some Win 10 drivers here:
ASUS Global
AsIO.sys Wed Aug 22 10:54:47 2012: Asus PC Probe Utility. Please remove.
RTKVHD64.sys Thu Apr 24 12:40:09 2014: Realtek High Definition Audio Function Driver please update:
http://www.realtek.com.tw/downloads...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false
Just a thought, do you have the Intel 4000 gpu (onchip) disabled in the bios?
If you haven't already try reseating the gpu.
Hello Space,Hmmmmmmmm.
Woke up, turned on my monitors, and it BSOD'd. Weird.
Went 8 days without a BSOD while using Clockblocker.
i was wondering why it should work for you as in the default setting clock blocker is not enabled without a game running.
Circinae enabled it during idle desktop and you did not.
BR
Sven
Last edited:
Hello All,
AMD suggested to try the newest driver and toggle the Power Efficiency feature:
=== AMD reply start ===
I certainly do understand that you have done pretty much to narrow down the issue, however, could you please give one last try by toggling the power efficiency option provided in the Radeon settings, refer the attached screenshot to know more:
This option would be available with the latest Crimson Edition (Radeon settings) version, I would request you to try this task with the latest 16.11.4 driver.
Radeon Software Crimson Edition 16.11.4 Release Notes
Please perform the above and check the issue status.
=== AMD reply end ===
I didn't test it yet.
BR
Sven
AMD suggested to try the newest driver and toggle the Power Efficiency feature:
=== AMD reply start ===
I certainly do understand that you have done pretty much to narrow down the issue, however, could you please give one last try by toggling the power efficiency option provided in the Radeon settings, refer the attached screenshot to know more:
This option would be available with the latest Crimson Edition (Radeon settings) version, I would request you to try this task with the latest 16.11.4 driver.
Radeon Software Crimson Edition 16.11.4 Release Notes
Please perform the above and check the issue status.
=== AMD reply end ===
I didn't test it yet.
BR
Sven
SpaceKitkat
Member
Yep, I'm still getting BSODs. I haven't updated to that newest version, I'll try it out now though.
Edit: Updated, option isn't there.
:\
http://i.imgur.com/iqlpIeP.png
Edit: Updated, option isn't there.
:\
http://i.imgur.com/iqlpIeP.png
Last edited:
Latest driver is this:
Radeon Software Crimson Edition 16.11.5 Release Notes
Radeon Software Crimson Edition 16.11.5 Release Notes
Spacekitkat is correct, the option isn't there and we knew about this. Sven highlighted that this option wasn't available for older cards when he told us about the registry work around, which was one of the main problems. Of course AMD's own representatives would be less informed than a bunch of random individuals on a Windows 10 forum.
Similar threads
