Disabling Hardware Acceleration in applications that use it (browsers, Discord, Spotify, etc.) seems to be working for me currently. This is of course a remedy and not a fix, but worth trying.
Updating to the december AMD drivers did not work. I’m also running the common 2x16GB Crucial kit, CT2K16G56C46S5. This freezing issue appears to exist with other AMD graphics cards based on threads in other forums, so very reasonable to suspect the graphics drivers.
Try rebooting into safe mode and running DDU to uninstall the graphics drivers. Then reinstall directly from AMD. I have been on the November drivers with no issues.
After switching to a supported 8GB kit (The SK Hynix one) it appears to have solved most of my issues as of now. I really dont want to buy back up to 32GB but hey I guess im at least stable for now.
Has it crashed at all since the RAM change, or was it actually fully fixed?
Pinpointing the cause of random crashing is damn near impossible. It takes years! The 820-2850 random crash/recall wasn’t solved for years; and that was only because it has a copy/pasted circuit from a prior 820-2330 board that had a similar issue with an identical circuit that was failing in a way that caused no power, in a much more obvious way. Without that hint, it might have never been solved at all.
This did not fix things for me.
Anyone else having crackling audio issues when waking from sleep/hibernate?
win11 latest amd drivers
the issue stopped completely after the ram had been swapped
That’s promising, how long have you gone w/o an issue?
Hopefully this isn’t the proper solution. So many applications are electron/browser based these days, that you may not even be able to disable it reliably.
Found a solution (I think).
I changed the AMD iGPU plan to match what I set in AMD Adrenalin. For example, when setting the iGPU to Gaming mode in Adrenalin (to get the full 4GB of dedicated iGPU memory), I also went into the BIOS to ensure that the BIOS setting is also set to Gaming.
By default, the BIOS setting is set to Auto and Adrenalin is set to Productivity.
I noticed that when the BIOS is set to Auto but Adrenalin is set to Gaming, I would have the freezes. It is possible that there is some BIOS or Driver error that causes the Automatic preset to switch or error out even though it should be match the Adrenalin setting.
Let me know if this works for anyone else!
I have had an issue where my microphone input (Audio-Technica AT2020USB) sounds terrible- crackling and poor quality after waking from hibernate mode. Unplugging and replugging the microphone USB doesn’t work, tried different ports on my dock, USB hub and directly into the computer via USB-A card, and the I even tried removing the device from device manager and then finding the device again and letting it reinstall drivers (using Microsoft ones that it finds by default). None of this was successful, but if I restart the computer, it starts working normally with good quality again.
Strangely enough, when this happens, I can switch to other audio-input devices which are also using the Microsoft drivers, and they don’t have the same issue. And there’s no warning that it’s sounding crackly on the input because the computer output (and live monitoring mix from the microphone) sounds fine, so I basically have to jump into “Sound Recorder” at the beginning of the day to check that my microphone isn’t crackly, before I get going on virtual meetings where I won’t know unless people complain. So far it’s annoying and I can’t reliably reproduce it, it’s only been 2-3x in the past month.
I don’t know for sure this is fixed, because it’s only been 3 days, but I’m curious how many people who are seeing crashes have the Realtek drivers installed.
I was already on the December AMD drivers which did not fix the crashing.
On the 23rd I installed the Realtek drivers from Framework (previously I was using the Microsoft built-in audio drivers), and then updated to the newest Realtek 9597.1 drivers I could find in the Microsoft Update Catalog (Microsoft Update Catalog).
Since then, I haven’t had a hard freeze. Though I’m sure right after I post this I’ll probably end up having another. 
Edit: Switched the Microsoft Update Catalog / Realtek driver link to one that would let you download it instead of the details page.
Edit 2: yep, too good to be true, just had a crash after 8 days.
I’m on an 8 day uptime streak with AMD 23.12.1 and win11 pro 22631.2861
I want to say crashes stopped after the windows update, but I’m not sure.
I’ll have to check my mic next time that happens. For me it was only the output. IIRC one time it happened I was on a discord call and apparently my mic was fine but the output of everything was bad.
For reference I had the FW drivers installed initially but now my drivers for “speakers (realtek audio)” are using microsoft drivers 10.0.22621.1 dated 5/6/2022
Since doing the AMD drivers update a week ago and Windows update, I feel like my stability took a step back. Other than sleep issues (inability to stay sleeping and dead batteries with high drain overnight while sleeping, necessitating a switch to hibernate only), I had a pretty stable Windows 11 pro on the original drivers. I have since done AMD driver updates twice and in addition to the crackly mic input intermittently, now every time I wake from hibernate this past week, the taskbar doesn’t work (you can see and click on any app/window but it doesn’t switch to the app and bring it forward) until I unplug and replug my Thunderbolt 4 dock (tried both my Dell and Lenovo docks with the same issue). After unplugging and then replugging the taskbar works as expected. But it reduces the joy of one dock cable if I have to unplug and replug Everytime I use the computer.
For what it’s worth, about 6 days now since I’ve had a hard freeze after installing and then updating the Realtek driver. Again, not sure it’s definitely a fix but so far so good here.
Edit: yep, too good to be true, just had a crash after 8 days.
I had no issues previously but somehow over the past week or so I started getting crackling / popping audio seemingly at random times, but definitely noticeable when you wake from sleep or hibernate. Tried various realtek drivers and it doesn’t seem to make a difference for me at all.
Just recovered from another BSOD. Another DPC Watchdog Violation error. This one actually pointed to another file alongside NTOSKRNEL. AMDKMDAG.SYS.
Running the latest Adrenalin drivers.
Windbg calls out the following
SYMBOL_NAME: dxgkrnl!DXGADAPTER::SetPowerComponentIdleCBWorker+22a
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.22621.1254
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 22a
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DXGADAPTER::SetPowerComponentIdleCBWorker
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {25ca888a-406c-e8a0-26b1-b2b0fa0a1558}
I’m in the same situation and have those two files responsible for my BSODs. Out of curiosity, do you have an HDMI expansion card inserted?
Nah. Have two USB-Cs in the top two slots (1 and 3), a USB-A in the bottom-left (2), and a DisplayPort one in bottom-right (4).
I just DDU’d my GPU drivers, gonna run without them for a few days and see how that goes actually. If it bluescreens again, then I can see it possible to rule out AMD drivers at fault (could be power management perhaps? another driver at fault or some incompatibility not picked up, if not potentially hardware related). If it doesn’t, then I can safely say it’s AMD driver/firmware related.
UPDATE: Disregard part of that. Ended up installing the graphics drivers (Framework ones again) since I had issues with the display not turning on when waking from sleep and being unable to get an output working.
Have just opened a support email with Framework themselves too so will update if anything comes out of that.
Ah k, so you have a DP expansion card in the same port as my HDMI card. I am doing an experiment to see if the BSODs stop if there are no display expansion cards inserted. So far so good but it has only been 1.5 days.
This is the last act of desperation I can think of to try. I recall in some other thread someone mentioned support said bad expansion cards can cause this sort of BSOD.