-
-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DPC WATCHDOG VIOLATION on Windows #1723
Comments
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
You can try the current beta. we reworked the kext. You mention "high resource usage" what are you doing before the error happens? |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
I am experiencing a DPC WATCHDOG VIOLATION error when running Portmaster on my Windows system. The software works fine on Unix systems, but it consistently causes a BSOD (Blue Screen of Death) on Windows 10.
Portmaster should run on Windows without causing any BSODs or interruptions, similar to its performance on Unix systems. Each time I run Portmaster on Windows, I encounter a DPC WATCHDOG VIOLATION BSOD, which disrupts my system.
I would appreciate any guidance or solutions you can provide regarding this issue, as it significantly affects my experience with Portmaster on Windows. Thank you for your attention to this matter!
I have checked the known issues page and found no existing reports of this specific problem. The error seems related to high resource usage or conflicts with network drivers, as it only happens on Windows and not Unix systems. Any guidance on resolving this issue would be greatly appreciated!
The text was updated successfully, but these errors were encountered: