Scrapebox problems! does anyone know how to fix this?

Tried cleanmem, did not help, also running on windows 7 32bit..... even if i split the list in batches it still does this after a while and i don't believe it is a ram problem as my notebook is running ok, no crashes no slow down...dunno why this happens...btw i also tried setting sb to run under xp mode and still the same
 
Delete the temp internet files and run the disk cleanup tool on C:
The programs that are supposed to free up ram are useless.
 
Delete the temp internet files and run the disk cleanup tool on C:
The programs that are supposed to free up ram are useless.


did that, used atf cleaner, ccleaner and disk cleanup tool and still the same, it must be something related to the cache
 
window 7 run like a dog with only 1GB ram -- need about 4 GB

best to use xp if you only have 1 GB
 
window 7 run like a dog with only 1GB ram -- need about 4 GB

best to use xp if you only have 1 GB

well, it runs ok so far as i have tweaked some stuff, anyways i am thinking of going for the vaio z series with 8gb ram, until then i have to work with what i have :)
 
Any solution to this? I'm experiencing the same problem and I have a good spec PC so far (Athlon X2 64bits, 4 gb Ram, almost 200 GB of HD free). I can't run any process for more than 5k blogs because Scrapebox freezes and I lost all the information and my IE or FF refuses conections so I need to restart PC (althought the PC works fine, just SB frozen and no internet).

:confused:
 
Seems no solution to this yet. I think i rebooted my machine about 40 times today...loool
 
Well, it sounds like you have tried a lot of the common troubleshooting steps for this, and the TCP half-open patch doesn't apply to Win 7, so...just a couple somewhat educated guesses...

Proxies could definitely be a culprit in the internet connectivity getting fockered, but...the part about your system drive running out of space...very hinky. Run a full security sweep lately? Like mbam in safe mode, then maybe hitman pro, kaspersky, or something along those lines? The part about your C drive running out of space is...unusual.

Also, just FYI, I have run sbox on a machine w/512MB RAM and while it was not a pleasant experience (nothing in the OS was until I bumped it up to 2GB), the program was able to run and complete tasks like this.
 
Well, it sounds like you have tried a lot of the common troubleshooting steps for this, and the TCP half-open patch doesn't apply to Win 7, so...just a couple somewhat educated guesses...

Proxies could definitely be a culprit in the internet connectivity getting fockered, but...the part about your system drive running out of space...very hinky. Run a full security sweep lately? Like mbam in safe mode, then maybe hitman pro, kaspersky, or something along those lines? The part about your C drive running out of space is...unusual.

Also, just FYI, I have run sbox on a machine w/512MB RAM and while it was not a pleasant experience (nothing in the OS was until I bumped it up to 2GB), the program was able to run and complete tasks like this.

thx for the info Greg, i will try tu bump up the RAM sometime next week, hope i get this sorted out since it's bugging the f*ck out of me :)
 
It can be caused by proxies. Bad proxies can cause the TCP state to go into FIN_WAIT_x state, which can last 10 minutes. During that time, the port is not available. Even the application shutdown the socket, the remote peer doesn't respond, and it end up in a FIN_WAIT_1.

What does that mean? Windows will run out of ports and when that happen, you internet connections seems to be not working anymore.

You have about 16384 available ports (you can test this by typing this at the command prompt: netsh int ipv4 show dynamicport tcp).

With bad proxies, it wont take long and all ports are in FIN_WAIT_x state...
 
It can be caused by proxies. Bad proxies can cause the TCP state to go into FIN_WAIT_x state, which can last 10 minutes. During that time, the port is not available. Even the application shutdown the socket, the remote peer doesn?t respond, and it end up in a FIN_WAIT_1.

What does that mean? Windows will run out of ports and when that happen, you internet connections seems to be not working anymore.

You have about 16384 available ports (you can test this by typing this at the command prompt: netsh int ipv4 show dynamicport tcp).

With bad proxies, it wont take long and all ports are in FIN_WAIT_x state...

Thx for the help, but what to do next to prevent this from happening?
 
To be sure it is the FIN_WAIT issue, I would first run a port scanner like curports (http://www.nirsoft.net/utils/cports.html) and check if the ports are indeed going into FIN_WAIT_x state. If they do, then I would change the proxies, maybe using private proxies. If they do not, the we are back at ground 0...
 
To be sure it is the FIN_WAIT issue, I would first run a port scanner like curports (http://www.nirsoft.net/utils/cports.html) and check if the ports are indeed going into FIN_WAIT_x state. If they do, then I would change the proxies, maybe using private proxies. If they do not, the we are back at ground 0...

cool, just one more question..i do the scan after i get the issue and i can't load any web pages anymore?
 
To be sure it is the FIN_WAIT issue, I would first run a port scanner like curports (http://www.nirsoft.net/utils/cports.html) and check if the ports are indeed going into FIN_WAIT_x state. If they do, then I would change the proxies, maybe using private proxies. If they do not, the we are back at ground 0...


I used cports for couple of weeks now an noticed that some ports are going into fin_wait2 state and then get back to normal. When everything drops, curports does not show anymore active connections from scrapebox and everything happens as i mentioned at the beggining of my thread.

Is there any other way around this?
 
btw, forgot to ask, is there anyway to unblock the ports which entered fin_wait state so that i wont have to restart my machine every half hour ?
 
Back
Top