Help - RS lag...

[Shelby_Polo]

Lately I've been experiencing some unusual lag. What happens is, the game runs fine for about 30 seconds to a minute, then "freezes" for about 5 seconds, and repeats. This has just started happening to me the last few days; I've done everything I can think of to try and stop it.

 

Including:

 

-Not playing on high detail and running RS in safe mode.

 

-Choosing a different world

 

-"Cleaning" my computer (Disk Defrag, Clearing Cathe's, ONLY running RS)

 

 

 

I'm using a HP Laptop.

 

 

 

I have the latest version of Java.

 

 

 

I use Firefox, also up-to-date.

 

 

 

For all that it helps, I don't think my laptop is overheating; I can usually tell if it is anyway.

 

And I'm also wireless, but most times I have a 'good' connection. So it shouldn't be either of those.

 

 

 

Comp Specs:

 

Windows Vista

 

32-bit Operating system

 

1.60 GHz Processor

 

1GB Memory

 

 

 

I should also add, I've looked at the rsof sticky about lag (didn't help :cry: )

 

 

 

Thanks in advance

 

:thumbsup:

[OldJoe]

Remove any old versions of Java.

 

Are you sure that no-one in your network is torrenting?

 

Have you tried another browser, such as IE/Opera/Safari?

[Shelby_Polo]

No one else on my network uses their computer lol

 

And I've tried IE, Safari and Google Chrome. And Firefox works the best

[sloter]

No one else on my network uses their computer lol

 

And I've tried IE, Safari and Google Chrome. And Firefox works the best

 

Your neighbors(if you have wireless)?

[Shelby_Polo]

No one else on my network uses their computer lol

 

And I've tried IE, Safari and Google Chrome. And Firefox works the best

 

Your neighbors(if you have wireless)?

 

 

 

lol ya.

 

Actually no, our router is password protected, so were all good.

[Phil]

You said cleaning, does that include virus and spyware scans?

[J35u5_M4]

Ctrl+Alt+Del (NOT the comic), press those keys at once, and check Processes Tab, on the CPU column you, there should be a high number at the bottom, called System Idle Process, that's the % of RAM that isn't being used, look up all the list and delete any program that you know, like a torrent that has a VERY high number (40+, won't be a window process because they don't use that much) if there aren't any, then I don't know :/

[Phil]

Ctrl+Alt+Del (NOT the comic), press those keys at once, and check Processes Tab, on the CPU column you, there should be a high number at the bottom, called System Idle Process, that's the % of RAM that isn't being used, look up all the list and delete any program that you know, like a torrent that has a VERY high number (40+, won't be a window process because they don't use that much) if there aren't any, then I don't know :/

 

If he's not sure what he's doing in there - post a screenshot of it for us. Either that or post a hijackthis log.

[Shelby_Polo]

You said cleaning, does that include virus and spyware scans?

 

 

 

Yep, my computer is very clean

 

 

 

Ctrl+Alt+Del (NOT the comic), press those keys at once, and check Processes Tab, on the CPU column you, there should be a high number at the bottom, called System Idle Process, that's the % of RAM that isn't being used, look up all the list and delete any program that you know, like a torrent that has a VERY high number (40+, won't be a window process because they don't use that much) if there aren't any, then I don't know :/

 

 

 

Mmk I did that and the only two things running are Firefox and Task Manager

[Nadril]

Processes tab, not applications.

[D. V. Devnull]

TheLeonardo, a super-serious note of warning here... Terminating items on the "Processes" tab of task manager can result in system instability and crashes. Only terminate something if you can identify it as being bad. Otherwise, you should leave it alone. :ugeek:

 

 

 

(Personally, I would 'monkey' with my startup settings long before I would go hard-terminating anything on that tab!!!)

 

 

 

 

 

 

 

BTW, could we have a HJT log, please? We might be able to tell if anything does need a knockdown in your startup section. :-k

 

 

 

 

 

~Mr. D. V. "Yeah, you don't want to bug that." Devnull

[urbestfreind]

TheLeonardo, a super-serious note of warning here... Terminating items on the "Processes" tab of task manager can result in system instability and crashes. Only terminate something if you can identify it as being bad. Otherwise, you should leave it alone. :ugeek:

 

 

 

(Personally, I would 'monkey' with my startup settings long before I would go hard-terminating anything on that tab!!!)

 

 

 

 

 

 

Well, if you terminate a process that's important for system stability, when you reboot, that process should be running again, and your system will be fine.

 

 

 

Stop a nescessary thing at startup, however, and your computer will crash on reboot, which can lead to a whole mess of problems. I would much rather stop a process through task manager than forever stop it in msconfig.

 

 

 

If you really want to be sure you are stopping something harmless, get Process Explorer. It's free, it's from Microsoft, and it's useful (3 things you rarely see/hear in the same sentence). Even if you use autoruns (again from MS), you still run the risk of stopping something vital from starting up.

 

 

 

Mr. ur"wishes DVD would stop putting stupid things in quotes when saying his name"bestfreind.

[Sbrideau]

 

 

 

Mr. ur"wishes DVD would stop putting stupid things in quotes when saying his name"bestfreind.

 

 

 

I actually like them, makes me laugh a bit after a hard day ;).

 

 

 

Neway, on topic: What urbestfriend said is true, it's a lot more safer to kill processes there than doing it in msconfig.

[D. V. Devnull]

Mr. ur"wishes DVD would stop putting stupid things in quotes when saying his name"bestfreind.

I actually like them, makes me laugh a bit after a hard day ;).

Always glad to give a good laugh out. :)

 

 

 

<<<Quote Snip>>>

 

 

 

Well, if you terminate a process that's important for system stability, when you reboot, that process should be running again, and your system will be fine.

 

 

 

Stop a nescessary thing at startup, however, and your computer will crash on reboot, which can lead to a whole mess of problems. I would much rather stop a process through task manager than forever stop it in msconfig.

 

 

 

If you really want to be sure you are stopping something harmless, get Process Explorer. It's free, it's from Microsoft, and it's useful (3 things you rarely see/hear in the same sentence). Even if you use autoruns (again from MS), you still run the risk of stopping something vital from starting up.

Neway, on topic: What urbestfriend said is true, it's a lot more safer to kill processes there than doing it in msconfig.

Unless it knocks your PC so unstable that you can't shutdown or reboot or do anything other than hitting the power switch. Further, msconfig can actually show you stuff that you really don't want to be messing with there. (e.g.: The option to hide critical/essential processes... At least, it was there the last I'd heard/remembered.) :-k ... And of course, there is the ever-infamous "Safe Mode" option for booting with in the event something is killed that really shouldn't have been. Which, BTW, if you do kill something that critical with msconfig, it should fly near straight into Safe Mode, instead of trying to run in that 'ganked' state, so you can instantly undo what you did before it can have any bad consequences. :

 

 

 

~D. V. "That's odd... I heard otherwise." Devnull

[sloter]

No one else on my network uses their computer lol

 

And I've tried IE, Safari and Google Chrome. And Firefox works the best

 

Your neighbors(if you have wireless)?

 

 

 

lol ya.

 

Actually no, our router is password protected, so were all good.

 

Saying know one could have guessed or cracked it?

[D. V. Devnull]

No one else on my network uses their computer lol

 

And I've tried IE, Safari and Google Chrome. And Firefox works the best

Your neighbors(if you have wireless)?

lol ya.

 

Actually no, our router is password protected, so were all good.

Saying know one could have guessed or cracked it?

LOL! :lol: ... Would be kinda sad if the pass on the wireless was that weak. :P

 

 

 

~D. V. "Oh, geez... LOL!" Devnull

[Nadril]

A lot of Wireless encryption can be bypassed fairly easy through brute force using certain programs. Not saying that this is the case at all, but it is possible.

 

 

 

Unless it knocks your PC so unstable that you can't shutdown or reboot or do anything other than hitting the power switch. Further, msconfig can actually show you stuff that you really don't want to be messing with there. (e.g.: The option to hide critical/essential processes... At least, it was there the last I'd heard/remembered.) :-k ... And of course, there is the ever-infamous "Safe Mode" option for booting with in the event something is killed that really shouldn't have been. Which, BTW, if you do kill something that critical with msconfig, it should fly near straight into Safe Mode, instead of trying to run in that 'ganked' state, so you can instantly undo what you did before it can have any bad consequences

 

 

 

Really Devnull? The worst that will happen from killing a process is your PC reboots and, thus, all of the processes reboot as well. Kill it in msconfig and it won't be booting that up.

 

 

 

And really, I'd figure it would be easier for processes to get automatically restarted instead of the user trying to figure out how exactly he killed his machine.

 

 

 

~Nad "D_V_Devnull shouldn't be near computers" ril

[D. V. Devnull]

Meh.....Maybe I'm just a lot more careful with my msconfig than the average user, and that's why I'm able to rely on that method more. -.-

 

 

 

(Off-Topic: BTW, quit trying to start something with your insults aimed at my 'thought-in-quotes' signatures. It really doesn't say much for people's IQ/maturity when they start firing those kinds of insults. :shame: ...)

 

 

 

~D. V. "Carefulness Counts..." Devnull