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

AMASS Command Causing Bsod #1055

Open
T-Perm777 opened this issue Jan 26, 2025 · 2 comments
Open

AMASS Command Causing Bsod #1055

T-Perm777 opened this issue Jan 26, 2025 · 2 comments

Comments

@T-Perm777
Copy link

T-Perm777 commented Jan 26, 2025

OS: Windows 11 Home
Installed via: GO Install
When I tried to run the command amass enum -d youtube.com, CMD sat there for a second, displaying no output. After a couple seconds, my whole PC froze, and the power button, keyboard inputs, and mouse inputs were not working. After another few seconds, it displayed a BSOD, with the exit code DPC_WATCHDOG_VIOLATION. I can run amass -help just fine.

@ankit-tiwari18
Copy link

So, basically BSOD causes by the reason of hardware failure, insufficient resources, high system load and driver issues from these things it causes. In your case your whole system freeze so its driver issues because its take too many loads and system just freeze because of too many loads and running too many resources, So update your driver for not getting this type of issues.

@T-Perm777
Copy link
Author

So, basically BSOD causes by the reason of hardware failure, insufficient resources, high system load and driver issues from these things it causes. In your case your whole system freeze so its driver issues because its take too many loads and system just freeze because of too many loads and running too many resources, So update your driver for not getting this type of issues.

Which drivers should I update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants