After upgrading to v0.08 and removing the crossfire adapter (2xHD5970 cards) my system screen begin to be filled with garbage. Does someone have an idea how to correct the problem? If I want to make a screen-shoot nothing strange on the saved image, I had to take a photo from the screen. If I move an open window the garbage disappear behind the window. The machine working well but a little instability appeared. I can not put back the crossfire adapter because changing the fans to arctic coolers. Thanks for the ideas!
hashcat Forum
›
Deprecated; Ancient Versions
›
Very old oclHashcat-lite Support
strange screen error
strange screen error
|
strange screen error
|
Either heat, or an issue with the card. What you are seeing is called artifacting. This is common with overclocking and has to do with errors on the shaders. Try running something like FurMark and see if you can replicate something similar. It may not look the same everytime, but unless you underclock you will continue to see this.
It could also be your computer hating you for running SL3. 
02-01-2012, 09:40 PM
Its a driver thing. You must lower -n and/or --gpu-loops to avoid this. However, speed will drop.
My Pc:
win7 64bit HD 6990 #2 cards ---------------------------------------------------- before: hashcatlite 0.6 catalyst control 11.8 Hash.Type......: SL3 Time.Left.......: 1 day 10 hours Speed GPU.#1: 1700 - 1800 Speed GPU.#2: 1700 - 1800 Speed GPU.#3: 1700 - 1800 Speed GPU.#4: 1700 - 1800 Speed GPU.#*: 7200 - 7400 HWMon GPU.#1: 97% - 99% GPU 55c Temp HWMon GPU.#2: 97% - 99% GPU 55c Temp HWMon GPU.#3: 97% - 99% GPU 55c Temp HWMon GPU.#4: 97% - 99% GPU 55c Temp now: hashcatlite 0.8 catalyst control 11.12 pls help me???
??????
HWMon GPU.#1: 50% GPU 55c Temp HWMon GPU.#2: 50% GPU 55c Temp HWMon GPU.#3: 50% GPU 55c Temp HWMon GPU.#4: 50% GPU 55c Temp how to speed up and GPU % HWMon GPU.#1: 97% - 99% GPU 55c Temp HWMon GPU.#2: 97% - 99% GPU 55c Temp HWMon GPU.#3: 97% - 99% GPU 55c Temp HWMon GPU.#4: 97% - 99% GPU 55c Temp
02-02-2012, 07:32 PM
I resolved my problem: the solution was the reducing of the memory clock. Thanks for the reply!
|
|
« Next Oldest | Next Newest »
|