When the computer freezes, please wait and see if a BSOD appears, be sure to mark down any error messages displayed on the blue screen.
If it is not a DPC_WATCHDOG_VIOLATION, then it is not the same issue. How do you know it’s not an issue with the game itself? If it only occurs with that specific game, then it is likely the game is at fault, not necessarily your laptop. The fact that there is nothing in event viewer is strange…
On my system, it will freeze for up to three minutes before actually triggering the BSOD. I assume most users will force restart before that point.
In such a case event viewer will likely show only an unexpected shutdown and nothing else
I waited more than 2 hours. It just freeze. No BSOD. No response.
Yes, it may not be the same root cause as “DPC_WATCHDOG_VIOLATION”.
The game is also not an AAA game or some heavy resource game. I’m also not have the freeze issue in game but in using browser or do other thing. I just found it is the easiest way to reproduce the issue.
The only strange in event viewer is “Display driver amdwddmg stopped responding and has successfully recovered.”. But it does not recovered freeze.
I’ve had this issue since I got this laptop as a part of batch 2. I originally posted on Reddit about this issue, but was not able to solve it.
Since then, I’ve had a (extremely infuriating) conversation with framework support, wiped the laptop and put a fresh install of
Ubuntu 23 (did not crash, but had issues with display strobing white after waking from sleep),
Ubuntu 22 (same issue as Ubuntu 23),
and now back to Windows 11. After my most recent fresh install of Windows 11, it ran fine for the first week, then I had a bluescreen, then it was fine for 2 weeks, and now just tonight I had another DPC_WATCHDOG_VIOLATION bluescreen.
As many of you probably are feeling, I love this laptop, but this process has been incredibly frustrating, and I am ready to throw this thing out the window.
oh this is the same issue I have had, have submitted a ticket with heaps of info, minimal response from Framework.
People getting BSOD in Windows, please run WhoCrashedMe from Resplendence Software - WhoCrashed, automatic crash dump analyzer
I definitely get you here. I use mine for work, I just can’t rely on it.
I’ve got lots of these:
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck.
Mine is never really under any kind of heavy load when it happens, in fact it seems like light workloads are the trigger somehow, maybe coincidence? Anyway, running long sessions of ZAP which is quite CPU intensive, or playing games, it’s fine. It’s only been editing word docs, working in VSCode or browsing my freezes have happened.
There is another window or report somewhere in that program that should point to the driver itself - depending on how the crash was captured.
Conclusion
11 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:08 (h:mm:ss).
Computer says no, unless I part with some dosh! Might be worth it to speed up the support process. Seems like support don’t know what’s going on so it might be useful.
Huh. I may have had full crash dumps on.
Thanks anyway.
I’ve noticed the same thing. I can’t seem to pin down any particular variable on my crashes other than it seems to be low workloads.
Maybe it has something to do with Windows ramping down the CPU to help with battery life, but it gets hung up on something or somehow ramps it too low that it can’t handle it?
The two things I can think of is some sort of power state issue, or maybe it undervolting to an unstable frequency, if that was the case. But then the mobo/bios should have factory configured settings that are set to stable voltages.
I can rule out thermals in my case. I have HWInfo in my taskbar monitoring those, and has never ran hot enough to even reach thermal throttling.
This hitting so many people, even as far back as Batch 3 would make me think either the firmware is buggy or the hardware quality isn’t up to scratch. The only thing unique so far is that everyone with these issues is getting the same BSOD and are all running AMD laptops. It’s not even a bad CPU in terms of performance or battery life, but so many issues will reflect on them. Had I known AMD Framework laptops are assumedly unstable, I would either have gone for an Intel one, or shopped around.
I take this back and apologize for my harsh wording, fw support has been really helpful through my issue which was, infact, my ram…
Interesting. How did you narrow it down to RAM? Did you do the whole running on one stick, swapping slot etc? It’s where I’m at with framework support right now
So I have 2 ddr5 sodimm laptops an xps 15 9520 and the framework. I got the framework to replace the XPS because of random hard freezes. I ran memtest on my xps countless times and it would not report any errors. I didn’t think it was the ram when I put the ram from my xps into my framework. So I was getting similar issues as my xps on my framework but I just choked it up to a new platform. A month goes by and I get in contact with support they say they can’t help because I didn’t have supported ram. I didn’t believe that was the issue because I had ran memtest on both machines at this point. Fast forward to two weeks from then and I receive the 8GB skhynix kit that they list in their supported section. Put it in my laptop 0 crashes ever since. Then I validated that by also putting it in my xps and I ran furmark for 24 hours without a crash before ending it myself(previous record is 2 hours). I then ordered the 32gb kit from framework and I have had 0 issues with both laptops since.
It’s just strange because I feel like there was an example of someone running into this on a prebuilt (which would imply it’s not unsupported RAM). It doesn’t quite make sense to me… Why would funky RAM be causing AMD drivers to hang like that…?
I also think that the fact it occurs more under light load than heavy load suggests “not RAM” - RAM should (generally) be more heavily utilized leading to more faults under heavy load. But it is the opposite, which suggests something about the drivers to me. Also, the fact that it doesnt seem to be occuring on Linux (though I wonder what the closed source amdgpu-pro is like on Linux…).
Another light workload crash, Firefox with the Proxmox webUI and some SSH open in windows terminal.
I had hoped the latest windows update had fixed this : /
I had ordered two sticks of Kingston Fury (2x16GB), and after reading @TossedTripod645 experience, I was hopeful it was a dodgy stick that was causing me issues too.
Turns out the DPC_WATCHDOG_VOOLATION still persists. Just happened watching a youtube video…
This is very very frustrating
Kinda reminds me of that AMD ULPS problem years ago. But as far as I know, ULPS has no effect on iGPUs