01-30-2013, 11:55 PM
01-31-2013, 12:02 AM
(01-30-2013, 11:55 PM)undeath Wrote: [ -> ]Then this might be a heat problem. Try running both cards with an open case and maybe put another fan there.
It's allready a open case . I can touch the card with my hand, and it's not that hot!
It's strange that freeze after 3-5sec. I think the card can't get that high tempeture in 3-5 sec.... These cards with 3 cooler on
each...no way to get overheat in that short time...
01-31-2013, 12:05 AM
(01-31-2013, 12:02 AM)hoze Wrote: [ -> ](01-30-2013, 11:55 PM)undeath Wrote: [ -> ]Then this might be a heat problem. Try running both cards with an open case and maybe put another fan there.
It's allready a open case . I can touch the card with my hand, and it's not that hot!
It's strange that freeze after 3-5sec. I think the card can't get that high tempeture in 3-5 sec.... These cards with 3 cooler on
each...no way to get overheat in that short time...
...does somebody know what is the symptoms of low PSU maybe ?
01-31-2013, 05:54 AM
Well, if I understood correctly one of your post, your 2 GPUs were on 2 separate PSU so if they run fine alone, then it should not make a difference if they run together (PSU wise). Are they both directly on the motherboard or you are using PCI-E extenders? Make sure that they are well seated in their slots. I can't think of anything else right now. I don't know if it does still make a difference but if you have crossfire, disable it.
01-31-2013, 11:36 AM
(01-31-2013, 05:54 AM)mastercracker Wrote: [ -> ]Well, if I understood correctly one of your post, your 2 GPUs were on 2 separate PSU so if they run fine alone, then it should not make a difference if they run together (PSU wise). Are they both directly on the motherboard or you are using PCI-E extenders? Make sure that they are well seated in their slots. I can't think of anything else right now. I don't know if it does still make a difference but if you have crossfire, disable it.
Yes, separate PSU and directly on MB,without extenders and without crossfire!
01-31-2013, 12:06 PM
if it's happening on both windows and linux then you know it's not a software or driver issue. if each card works fine individually then you know it's something like your motherboard, bios settings, psu, etc.
01-31-2013, 01:03 PM
(01-31-2013, 12:06 PM)epixoip Wrote: [ -> ]if it's happening on both windows and linux then you know it's not a software or driver issue. if each card works fine individually then you know it's something like your motherboard, bios settings, psu, etc.
I think the PSU is the problem. I will replace it today and post the result...
01-31-2013, 06:45 PM
You can also use the -d 1 and -d 2 to check cards individually and maybe see which of the cards create the problem, or both, who knows...
01-31-2013, 08:18 PM
(01-31-2013, 06:45 PM)atom Wrote: [ -> ]You can also use the -d 1 and -d 2 to check cards individually and maybe see which of the cards create the problem, or both, who knows...
OK, I will try that now. In meantime I change one of the PSU and now I can run in full speed both GPU,but after 3-5min the system is freeze. Before with old PSU after few second the system freeze,so I think the PSU is the trouble maker
Here is log from both GPU (running stable 3-5min)
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 16 loops, 160 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Tahiti, 2048MB, 1100Mhz, 32MCU
Device #2: Tahiti, 2048MB, 1100Mhz, 32MCU
Device #1: Kernel g:\wpa2\oclHashcat-plus-0.12/kernels/4098/m2500.Tahiti_938.2_CAL 1.4.1741 (VM).kernel (1399164 bytes)
Device #2: Kernel g:\wpa2\oclHashcat-plus-0.12/kernels/4098/m2500.Tahiti_938.2_CAL 1.4.1741 (VM).kernel (1399164 bytes)
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: oclHashcat-plus
Status.........: Running
Input.Mode.....: Mask (?l?l?l?l?l?l?l?l)
Hash.Target....: xxxxx
Hash.Type......: WPA/WPA2
Time.Started...: Sun Dec 02 18:33:31 2012 (1 min, 12 secs)
Time.Estimated.: Mon Dec 10 15:30:29 2012 (7 days, 20 hours)
Speed.GPU.#1...: 157.4k/s
Speed.GPU.#2...: 157.4k/s
Speed.GPU.#*...: 314.8k/s
Recovered......: 0/1 Digests, 0/1 Salts
Progress.......: 22282240/208827064576 (0.01%)
Rejected.......: 0/22282240 (0.00%)
HWMon.GPU.#1...: 99% Util, 68c Temp, 84% Fan
HWMon.GPU.#2...: 99% Util, 68c Temp, 84% Fan
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
01-31-2013, 08:54 PM
(01-31-2013, 06:45 PM)atom Wrote: [ -> ]You can also use the -d 1 and -d 2 to check cards individually and maybe see which of the cards create the problem, or both, who knows...
I test both card separately with -d 1 and -d 2 option and work fine. Here is the log for -d 1:
oclHashcat-plus v0.12 by atom starting...
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 16 loops, 160 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Tahiti, 2048MB, 1100Mhz, 32MCU
Device #2: skipped by user
Device #1: Kernel g:\wpa2\oclHashcat-plus-0.12/kernels/4098/m2500.Tahiti_938.2_CAL 1.4.1741 (VM).kernel (1399164 bytes)
Session.Name...: oclHashcat-plus
Status.........: Running
Input.Mode.....: Mask (?l?l?l?l?l?l?l?l)
Hash.Target....: xxxxx
Hash.Type......: WPA/WPA2
Time.Started...: Sun Dec 02 19:06:11 2012 (20 mins, 38 secs)
Time.Estimated.: Sat Feb 16 11:46:23 2013 (15 days, 16 hours)
Speed.GPU.#1...: 157.4k/s
Recovered......: 0/1 Digests, 0/1 Salts
Progress.......: 192020480/208827064576 (0.09%)
Rejected.......: 0/192020480 (0.00%)
HWMon.GPU.#1...: 99% Util, 79c Temp, 100% Fan
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
log for -d 2:
oclHashcat-plus v0.12 by atom starting...
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 16 loops, 160 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: skipped by user
Device #2: Tahiti, 2048MB, 1100Mhz, 32MCU
Device #1: Kernel g:\wpa2\oclHashcat-plus-0.12/kernels/4098/m2500.Tahiti_938.2_CAL 1.4.1741 (VM).kernel (1399164 bytes)
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: oclHashcat-plus
Status.........: Running
Input.Mode.....: Mask (?l?l?l?l?l?l?l?l)
Hash.Target....: xxxxx
Hash.Type......: WPA/WPA2
Time.Started...: Thu Jan 31 19:44:51 2013 (1 min, 40 secs)
Time.Estimated.: Sat Feb 16 07:35:26 2013 (15 days, 11 hours)
Speed.GPU.#1...: 157.5k/s
Recovered......: 0/1 Digests, 0/1 Salts
Progress.......: 15728640/208827064576 (0.01%)
Rejected.......: 0/15728640 (0.00%)
HWMon.GPU.#1...: 64% Util, 31c Temp, 50% Fan
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
...just one thing I don't understand. With " -d 2" every time i press S for status I got different util value.Sometimes 43%,sometimes 84%,then again 50% ,tempeture only 31c, but the "Speed.GPU" stay allmost at 157k all the time and the remaining time is shown correctly.