Question Watchdog Violation BSOD only during gaming? - Most recent mini-dump attached.
Question Watchdog Violation BSOD only during gaming? - Most recent mini-dump attached.
I would still switch it on and off to remove any caches it might have.
It might be possible, but I haven't verified it. Both the 0x9F and the 0x133 bugchecks are linked to network issues, and you now have the newest driver for that adapter. All that remains is the LAN adapter itself. You might want to check your motherboard driver site and install the LAN adapter driver from there. Sometimes standard drivers lack the specific customization that the motherboard driver provides.
Aright, sounds good. So the current plan is that I reset the router to factory settings and rebooted the router and modem by unplugging.
I'll leave my computer on while I'm at work.
If it ends up crashing again, I'll buy a USB Wi-Fi dongle and see if disabling the LAN Adapter makes the crashes stop.
If it does crash again and going on Wi-Fi fixes it, really the only solution will be to get a new LAN adapter for my spare PCI slot or a new motherboard, I'm assuming?
Well, I've come back.
Since our last conversation, I purchased a USB Wi-Fi Adapter. When using that adapter with the LAN driver turned off, I experienced only one crash, which eventually resolved to a NVIDIA driver issue. Over the following weeks, apart from the USB adapter's problems with intermittent disconnections, I didn't encounter any crashes linked to these network drivers.
Today, I acquired a new Network Card. After launching WoW, within an hour I encountered another crash, this time returning to the tcpip issue from before.
https://drive.google.com/file/d/1eUbzY3C...drive_link
I've shared the file here for your verification (if you're still interested), but I've since installed the program myself to examine the logs. The results match the previous crashes quite closely. The card I bought features an RTL8125B chip and operates via PCI.
My next step is to completely remove the old device and driver from Device Manager and observe the outcome. I believe this will help determine what's causing the issue. At this stage, I have both the USB adapter and the new PCI adapter ready.
If a crash occurs again, and you have no other suggestions, I expect the next action will be to reinstall Windows 11. This machine was originally a Windows 10 system that I upgraded to Windows 11 about six or seven months ago, so perhaps the incompatibility is now surfacing.
This situation is quite intriguing!
The dump you shared points to a DPC_WATCHDOG_VIOLATION, indicating the device's back-end processing halted excessively. According to the analysis, the operation is a networking task currently underway.
However, a significant detail emerges from the complete call stack: the driver in question is wfpent8.sys, and it's being invoked repeatedly within this segment.
Hey, just wanted to let you know.
It turned out the problem was actually a simple bug in Windows.
I started by updating from version 10 to 11, and it mostly worked, but I felt a strange connection between the driver issue and that update. I waited as long as I could, but after a fresh Windows 11 install it has been smooth for weeks now.
Thanks a lot for all your support through this—you really helped me learn how to troubleshoot things in the future.
It wasn't a flaw in Windows.
Upgrading from Windows 10 to 11 often brings problems when drivers for rare or unsupported hardware are still present.
A cleaner installation of Windows 11 from the beginning is usually better.
Although it requires more effort, a stable system right away makes the process quicker and easier overall.