[SOLVED] Freezing / BSOD while idle - DPC WATCHDOG VIOLATION bugcheck 133 - FIX: I disabled C states in the BIOS

If it allows you do that then give it a try. Usually, you're required to have an even number of cores with Ryzen but maybe it's different with Zen 3 and/or two CCD CPUs.
 
Ran for the past day or so on these settings, confirmed from task manager I was on 16 logical cores, was not crashing yesterday but it froze overnight.

1724548578570.png
 
Please rerun the "Sysnative BSOD Dump + File Collection App" and link the resulting new zip file.
 
So, it looks like a minidump was generated for a crash today. Did it also create a new C:\Windows\MEMORY.DMP file? If so, please make that available for comparison.
 
The latest memory.dmp shows a thread owned by the Discord.exe process calling into a system service. There's an I/O request packet (IRP) pending which looks to be associated with the Network Store Interface Proxy Service (nsiproxy.sys). That was true in the first memory.dmp file provided, too. The callstack looks to be getting information about the process and then gets stuck in the function nt!KeFlushProcessWriteBuffers for two minutes - the watchdog timeout period. I'm pretty sure that function would raise the IRQL to DISPATCH_LEVEL or above while doing what the function name would suggest it's doing. From what I can tell, it synchronizes write buffers shared across other threads on other cores but is getting stuck. This all looks to be while running Microsoft code.

Disabling cores doesn't always work, if the problem is what I think it is. The next thing I'd want to try is disabling C-states in the BIOS, if possible. I'm assuming it's still not crashing while playing a video or game. The idea being that the CPU is having trouble transitioning to and from lower power states while idle which I've seen be a problem in quite a few modern CPUs. You can also enable all of the cores as that didn't seem to make much difference.
 
I think that's the right setting. Was it already set to Disabled or you've done it now?
 
3 days, no freezes or crashes, screens have gone to sleep several times, which it would usually have not come back from.

Is there any potential side effects of disabling the C-state? aside from probably a slightly higher power usage, my PC is pretty well always on.
 
As you already noted, it will likely use more power but I'm not aware of any issues caused by disabling C-states. I'd be tempted to try and get an RMA accepted from AMD if it's still under warranty. I haven't seen many Vermeer CPUs (maybe 4 or 5) have problems while idle but I've seen quite a few Matisse CPUs (dozens) turn out to be faulty. AMD have always accepted an RMA and replaced the CPUs, after which the crashes stopped. Those were when disabling C-states didn't stop the crashes, though, so I don't know what to expect in your case. Nobody I was helping bothered to try an RMA after disabling C-states prevented the crashes - you would be the first.
 
I think the factory warranty was 3 years which has ended and since I've effectively solved the issue I'm fine with it.

Thank you for all the help, really appreciate it. Going to make a small donation to the site.
 
Thank you for the update. I'm glad the crashes seem to have stopped. I'd consider disabling C-states more of a workaround rather than a fix but it's hard to argue with a good result. Please do let us know if the crashes return. Good luck!
 
Back
Top