Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Sick rig

    Mining
    6
    12
    3705
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DeadZebra Regular Member last edited by

      Hey guys :) I got a new 7950 WF3 card yesterday and added it to one of my rigs. Anyway it runs for a while then cgminer either reports it as being sick or the computer freezes. Drivers maybe? I have installed the same drivers on a rig with the exact same hardware specs.

      1 Reply Last reply Reply Quote 0
      • A
        ASDASDASD last edited by

        What do you mean by reports it as sick? HW errors?

        I have a 7950 running at max and it is very finicky. For any number of reasons it will completely freeze the system up & require a full reboot. Sometimes on start when I leave the I 20 it kills the driver and then requires a reboot. Other times using the same config settings can give it a rate of 30 kh/s or 500 kh/s, but once it gets in the right groove though I am hitting a steady 650kh/s.

        What I have found to work is to kill absolutely anything running on the computer and then start miner at lower intensity and bump it up to max to prevent the system from freezing.

        1 Reply Last reply Reply Quote 0
        • D
          DeadZebra Regular Member last edited by

          Ok cool I will give it a shot. On cgminer it says SICK next to the card.

          1 Reply Last reply Reply Quote 0
          • C
            ChristianRiesen Regular Member last edited by

            SICK is a hard hang, usually only a reboot fixes it. I have not found out exactly why it happens and when but I have seen that happen randomly on one of my cards. Strangely the card seems to be doing fine, then temps drop on the card slowly, and suddenly it says SICK. Still need to do more research there.

            I suspect a riser might be involved in the problem.

            1 Reply Last reply Reply Quote 0
            • A
              ASDASDASD last edited by

              That just means you have a really bad ass card! 8)

              But I just looked that up and it seems related to the drivers.

              Do you have the latest card specific drivers? Did you remember to download the AMD SDK to the new rig?

              1 Reply Last reply Reply Quote 0
              • D
                DeadZebra Regular Member last edited by

                Yeah software and hardware is the exact same as my other rig. Although I do get a .NET 4.0 error on that machine and it says MOM.exe needs it or something? Anyway it was never an issue with one card but now with this second card it really doesn’t like something.

                1 Reply Last reply Reply Quote 0
                • S
                  silentgaps Regular Member last edited by

                  I think your card can’t handle the overclock. make a different overclock for that card. hope it helps. :)
                  btw try -1 on intensity first.

                  1 Reply Last reply Reply Quote 0
                  • D
                    DeadZebra Regular Member last edited by

                    My other 3 cards run on the same overclock fine and they are the exact same cards.

                    1 Reply Last reply Reply Quote 0
                    • S
                      silentgaps Regular Member last edited by

                      I got the same problem last 2 weeks ago when I try to set a good overclock. What I did is, I set it to default, and then overclock again, after overclocking is set. I change the intensity +1 every 5 mins. until now my card didn’t experience that again.

                      1 Reply Last reply Reply Quote 0
                      • D
                        DeadZebra Regular Member last edited by

                        Thanks for all the advice people I will be having a look at the rig tonight when I get home. ;)

                        1 Reply Last reply Reply Quote 0
                        • D
                          DaMooMoo last edited by

                          Yep had this happen to me. Was caused by driver crashing due to overclocking the GPU memory. The driver recovers but cgminer does not and needs to be restarted. Maybe try setting the problem cards memory to default clock and gradually increase maybe in 50mhz steps until the driver crashes again. Then maybe decrease in 5mhz until you find the GPU’s sweet spot. e.g. my HD7760 would take 10 seconds to crash when set to 1050mhz, reduced it to 1045mhz and it was stable for about 3-4hours and then crash, finally setting it to 1040mhz and the card was happy.

                          1 Reply Last reply Reply Quote 0
                          • C
                            Clearcrystal15 last edited by

                            Expected a Monster rig when I saw the topictitle :P

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post