• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Fahmon reports GPU hung, what does that mean?

Camaroz06

Gawd
Joined
Jan 26, 2007
Messages
642
Hello All,
Quick question fahmon reports that a GPU client is hung, (epeen jokes aside) I take a look at the GPU log and I don't see any errors. What is fahmon reporting? When I start up fahspy nothing looks wrong either. I have noticed that the GPU client does indeed get stuck at a % but it doesn't error out, is this a hardware problem on my end or a quirk of the GPU client? Because when I start it up again everything is fine and it gets past the "hung" %.
 
Something is not stable. You may have to back off your overclock if you are OCing. It may be hot or power starved as well. It may also be an older client version or driver causing the problem.
 
That's weird. If I ran unstable OCs, it would just EUE until I lowered the clocks.
Is the GPU on the same system you're monitoring it with FahMon?
If not, it might be as simple as the time is different on the two machines and you'll see a client hung.

If that's the case, go to:

Toolbar/FahMon/Preferences/Monitoring
Check the "Ignore asynchronous clocks"
 
Hello All,
What is fahmon reporting? When I start up fahspy nothing looks wrong either.

It seems to be a characteristic/feature of FahMon to report *Hung* clients even though the client is crunching away on a work unit. I see this all the time [in fact checking my Fahmon now it show one of my 5 GPU clients as hung .... ] .

Right click the hung client in your FahMon list and "Refresh selected" ... maybe have to do it a few times in a row and it should revive the proper status.
 
I was overclocking a new card a couple days ago and got the eue . soo i clocked down restarted gpu client and was getting terrible tpf 1:45 on a 353 with a gtx260 rebooted still the same. set to stock setting nothing, i reinstall the drivers ah ha all fixed
 
think I found the problem on this one, one of my RAM sticks is partially dead, ran mem check and there were errors everwhere!

Down to 1GB in my system, I am currently waiting for another crucial RMA, not having much luck with the Ballistix in my 680i. I might just dump the mobo to a htpc and pick something else up for my folder/photoshop rig.
 
Spoke too soon, it still hung. I dint have the card at an overclock though. I was running it at stock speeds. It is an "overclock from factory" card though I bought as an open box. I am putting it down to normal card stock speeds to see what happens.
 
It seems to be a characteristic/feature of FahMon to report *Hung* clients even though the client is crunching away on a work unit. I see this all the time [in fact checking my Fahmon now it show one of my 5 GPU clients as hung .... ] .

Right click the hung client in your FahMon list and "Refresh selected" ... maybe have to do it a few times in a row and it should revive the proper status.

Have any of your clients actually hung? I took a look at the FAH log and it was indeed stuck at a % for some time. It never produces an error though.
 
Have any of your clients actually hung?

Not that I can recall. I'm far more prone to EUE's/yellow with th 101xx projects (which are real).

HFM does not seem to have this problem. A manual refresh (or three) gets FahMon back on track.
 
Back
Top