Reduce memory clock to ~300+. I have many times happened crashing of not only phoenix, but other miners also.
If i OC without reducing mem clock first then system freezes.
So, i always under clock memory manually with Afterburner, as mem clk CANNOT be reduce automatically, up to 300 then i apply OC.
Even though in Afterburner i saved the OC as 993/331, it will OC only core clock but can't under clock memory.
Just under clock memory & everything work fine.
Topic: Arrrghhh ... reboot issue due to software (Read 1619 times)
Solved .. I think. It was apparently my OC of just 950 core. I dropped to 900 and have had both mining contently for more than an hour. Weird that Furmark, Shogun 2, and Haven don't reveal this. MW2 had driver crashes at 960-ish, so I've just dropped down to 900 again. My hash rates have dropped by ~30-40 on each card though :\. I'll try to get away with 930 tomorrow. I need to mine to make up for all the lost time.
Believe it or not I was still convinced this was hardware. ;-) Applications, even ones designed to stress the GPU do not load your system identically. Even with same core temp and the same % load. For example a complex instruction like a BFI_INT might break under higher clocks/thermals because it's only just barely meeting the timing requirements under normal clocks/thermals. A benchmark is not guaranteed to execute every low-level instruction a card can perform (and is likely not going to execute ones that are hardware specific).
J.
Solved .. I think. It was apparently my OC of just 950 core. I dropped to 900 and have had both mining contently for more than an hour. Weird that Furmark, Shogun 2, and Haven don't reveal this. MW2 had driver crashes at 960-ish, so I've just dropped down to 900 again. My hash rates have dropped by ~30-40 on each card though :\. I'll try to get away with 930 tomorrow. I need to mine to make up for all the lost time.
Thought I found it when I removed aggression from one card. It lasted a good 15 minutes. Vectors maybe? This is just slightly annoying because if my system ever shuts down unexpectedly, my RAID driver automatically starts verifying the array, which makes the system take forever to start back up.
I used to be there, I have ten 1.5TB drives in my array. When I upgraded I saw that the build time was almost a whole day. So I switched to ZFS.
Thought I found it when I removed aggression from one card. It lasted a good 15 minutes. Vectors maybe? This is just slightly annoying because if my system ever shuts down unexpectedly, my RAID driver automatically starts verifying the array, which makes the system take forever to start back up.
The arguments I use follow: k phatk VECTORS BFI_INT AGGRESSION=8 worksize=128
So uhhh .... any ideas? Try poclbm on one card? I'm running Catalyst 11.5 with the 2.4 Stream SDK. Phoenix 1.48 with the included phatk version.
So uhhh .... any ideas? Try poclbm on one card? I'm running Catalyst 11.5 with the 2.4 Stream SDK. Phoenix 1.48 with the included phatk version.
Have you tried systematically removing kernel arguments until the system is stable?
This probably will not help, but try worksize=256 ?
So, I'm trying to run Phoenix Phatk on my dual 6870s (not crossfired), and some kind of software problem with phoenix makes the system reboot within two or three minutes once both cards are mining. This had me chasing my own tail forever until I realized it was a software problem and not an issue with my hardware. Extensive stress testing confirms this with certainty.
GPU clock is 975MHZ, RAM clock is 1100 MHZ.
No artifacts. Ever. No rejected shares, ever.
Either card can mine alone -- forever.
Both cards can run their own copy of furmark -- forever. No errors.
One card can run Shogun 2 maxed (90+% GPU usage at all times, identical thermals to Bitcoin mining) while the other mines coins. No issues.
Both cards can mine fine together IF AND ONLY IF one has no arguments set with Phoenix. I lose TONS of hashing power on that card (280-->230.)
The arguments I use follow: k phatk VECTORS BFI_INT AGGRESSION=8 worksize=128
So uhhh .... any ideas? Try poclbm on one card? I'm running Catalyst 11.5 with the 2.4 Stream SDK. Phoenix 1.48 with the included phatk version.
GPU clock is 975MHZ, RAM clock is 1100 MHZ.
No artifacts. Ever. No rejected shares, ever.
Either card can mine alone -- forever.
Both cards can run their own copy of furmark -- forever. No errors.
One card can run Shogun 2 maxed (90+% GPU usage at all times, identical thermals to Bitcoin mining) while the other mines coins. No issues.
Both cards can mine fine together IF AND ONLY IF one has no arguments set with Phoenix. I lose TONS of hashing power on that card (280-->230.)
The arguments I use follow: k phatk VECTORS BFI_INT AGGRESSION=8 worksize=128
So uhhh .... any ideas? Try poclbm on one card? I'm running Catalyst 11.5 with the 2.4 Stream SDK. Phoenix 1.48 with the included phatk version.
Jump to: