F@H SMP Client random process ending..

[ch33zw1z]

Running F@H SMP client on a P5K + E6600 @ 333x9. Regardless of clock speed, this still happens. Basically, the four FahCore_a1.exe's just close. However, fah.exe remains open. It's weird, and happens more frequently some days than others...is this a known problem?

 

[GLeeM]

Originally posted by: ch33zw1z
Running F@H SMP client on a P5K + E6600 @ 333x9. Regardless of clock speed, this still happens. Basically, the four FahCore_a1.exe's just close. However, fah.exe remains open. It's weird, and happens more frequently some days than others...is this a known problem?

It sounds like one of the known problems.

Changes in network.

If anything changes to network all FahCore_a1.exe's close but the console window stays open. I usually check temps or TaskManager to make sure all is OK.

A loose wire wiggled a bit was causing some of my problems.

Wireless can also cause it.

A changed address does too.

When I was on dial-up I had to close the client after downloading a new WU, make sure I was disconnected when I restarted. Then it would not have any problems again (even if I dialed up numerous times) until the client used the internet to send results and get new WU.

 

[ch33zw1z]

Thanks for the reply. I tightened up the two network connections on my rig. My temps around about 52C on both cores while running F@H, temps checked with CoreTemp. I'll keep working on it!

 

[GLeeM]

I don't think it is a temp or OC thing - those will give an error.

If tightening the connections doesn't help, you could try the below suggestion.

If you are near the beginning of the WU (so that it will run for long enough to prove this to you) you can prove it is the network thing.

Close the client.
Disable Local Area Connection (double click on icon next to clock in lower right and click Disable in dialog that opens)
Start the client after network is disabled.
After client gets into WU a few minutes then Enable Local Area Connection.

It should run without problem until the WU finishes and uses the internet. Sometime after that you can have problem again.

Does your router or ISP change your IP address often?

 

[LOUISSSSS]

i had the same problem where my clients wouldn't start up. its not an OC problem...
i couldn't figure it out so i reinstalled everything and everythings been working fine for the past 48 hours

 

[ch33zw1z]

Originally posted by: GLeeM
I don't think it is a temp or OC thing - those will give an error.

If tightening the connections doesn't help, you could try the below suggestion.

If you are near the beginning of the WU (so that it will run for long enough to prove this to you) you can prove it is the network thing.

Close the client.
Disable Local Area Connection (double click on icon next to clock in lower right and click Disable in dialog that opens)
Start the client after network is disabled.
After client gets into WU a few minutes then Enable Local Area Connection.

It should run without problem until the WU finishes and uses the internet. Sometime after that you can have problem again.

Does your router or ISP change your IP address often?

Pushing out the securing tabs on the network cable has seemed to help. It ran overnight without dropping *knock on wood* I do have two network connections running, maybe the client gets confused?

I will try the suggestions if the issue persists. My IP has been the same for 1 year+.

 

[Diogenes2]

This was driving me nuts also ... Found it happened whenever I reset my router ... ( for whatever reason )

 

[LOUISSSSS]

okay now i'm getting the same problem. both of my SMP clients keep hanging. i dunno if its at the same time or w/e cuz i'm usually away from my computer when it happens
i come back and see FAHMON *HUNG*

what are you guys doing to fix this?

(if it helps, i'm on wireless)

 

[Insidious]

I set my ip address manually on the machines that are on wireless connections to addresses outside the range that the router assigns using DHCP.

ie: The router is set to use DHCP addresses from .100 to .150, (addresses up to .250 or so are allowable) so I assigned the PC to addres 160. This way there is no 'lease' on the address and it doesn't get re-newed or re-assigned. So far, I've only had one hang and that was when the cat pulled the router plug out of the wall.

Hope that helps. If you need more detail on how to do this, let me know and I'll post tomorrow with specifics. (If you are on XP.... I don't know squat about Vista)

-Sid

 

[LOUISSSSS]

Originally posted by: Insidious
I set my ip address manually on the machines that are on wireless connections to addresses outside the range that the router assigns using DHCP.

ie: The router is set to use DHCP addresses from .100 to .150, (addresses up to .250 or so are allowable) so I assigned the PC to addres 160. This way there is no 'lease' on the address and it doesn't get re-newed or re-assigned. So far, I've only had one hang and that was when the cat pulled the router plug out of the wall.

Hope that helps. If you need more detail on how to do this, let me know and I'll post tomorrow with specifics. (If you are on XP.... I don't know squat about Vista)

-Sid

yes, can u give more details on how to do this and how will it affect my internet experience? slower/faster(?) i'm on XP

 

[Insidious]

Note: Before you start any of this, re-start Windows to make sure your F@H clients are not runninig. Also as you go along, remember what your original settings are in each place I'm going to have you change things so you can get back if you choose to later.

first check your router settings to see what is the starting address of DHCP (it's normally in the basic setup section.) For instance, mine says the starting address is 192.168.1.100

in one of the next entries it should tell you how many is the maximum number of DHCP users is. mine says 50, so that means that addresses ranging from 192.168.1.100 to 192.168.1.150 are DHCP assigned addresses which will be renewed periodically and can even be changed automatically by the router (this borks up the SMP clients).

from the above, I know that any address from 192.168.1.2 to 192.168.1.149 and addresses from 192.168.1.151 to 192.168.1.254 are all free to have clients with static addresses. (ones that won't change)

From this I decided to give my wireless PC the address of 192.168.1.160 (I just picked one)

Next, we have to set lup your PC with the static address.

First, right-click on the my network places icon and select properties from the drop-down menu.

double-click the wireless connection entry to pop up the local area status window. Select the support tab

write down the entries you see for subnet mask and default gateway. now click on the details tab and copy down the addresses for DNS servers. now close the status window and right click the wireless connection entry in my network places and select properties

in the window that comes up, highlight the internet protocol (TCP/IP) entry and then click the properties button.

we are going to select the 'Use the following IP address' button (which clears the 'Obtain an IP address automatically' button)

enter the IP address you chose to be the static address of your PC in the IP address section. Then enter the addresses you copied earlier into the subnet mask and Default gateway entries.

enter the DNS server addresses you copied earlier too.

You're done. re-boot windows and make sure your internet is working then start F@H

As to how this affects your internet experience, it doesn't make any changes to it at all. The only difference I notice is that my wireless connection gets made much faster when I re-start windows (which is nice!)

hope this helps

Sid

 

[ch33zw1z]

It's been hanging less since tightening up the network cables, but it seems that whenever there's a network change it will hang. I have a PCIE Gbit adapter that's a direction connection to another machine, when the other pc was turned off, the SMP client hung...

 

[Insidious]

Originally posted by: ch33zw1z
... whenever there's a network change it will hang.

... I have a PCIE Gbit adapter that's a direction connection to another machine, when the other pc was turned off, the SMP client hung...

The SMP client uses the network loopback adapter for the threads to communicate amongst themselves. If the network is disturbed (in windowsXP) the SMP clients will usually loose their minds.

-Sid

 

[ch33zw1z]

Originally posted by: Insidious

Originally posted by: ch33zw1z
... whenever there's a network change it will hang.

... I have a PCIE Gbit adapter that's a direction connection to another machine, when the other pc was turned off, the SMP client hung...

The SMP client uses the network loopback adapter for the threads to communicate amongst themselves. If the network is disturbed (in windowsXP) the SMP clients will usually loose their minds.

-Sid

Is there a way to tell it to use only one of my NICs? I have one connected to the router, with ICS, and the other is as described earlier. Can neither change?

 

[Insidious]

I don't know. It all comes down to this MPI application that F@H is using and Stanford says it is flawed in WindowsXP

I doubt if you have any way to configure this usage other than disabling the LAN ports you don't want it to use.

-Sid

 

[ch33zw1z]

Thanks Sid for the info. One last question for you guys...does the Linux SMP client has this issue as well?

 

[Insidious]

I think the Linux SMP client is pretty much stable, without these issues.

-Sid