Skip to content
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

Open
hackhubafrica opened this issue Oct 28, 2024 · 2 comments
Open

DPC WATCHDOG VIOLATION on Windows #1723

hackhubafrica opened this issue Oct 28, 2024 · 2 comments
Labels
bug TYPE: a report on something that isn't working

Comments

@hackhubafrica
Copy link

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!

@hackhubafrica hackhubafrica added the bug TYPE: a report on something that isn't working label Oct 28, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@Raphty
Copy link
Member

Raphty commented Oct 28, 2024

You can try the current beta. we reworked the kext.

You mention "high resource usage" what are you doing before the error happens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug TYPE: a report on something that isn't working
Projects
None yet
Development

No branches or pull requests

2 participants