AMASS Command Causing Bsod

[T-Perm777]

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]

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]

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?

[xGodlike0]

I am having the same problem both on Kali Linux VM (8 GBs RAM, 8 Processors) and on Windows 10 Pro 22H2 Build 19045.5737 (Intel i7 X-series CPU x64-based processor), 32.0 GBs RAM.

[mzpqnxow]

I am having the same problem both on Kali Linux VM (8 GBs RAM, 8 Processors) and on Windows 10 Pro 22H2 Build 19045.5737 (Intel i7 X-series CPU x64-based processor), 32.0 GBs RAM.

Blue screen of death on Kali? 😝

… perhaps you mean OOM is killing processes because you don’t have sufficient RAM? Or you have slow disks and your system starts swapping after RAM is eaten up, and the system appears to be hung? (In theory, it will eventually become responsive, it just might take a very, very long time, as your system is using the disk for RAM)

I think some memory profiling information from a run where the issues appear would be helpful if someone has time to look at it. Otherwise there’s not enough information here for anyone to help you.

Buy more RAM? Or maybe trim down the inputs and run in batches?

[xGodlike0]

I am having the same problem both on Kali Linux VM (8 GBs RAM, 8 Processors) and on Windows 10 Pro 22H2 Build 19045.5737 (Intel i7 X-series CPU x64-based processor), 32.0 GBs RAM.

Blue screen of death on Kali? 😝

… perhaps you mean OOM is killing processes because you don’t have sufficient RAM? Or you have slow disks and your system starts swapping after RAM is eaten up, and the system appears to be hung? (In theory, it will eventually become responsive, it just might take a very, very long time, as your system is using the disk for RAM)

I think some memory profiling information from a run where the issues appear would be helpful if someone has time to look at it. Otherwise there’s not enough information here for anyone to help you.

Buy more RAM? Or maybe trim down the inputs and run in batches?

I have 32 GBs of RAM (4.000 MHz), a Samsung 980 Pro and an Intel X series CPU ...

I tried it on a Kali VM with 16 GBs of RAM assigned and 8 processors. I tried it on the main system as well using Docker. In both cases I get BSOD. So it doesn't matter if I run it on the Kali VM or using Docker, it makes the whole system crash.

[mzpqnxow]

I am having the same problem both on Kali Linux VM (8 GBs RAM, 8 Processors) and on Windows 10 Pro 22H2 Build 19045.5737 (Intel i7 X-series CPU x64-based processor), 32.0 GBs RAM.

Blue screen of death on Kali? 😝

… perhaps you mean OOM is killing processes because you don’t have sufficient RAM? Or you have slow disks and your system starts swapping after RAM is eaten up, and the system appears to be hung? (In theory, it will eventually become responsive, it just might take a very, very long time, as your system is using the disk for RAM)

I think some memory profiling information from a run where the issues appear would be helpful if someone has time to look at it. Otherwise there’s not enough information here for anyone to help you.

Buy more RAM? Or maybe trim down the inputs and run in batches?

I have 32 GBs of RAM (4.000 MHz), a Samsung 980 Pro and an Intel X series CPU ...

I tried it on a Kali VM with 16 GBs of RAM assigned and 8 processors. I tried it on the main system as well using Docker. In both cases I get BSOD. So it doesn't matter if I run it on the Kali VM or using Docker, it makes the whole system crash.

Ah I missed that it was a Windows host for the VM

I can't diagnose the issue but I can say it's not an issue specific to Amass, rather it's induced by the pattern of behavior Amass has. You should be able to reproduce it by running any application that is heavy on network and/or disk i/o (theoretically, I wouldn't necessarily spend time trying to do this)

Driver error or hardware error on the Windows host or any issue with the virtualization software. Send the crashsdump to MSFT, let them suss it out. It's an availability issue. A VM shouldn't be able to panic the host

That error seems to be the system freaking out because it's not handling all the interrupts well. You may be able to disable that watchdog or tune it to allow the interrupt handler to take longer but your system will potentially be locked up anyway

You might look into whether your NIC supports MSI-X. And see if using a different NIC "resolves" the issue