CorneliousJD

For me the root cause ended up being a dying 5950X - I had it warrantied by AMD and the problem has not resurfaced. While I was searching I did disable c-states on my processor which HELPED reduce the crashing but didn't eliminate it. Separately I ALSO had a kit of bad RAM which corsair RMA'd. The RAM wont play nice still with any XMP/DOCP profile, so it runs at stock speeds sadly but the system is stable and passes 12+ hour AIDA64 stress tests now when before it would fail and/or crash within an hour every time.

Do you mean the exception breakpoint on shutdowns is caused by Nvidia drivers? Do you know which version fixed it? I just installed new drivers today and already saw it again. I just want to review their release notes.

No crashes again overnight, which is good, but I do get things like this every now and then on shutdown, sometime's it's my Jabra Direct, othertimes it's BitWarden. Not sure if it's worth reloading when sfc comes back as clean and DISM health checks come back normal too...

Woke up to NO crash today. Woo! It's too early to tell if it's actually fixed with just one day, but this is the first day w/out a crash overnight in a week or so. Summary of changes. got the latest chipset drivers from AMD instead of Asus (mobo), ran DDU (display driver uninstaller) and pushed a totally fresh copy of nvidia drivers (same version I had tho) disabled C-States in bios. Ran SFC /scannow and it fixed things, although i think this was likely caused by crashes? -- no idea which of these fixed it. or if today was just a lucky day.

I disabled C-States in BIOS (it was set to AUTO before) -- power options I don't have that option for AMD Ryzen, looks like that might be laptop specific for AMD Ryzens. I do know for a fact when these issues started on Win 10 that I had min/max both at 100% for sure.

Thanks for the helpful hints. I downloaded and installed latest chipset drivers you suggested. Fingers crossed for something. In terms of GPU, both of those updates were already installed. Downloaded and tried again for good measure but it did confirm both were already installed. I did also just run the DDU to fully remove nvidia driver and reinstall it fresh for good measure. I did run SFC /scannow and it found (and fixed) corrupt files Re-run of sfc/scannow shows no integrity violations. Rebooting again after this and we will see. Sadly I have to wait overnight to really know what's going on. If you (or anyone else) has any other suggestions to try, I'm all ears, I can throw things at it during the day and hopefully something will stick by nighttime!

I should also note that Sleep mode and Hibernation are both disabled. PC should be on and running 24/7.

I will try to keep this brief, while also giving relevant information... About a week ago my PC started crashing at night, I would wake up and the system would be unresponsive, but powered on, nothing would display on the monitors, nothing woke them up. Only option was to hard reboot. BSODs logged in event viewer at random times over night. Sometimes 20 mins after I left my PC, sometimes 7 or 8 hours later. I was running a 2-year old install of Windows 10 and thought it was time to do a fresh wipe/reload and install Windows 11 anyways. I started with that, did BIOS update to latest version, installed Win 11, got drivers from Asus (mobo) website, and then the crashes continued overnight again. Note that I work from home on my PC so I use this thing for 9+ hours a day, some days 12+ hours - no issues, it ONLY crashes overnight. WEIRD! I did a Windows memory diag and it found problems. Cool, easy enough to troubleshoot and solve that. Removed my DOCP RAM profile, used latest Memtest86+ to test individual DIMMs in different slots, found the bad one and removed it. Re-ran Memtest with 3 of 4 sticks and all came back as passed. Bad RAM stick is awaiting warranty replacement now. I assumed things were solved when I removed that bad RAM stick, but once again this morning I woke up to an unresponsive PC. Now I'm both frustrated and confused. BSOD logged about 30 mins before I got to my PC. There was NOT a BSOD logged the night prior but I had experienced the same unresponsiveness all these previous nights, every single night. I quickly ran Prime95 and Furmark just to make sure it wasn't CPU/GPU related - I didn't run them LONG yet but a quick 15 min test on each shows no issues. TL;DR is Crashes every night when idle, PC powered on still but unresponsive until hard reboot. Fresh reload of Windows, latest drives, BIOS, etc. No Overclock whatsoever, not even DOCP profile on RAM at this point. I assumed it was bad RAM when I found that, but now I have no idea what to check next... Hardware info below, along with whocrashed and bluescreenview results with DPC_WATCHDOG_VIOLATION HARDWARE Windows version: Windows 11, 10.0, version 2009, build: 22621 (x64) Windows dir: C:\Windows Hardware: ASUS, ASUSTeK COMPUTER INC., ROG CROSSHAIR VIII HERO (WI-FI) CPU: GPU: AMD AMD Ryzen 9 5950X 16-Core Processor 8664, level: 25 Nvidia RTX 3080 Founder's Edition Processor count: 32 logical processors, active mask: 4294967295 RAM: 49065.2MB (This is with the 1 stick removed, normally 4x sticks of 16GB) WHOCRASHED On Thu 1/19/2023 7:39:16 AM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\011923-11515-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8031A51C340, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Bug check description: 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). Analysis: 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. BlueScreenView is attached.

I had the same issue and saw this thread linked here: https://answers.microsoft.com/en-us/windows/forum/all/playpause-and-stop-media-keys-not-working/d26b166d-87bd-4d9e-9406-45a59ea1c1cc For me it ended up being Microsoft Teams... we use MS Teams phone system and with Teams opened after making or receiving a call, then the play/pause and stop keys stop working, but last/next track still does. As soon as I close Teams, it's fine again, and stays fine if I reopen teams until I make/get another phonecall. Bummer, as I use Teams M-F 8a-5p and regularly use it for phone calls. Now I'm wondering if there's any fix to prevent Teams from hijacking my buttons.

The Razer Leviathan has 3.5mm (headphone jack), optical, and bluetooth as options for inputs. It comes with an optical cable in the box, so I used that. My motherboard does indeed have optical out. The issue I'm referring to doesn't seem to be 5.1 vs 2.1, it's a digital audio handshake taking 500ms or so. Described here by the last post in this thread: https://forums.tomsguide.com/threads/calling-all-audiophiles-windows-sounds-cut-off-w-hdmi-possible-s-pdif-keep-alive-issue.373126/ The idea they had was using some type of utility to keep that connection alive, and I see various utiliies that can do that, such as the one I linked already, this is another: https://veg.by/en/projects/soundkeeper/ The question I have was "Would something like this be a good option to prevent this issue? Or is there any other (better) options than this?"

I've just transitioned from a 12+ year old 5.1 speaker system using analog connections on my PC to a Razer Leviathan, which comes with an optical cable in the box, so I figured why not, lets hook it up! (I know there's much better options already, I wanted something that wouldn't take up much space on my desk or walls, and had a subwoofer, so I settled for this) I noticed that the sounds are cutting out after a period of silence which makes getting things like email/chat notifications awful, because they're usually missed entirely, or the entire beginning of them is at least cut off completely. I did find that this is pretty common because the motherboard will turn off the optical output during silence and it has to re-establish the signal and wake up the audio hardware again when it reconnects. Is there any way in Windows to disable that feature? I did find this on GitHub https://github.com/handruin/spdif-ka Would something like this be a good option to prevent this issue? Or is there any other (better) options than this? My current understanding is over analog this WOULDN'T happen, but why use analog when digital is an option for me finally? Thanks in advance!

Definately let me know how it goes - if nothing else I'm curious if you have the same resolution and whatnot. Also FWIW I ran memtest overnight on 3200 Mhz and it failed every time (but took forever to fail, had to let it run for hours) have repeated the same test 6 times now on 3133Mhz anda no failures on Memtest.

I had the same thing in Call of Duty Cold War, so instead of disabling DOCP enitrely though I just lowered it to 3133MHz and it's been fine and happily stable since then. Slightly lower timings for staiblity ended up being the solution for me.

Sadly this is not working for me, the 2nd monitor oddly enough just goes to 1920x1080 (not its actual resolution) when I do this setup, and my windows still end up being resized.

interesting. I haven't seen this exact method before, so I will give it a try (probably tomorrow) and report back.