07-21-2013, 05:20 AM
Today I was running hashcat 0.46 via a batch/command file with a list of 52 rules, and it seemed to be a culprit in crashing my 16 GB Windows 7 Home Premium system. I've run that same batch/command file many times, with past versions, against more hashes, with no problems, so it may a quirk with my system at this point in time, and nothing to do with hashcat.
When it got to only line 9 of 52 lines of rules, the system event log reported this:
Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 7/20/2013 6:33:51 PM
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
User: SYSTEM
Description:
Windows successfully diagnosed a low virtual memory condition.
The following programs consumed the most virtual memory:
hashcat-cli64.exe (3780) consumed 40,719,126,528 bytes,
svchost.exe (792) consumed 352,260,096 bytes, and
mysqld.exe (1588) consumed 192,524,288 bytes.
There is a variety of software running, and I have done some hardware changes, recently, too, so this may be a fluke. E.g., my page file may have already been corrupted before this.
But, I want to mention it here, in case anyone else has a similar crash.
When it got to only line 9 of 52 lines of rules, the system event log reported this:
Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 7/20/2013 6:33:51 PM
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
User: SYSTEM
Description:
Windows successfully diagnosed a low virtual memory condition.
The following programs consumed the most virtual memory:
hashcat-cli64.exe (3780) consumed 40,719,126,528 bytes,
svchost.exe (792) consumed 352,260,096 bytes, and
mysqld.exe (1588) consumed 192,524,288 bytes.
There is a variety of software running, and I have done some hardware changes, recently, too, so this may be a fluke. E.g., my page file may have already been corrupted before this.
But, I want to mention it here, in case anyone else has a similar crash.