Hey folks, I'm really struggling with persistent DPC_WATCHDOG_VIOLATION (0x133) BSODs that have been driving me crazy for weeks. Even after a complete OS reinstall, these crashes keep appearing. I'll often get a 1-2 second freeze followed by this weird buzzing noise from my audio, which is just frustrating. Here's a bit about my setup to give you some context:
- OS: Windows 11 Pro (clean install)
- CPU: Intel Core i5-12400
- Motherboard: Gigabyte H610M H DDR4
- RAM: 19.78GB mismatched kit (1x 16GB G.Skill and 1x 4GB no-name)
- GPU: NVIDIA RTX 2060 SUPER
- C: Drive: WD Green 240GB SSD (DRAM-less)
I've tried reinstalling my OS, cleaning up drivers, resetting my BIOS, and running various tweaks to my power settings. While I did notice a bit of improvement after manually updating my SATA drivers, the crashes still happen. Sometimes it's a short freeze, and other times it results in a full BSOD.
The common element in all the crash reports points to ntoskrnl.exe, which usually means there's an underlying issue, and I suspect it's related to my hardware. My SSD shows a few reallocated sectors and a command timeout error, and I'm also worried about my mismatched RAM. Honestly, I'm losing my mind over this. Have I overlooked something obvious? Is it time to replace my hardware or did I miss something in the software/drivers? I'm open to any suggestions, theories, or definitive advice!
3 Answers
It sounds like you’ve done a lot already! Have you looked into your dump files? Those can really give you insight into what's triggering the BSODs. Sometimes tools like BlueScreenView can mislead you. If you see crashes pointing to a specific driver, that could be your answer.
Also, considering your hardware: that mismatched RAM is definitely a possible culprit. It can lead to instability, especially under load. If you can, try running with just one stick at a time to see if that helps.
Props for the detailed post! I’d suggest running some tests on your RAM, like memtest. Sometimes, errors can pop up that wouldn’t necessarily show themselves until the system is under load. With your SSD indicating issues too, you may need to pursue that path as well.
Testing one RAM stick at a time is a great idea, and it’s quick to do. Plus, it eliminates a variable without needing to make massive changes right off the bat.
Thanks, I appreciate the support! It’s been a hell of a journey, and it helps to get opinions from others. I’ll test the RAM and report back.
You definitely should consider replacing that mismatched RAM. Even if it didn’t cause BSODs in the past, after your OS reinstall, it could be that the system is now more sensitive to memory issues. And about your SSD, the command timeout and reallocated sectors are not good signs. I’d say both are worth addressing.
If switching out RAM doesn’t help, maybe try a different SSD as well. It seems like it’s been showing signs of wear.
Thanks for the advice! I was leaning toward the RAM being the issue, especially after the dump file analysis. I’ll look into getting a new SSD if things don’t improve after the RAM swap.
Good call! I hadn’t thought to isolate the RAM sticks like that. I’ll definitely give it a try and see if the issue persists after removing one.