I have this issue with Internet Explorer and Google Chrome simply locking up or hanging my system. I can't TAB to anything, I can't use the task manager, I can't click anything on the task bar. All I can do is close the browser or force boot my PC. I have been using FireFox for a long time and the browser is working fine. The main reason why i also use IE (and now trying Chrome) is I can't access my bank stuff and a few other pages in FF, so i kinda have to have another browser working.
There is a thread about this issue here:
It's sorta old but the issue is still not "fixed" since May 2009, the issues in that thread is mainly related to Google chrome.
Windows 7 Ultimate 64 bit
6 GB RAM
AMD Phenom II X2 544
Callisto 45nm Technology
Philips 244E ([email protected])
ATI Radeon HD 4600 Series
733GB Seagate ST3750528AS ATA Device (SATA)
Not sure any of that helps but who knows, because I'm out of ideas. One thing that does seem to work but isn't really a great solution is running FireFox THEN IE or Chrome, then there is zero issues. Close down FF and start IE or Chrome again and it locks up.
This is one of the responses from 08/31-10 (in the link provided)
I'm hoping someone with more computer/software knowledge than me maybe knows a little more or have any sort of fix/suggestions?This is DEFINTELY a bug in the CORE processes of the browsers. It may cause some extensions to fail and to be reported, but extensions are NOT the cause of this problem, because it happens VERY FREQUENTLY as well when using Chrome WITHOUT ANY extension, or when running Windows in safe boot mode (with minimal network support).
Google isconstantly giving FALSE hints to users (and dangerous instructions such as disabling antiviruses that are NOT the cause of this problem): this just avoids some reports.
I have this browser hang every 10 minutes on Wikipedia, when navigating in large pages, but sometimes as well when just opening or refreshing its default home page.
Cleaning browser's cache completely or even erasing completely the user's profile in AppData\Googlle\Chrome DOES NOT solve this problem (in fact it causes the problem to come again even faster...)
This is an old CRITICAL BUG signaled many times since TWO YEARS, but Google persists in considering this bug as non critical only because it cannot see it on its own (and specific) development systems, or because it does not cause the browser to crash, most of the time (it just causes the browser to hang and use all system ressources, so that the Google Crash Report process cannot even report it as it cannot even run, when the browser's core processes is stealing everything).