- This topic has 3 replies, 3 voices, and was last updated 15 years, 2 months ago by
.
-
Posts
-
Hi, this is my first time here and I have read through the forums and can’t really find my specific problem. However, in the n230 forum there is a problem similiar to mine where your netbook freezes when browsing Mozilla. I have a similiar problem. It started with my n130 freezing when I went on to Mozilla. I could then not get on the Task Manager to switch anything (it doesnt show a minimize, delete or enlarge option at the top left like most browser screens do). The computer doesnt recognize it froze (Mozilla acts like its a brand new browser and the computer doesn’t acknowledge any problems ). Over time, however, it has gone on to freeze systematically after 5 minutes regardless of what browser is up or whether there is in fact a window up at all. So far I have tested Google Chrome, Internet Explorer, iTunes, and not having any browser on at all. It has frozen every single time after around 5 minutes. Help!
I ended up doing a factory restore; and it worked (so far). BUT, I would like to know why this might have happened to make sure of why it happened in the first place as to make sure I dont do it again accidentally =)
Welcome to the forum msay,
Glad it seems fixed now. The only thing you can do is keep your eye on things as and when you change or add anything. No-one but you can know what you may or may not have done which might have brought about the issue.
And don’t attempt any ‘tweak’ unless you are definitely, positively, utterly sure of what side effects it may have. Or at least ensure that it is reversible 🙂
msay – Welcome to the forum
Several other forum members have reported freezing problems with Firefox, primarily the latest versions however your problems could have been caused by a Windows update. Can I suggest setting the updates to manual and selecting those that need to be installed and if the problem re-occurs then rolling back to a Windows Restore Point prior to the date of the update should resolve the issue and also isolate the offending update, if they are installed in singular succession.
Hope this helps
- You must be logged in to reply to this topic.