I have a rig with 3 x 1080 and
when i start hashcat... few minutes later come this message :
Driver temperature threshold met on GPU #4. Expect reduced performance.
windows shut down or restart
what is the problem ?
I use a asus mainbaord bequiet 600 & 500 watt, 4 gb ram
3 x 1080 geforce , driver sucessfull installed...
thank you
It's exactly what it states. GPU on slot 4 is reaching a very hot temperature and is reducing its performance due to it reaching the default 90ºC Temp.
You probably have non-reference design cards stacked ontop of each other with the backplates still on causing it to overheat. You need better cooling solutions or space the cards out more.
the distance per card is 15 cm and in a cool room, that should not actually happen.
ist it possoble to reduce the attitude that it does not overheat?
Something with your cooling/airflow is bad.
Run it with a lower profile such as -w 1 or -w 2 and fix your fan curve to have them run at 100%
ok profile is -w 3 i try -w2 with 100% fan and report tomorrow
so ive try again here is the log, after 30 minutes, follow error comes :
[s]tatus [p]ause [b]ypass [c]heckpoint [q]uit =>
nvmlDeviceGetTemperature(): Unknown Error
nvmlDeviceGetTemperature(): Unknown Error
clGetEventInfo(): CL_OUT_OF_RESOURCES
clGetEventInfo(): CL_OUT_OF_RESOURCES RCES
clEnqueueReadBuffer(): CL_DEVICE_NOT_FOUND
nvmlDeviceGetUtilizationRates(): Unknown Error
cvmlDeviceGetUtilizationRates(
nvmlDeviceGetUtilizationRates(): Unknown Error
nvmlDeviceGetFanSpeed(): Unknown Error
nvmlDeviceGetClockInfo(): Unknown Error
nvmlDeviceGetClockInfo(): Unknown Error
nvmlDeviceGetCurrPcieLinkWidth(): Unknown Error
nvmlDeviceGetFanSpeed(): Unknown Error
nvmlDeviceGetClockInfo(): Unknown Error
nvmlDeviceGetClockInfo(): Unknown Error
nvmlDeviceGetCurrPcieLinkWidth(): Unknown Error
Session..........: hashcat
Status...........: Error
Hash.Type........: DES (PT = $salt, key = $pass
.....
That looks like a card stopped functioning during the cracking session.
i think i try ubuntu, hope that is an windows problem or what is your opinion?
thank you....
Looks rather like a hardware error of some kind.