Posts: 134
Threads: 27
Joined: May 2010
07-08-2010, 02:07 AM
(This post was last modified: 07-15-2010, 10:49 PM by proinside.)
Win7 x64 SDk 2.1 Catalyst 10.2 (cause 10.6 is giving lots of problems
with other software), and do not know if it has something to do with
10.2 Catalyst, or anything else. Here is the message:
Problem signature:
Problem Event Name: APPCRASH
Application Name: oclHashcat.exe
Application Version: 0.0.0.0
Application Timestamp: 4c21f302
Fault Module Name: aticaldd.dll
Fault Module Version: 6.14.10.553
Fault Module Timestamp: 4b68f2b5
Exception Code: c0000005
Exception Offset: 00114a6a
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2070
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Posts: 5,185
Threads: 230
Joined: Apr 2010
oclHashcat requires at least Catalyst v10.4 but if you have multi-gpu i would recommend v10.5+
Posts: 134
Threads: 27
Joined: May 2010
07-15-2010, 09:24 PM
(This post was last modified: 07-15-2010, 09:27 PM by proinside.)
XP Pro SP3 SDk 2.1 Catalyst 10.5
Can not make it to work correctly, or at least doesn't look well.
What can be wrong/missing ? Thanks.
Command line used: oclHashcat.exe example.hash -1 ?l?u?d ?l?l?l?l ?l?l?1?1
oclHashcat v0.22 starting...
Digests: 4 entries, 4 unique
Platforms: 1
Platform #1: Advanced Micro Devices, Inc., OpenCL 1.0 ATI-Stream-v2.1 (145) (2 matched)
Device #1: Cypress, 256MB, 850Mhz, 20MCU
Device #1: Kernel kernels/oclHashcat_m0000_4_4098_AMO.kernel (399221 bytes)
Device #2: Cypress, 256MB, 850Mhz, 20MCU
Device #2: Kernel kernels/oclHashcat_m0000_4_4098_AMO.kernel (399221 bytes)
[s]tatus [p]ause [r]esume [h]elp [q]uit =>
9f2adb8b388ecffe4265a4b1dc47b507:¿ûò½óÿòýw|óý¿~ÿ
[s]tatus [p]ause [r]esume [h]elp [q]uit =>
ec37cc43d400ee9a3642efedf94a9da0:óÃÂ÷ÿâ€â€oþ·óîûÿ_ýú
[s]tatus [p]ause [r]esume [h]elp [q]uit =>
2456a79ad2d55c792d60a0f0e13bd1ca:_ÿõ÷~ñëûïûÿÿ~ß
[s]tatus [p]ause [r]esume [h]elp [q]uit =>
0bb1306f696aa2dd3243c5d03ff63eee:ßÿòŸqÿÿßøïóïÿïý
[s]tatus [p]ause [r]esume [h]elp [q]uit =>
Threads...: 2
Mode.Left.: Mask '?l?l?l?l' (456976)
Mode.Right: Mask '?l?l?1?1' (2598544)
Speed.GPU1: 797.3M/s (running)
Speed.GPU2: 99.2M/s (running)
Speed.GPU*: 896.5M/s
Recovered.: 4/4 Digests, 1/1 Salts
Progress..: 458752000/1187472242944 (0.04%)
Running...: 0 secs
Estimated.: 22 mins, 4 secs
Started: Thu Jul 15 20:14:30 2010
Stopped: Thu Jul 15 20:14:32 2010
Posts: 134
Threads: 27
Joined: May 2010
Answering myself: by disabling crossfire, it works but only for one card.
Remains the question: what were ATI thinking about with these drivers updates ?
Posts: 601
Threads: 18
Joined: Apr 2010
They were bribed by Nvidia to code shitty drivers, perhaps?
Posts: 5,185
Threads: 230
Joined: Apr 2010
how did you manage to disabled crossfire? this is the well known and often discussed HD5970 (cypress) crossfirex ATI driver problem. i have exactly the same error on my card and there is currently no way to workaround this problem except using -d 1. but this limits the usage to first gpu (well i think it is the "virtual" crossfirex'd gpu) but that also means we can not gain the full 5970 performance. but it should solve the random output of cracked hashes.
we have to wait for ATI updating their drivers. till that, use -d 1 and dont forget -n 80 for max. performance
Posts: 134
Threads: 27
Joined: May 2010
07-16-2010, 05:32 PM
(This post was last modified: 07-16-2010, 05:54 PM by proinside.)
(07-16-2010, 01:52 PM)atom Wrote: how did you manage to disabled crossfire?
By disable crossfire in Catalyst Control Center.
(07-16-2010, 01:52 PM)atom Wrote: this is the well known and often discussed HD5970 (cypress) crossfirex ATI driver problem. i have exactly the same error on my card and there is currently no way to workaround this problem except using -d 1. but this limits the usage to first gpu (well i think it is the "virtual" crossfirex'd gpu) but that also means we can not gain the full 5970 performance. but it should solve the random output of cracked hashes.
I have 2x5870 crossfired, but the problem is the same, I guess. Thus, only
one card works in these conditions!
(07-16-2010, 01:52 PM)atom Wrote: we have to wait for ATI updating their drivers. till that, use -d 1 and dont forget -n 80 for max. performance
Yes, -n 80 gives a much better performance indeed. However, I still
find it slower than ighashgpu, above 3200 for ighashgpu on single hash,
below 1500 for oclhashcat. Oclhashcat looks way much better because
of the development you have been done, are keep doing, while ighashgpu
just stoped the development, which is a pitty.
About multihash performance they are very similar in performance.
Posts: 134
Threads: 27
Joined: May 2010
(07-16-2010, 06:16 PM)budden Wrote: 2*5870 work both perfect. so no - you don't have any problem.
That sounds good.
Did you make oclhashcat 0.22 run with 2x5870 crossfire enable ?
With which catalyst version ? And, would help also, can you specify
the (full) command line do you use to make it run ?
Posts: 5,185
Threads: 230
Joined: Apr 2010
you need to have crossfirex disabled. oh and there is another thing. on ATI, you need to have the cards connected to monitor.
