ARGHH!

Pneumonic

Pneumonic

Pneumonic

Soldato
Joined
19 Oct 2007
Posts
3,246
Location
Suffolk
ok anyone got an ideas on this one?!

Moved my machines over to SMP clients as it appears the normal unit servers are playing silly buggers...

So everything set up nicely and first machines is up and running in 5 mins and goes off an get a unit no problem... my other rig however whenever it tries to connect just gets assigned to server 0.0.0.0 useful huh?! been doing this now on and off for hours... where as I can end the other rigs unit and it will go off and get another one straight off... tried uninstall/reinstalling the client.. no help..

am going to re-install xp later on this rig anyways but if it keeps doing this I am going to be a bunny without a carrot = friggin unhappy
 
this used to happen a lot with a first install.....*racks brain*

I'm sure you needed to kill the active process three time in task manager, unistall reboot and then reinstall - or you my just have a machine that doesn't like WinSMP
 
I was being assigned 0.0.0.0 earlier for some reason too. My machine has no problems with winSMP normally and it resolved itself when I restarted windows.
 
0.0.0.0 usually occurs when the assignment server is borked - check the Stanford server stats page.
Just had a look and 171.64.65.64 should be working but 171.64.122.76 is on standby - which means the server isn't serving WUs. Could be the reason.
 
well the machine is unstable with the SMP client anways.. can't be the hardware as its unstable at stock.. even at super snail mode

I am guessing it might be the on board wireless card that is causing instability even though its totaly disabled (the asus drivers are like a damm virus you cant flippin get rid of em!)

So last resort is a clean install.. will set the client up as the first piece of software on the comp! and see what it does.. then run through windows update / the various software I need to install and see if anything interfears with it..

Just so odd that on the rig I setup yesterday I can run an smp client at a clock I know will fail prime in under 10 seconds... and it goes fine... yet on this rig it fails everytime.. yet I know its not a hardware instability! I have run an 8 hour blend test on the memory no issues, memtest no issues, the clock has more vcore and slower RAM timmings than the settings I used for a 24 hour prime small FFTs run..
 
You must log in or register to reply here.
Back
Top Bottom