This happens every time I go in to IE8. Complete freeze - have to hard reboot. Restoring IE8 to default settings, uninstalling IE8 & using IE7, and running IE8 without add-ons - none of these worked.I can access Internet via Google Chrome & Safari, also BBC iPlayer & Sky Player, and other Internet-linked programs. No other use of the PC consistently causes crashes, although it does occasionally.I have Automatic Windows Update, BT NetProtect Plus from McAfee and do regular scans. I have run CCleaner several times and tried other utilities, without success. Today I have downloaded a number of suggested fixes from Microsoft, none of which have worked.But I need to use IE because my work's remote-access Citrix applications only seem to work with IE, not Google Chrome, etc.Please help!!1 person needs an answerI do too

you might try testing ie via safeboot w/networkingdb`...>-)))> `...>-)))> share the nirvana mann

XP doesnt care to much for switching back & forth in IE...Stick with IE8,reset internet options tabs,try disk clean-up,defrag,chk out install/uninstall programs,windows components,edit the networking add-ons,SP3 uninstalls/unchecks boxes that were checked before,last,open cmd prompt,type: netsh Winsock reset Agree,exit,restart pc.

You used the freeze word and the crash word.When I hear "crash", I think of the Blue Screen of Death crash...If your system stops responding, hangs or freezes and you can't figure out why, you can force a Blue Screen of Death (BSOD) which will create a crash dump file that you can analyze and see what is running at the point of the freeze and get some ideas that do not involve guesswork.While it may seem odd to think about purposefully causing a Blue Screen Of Death (BSOD), Microsoft includes such a provision in Windows XP. The feature is built in to XP specifically to diagnose the problem when a system stops responding.This will eliminate trying things or guessing about what might have happened maybe.Sometimes there will not even be a clue about the problem in the Event Log.Here's how to force your system to create a BSOD:First make sure your system is not set to automatically restart on a system failure.Right click My Computer, Properties, Advanced, Startup and Recovery, Settings.In the System failure section:Put a check mark in the "Write an event to the system log" box.Put a check mark in the "Send an administrative alert" box.Uncheck the "Automatically restart" box.In the Write debugging information section, choose:Small memory dump (64 KB)Set the Small dump directory to:%SystemRoot%\MinidumpClick OK twice to save the settings.Now enable the XP feature to generate a crash dump on demand.Before making registry changes (there is no undo or quit without saving in the registry editor), backup your registry with this popular free and easy to use tool:http://www.snapfiles.com/get/erunt.htmlFor PS/2 keyboards, launch the Registry Editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\i8042prt\ParametersFor USB keyboards, launch the registry editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\kbdhid\ParametersClick Edit, select New DWORD Value and name the new value:CrashOnCtrlScrollDouble-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value Data text box to enable the feature, and click OK. Close the Registry Editor and restart Windows XP for the changes to take effect.When you want to cause a BSOD (when your system has stopped responding), press and hold down the [Ctrl] key on the right side of your keyboard, and then tap the [ScrollLock] key twice. Now you should see the BSOD and you will have a crash dump file to analyze.You may not see much meaningful information about your problem on the BSOD screen, but you will find the answer in the crash dump files. You may need some help interpreting your crash dump files if you have never seen one before, so that is okay too.You can read about the feature here:http://msdn.microsoft.com/en-us/library/ff545499.aspxThere is no harm in leaving the feature enabled (mine is always on), but if you are compelled to remove it, just undo the change you made in the registry.Launch the Registry Editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\i8042prt\Parameters orHKLM\System\CurrentControlSet\Services\kbdhid\ParametersSelect the CrashOnCtrlScroll value, click the Edit menu, and select the Delete command. Close the Registry Editor and restart Windows XP. Go ahead and test the new manual crash dump on demand feature to be sure it works as expected, then wait for the system to hang again and get some crash dumps of the system when it is hung up.Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

You used the freeze word and the crash word.When I hear "crash", I think of the Blue Screen of Death crash... If your system stops responding, hangs or freezes and you can't figure out why, you can force a Blue Screen of Death (BSOD) which will create a crash dump file that you can analyze and see what is running at the point of the freeze and get some ideas that do not involve guesswork or trying things that might work.While it may seem odd to think about purposefully causing a Blue Screen Of Death (BSOD), Microsoft includes such a provision in Windows XP. The feature is built in to XP specifically to diagnose the problem when a system stops responding.This will eliminate trying things or guessing about what might have happened maybe.Sometimes there will not even be a clue about the problem in the Event Log.Here's how to force your system to create a BSOD:First make sure your system is not set to automatically restart on a system failure.Right click My Computer, Properties, Advanced, Startup and Recovery, Settings.In the System failure section:Put a check mark in the "Write an event to the system log" box.Put a check mark in the "Send an administrative alert" box.Uncheck the "Automatically restart" box.In the Write debugging information section, choose:Small memory dump (64 KB)Set the Small dump directory to:%SystemRoot%\MinidumpClick OK twice to save the settings.Now enable the XP feature to generate a crash dump on demand.Before making registry changes (there is no undo or quit without saving in the registry editor), backup your registry with this popular free and easy to use tool:http://www.snapfiles.com/get/erunt.htmlFor PS/2 keyboards, launch the Registry Editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\i8042prt\ParametersFor USB keyboards, launch the registry editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\kbdhid\ParametersClick Edit, select New DWORD Value and name the new value:CrashOnCtrlScrollDouble-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value Data text box to enable the feature, and click OK. Close the Registry Editor and restart Windows XP for the changes to take effect.When you want to cause a BSOD (when your system has stopped responding), press and hold down the [Ctrl] key on the right side of your keyboard, and then tap the [ScrollLock] key twice. Now you should see the BSOD and you will have a crash dump file to analyze.You may not see much meaningful information about your problem on the BSOD screen, but you will find the answer in the crash dump files. You may need some help interpreting your crash dump files if you have never seen one before, so that is okay too.You can read about the feature here:http://msdn.microsoft.com/en-us/library/ff545499.aspxThere is no harm in leaving the feature enabled (mine is always on), but if you are compelled to remove it, just undo the change you made in the registry.Launch the Registry Editor (Start, Run, regedit.exe) and navigate to:HKLM\System\CurrentControlSet\Services\i8042prt\Parameters orHKLM\System\CurrentControlSet\Services\kbdhid\ParametersSelect the CrashOnCtrlScroll value, click the Edit menu, and select the Delete command. Close the Registry Editor and restart Windows XP. Go ahead and test the new manual crash dump on demand feature to be sure it works as expected, then wait for the system to hang again and get some crash dumps of the system when it is hung up. Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!