hashcat Forum

I recently switched from Windows to Ubuntu Server and have ran in to a bit of an issue, after a number of hours it seems one of my r9 290x's just stops responding. I'm trying to figure out if this is a card issue or something I'm doing, I don't recall ever having this issue in Windows.

System details: regular tower case, Intel 4770k, MSI z87 motherboard, 3x r9 290x reference, 1x FirePro v4900 (needed vga so I added this I had laying around).

Basic NTLM brute force using -w 3 and --powertune-enable. I had paused it on this particular scan for a while which is why the time started is so long.


Once it does this and the card hash/s goes to 0, I cannot quit, pressing q just hangs. kill -9 pid doesn't seem to do anything except the process goes defunct, have to reboot to do anything.

Stock clocks, nothing else changed, any suggestions? I may stress test that card individually to see if anything happens with it.

If you're getting an ASIC hang during NTLM brute force, then it is very likely a power issue. How big is your PSU?

Corsair HX1050, definitely starting to push it...

It might just come down to the powertune settings pushing it over the edge, I'll report back with a larger PSU once I get things swapped around. Thanks!

Those 290Xs will draw around 320W on NTLM brute force, so your GPUs alone are likely pulling around 960W. Doesn't leave much power available for everything else in your system. Plus that's a pretty low-end power supply, so I'm not sure how well it handles cards that violate the PCI-e spec (as most high-end AMD GPUs do.) It may not like pushing more amps than its rated for.

I would start by removing the --powertune-enable switch from your command line, and use od6config to underclock the GPUs and de-tune PowerTune.


That should help until you can buy a proper PSU for your rig.

The performance is ways to slow for NTLM. I'd say wrong driver / bad driver installation. See here for solution:

https://hashcat.net/wiki/doku.php?id=fre...hould_i_do

I don't think so, I just rebuilt the OS less than a week ago and used the same driver reference in the wiki.

I had it crash twice doing a benchmark, so I think power might be it, just interesting I never this this problem with this setup for a couple weeks in Windows (before this I had 280x cards which were a little less power hungry, but had awful cooling).

I think it's probably because there are still 100+ hashes pending on that run that's slowing it down for hashrate, benchmark seems to be where it should be.

The speeds look fine to me, atom. Both the single hash speeds and the multi-hash speeds. Are you perhaps looking at the speed of the Firepro card?

I was just expecting a -b benchmark. Speeds are fine for multi-hash.

Well, my new PSU came... Just got it in. EVGA 1300W. if I was on the edge before, an extra 250W should be sufficient. This thing supports 110A on the 12v rail.

Once installed this morning every time I kicked off a test it's crashed and hung the system. Either on the "Finding weak hashes" of a regular scan or when kicking off the benchmark.

Narrowed it down to the same GPU #1 I was having issues with before. If I run without it, it works. So I think I'm going to try to RMA card #1... I'm leaning toward card issue over power issue still, but at this point I don't think I can prove it. (Or one could have caused the other I guess).

Well, if you can run -d 2,3 without problems and have trouble -d 1, I think that you have proven what the problem is. You can always try to swap the faulty card with another and see if it still causes problem but chances are that it will unless it was used with a PCI-e extender (that could be faulty too).