Hi Feedomstar,
Sorry to hear about your problems.
I've recently completed a clean install of XP SP3 plus the usual programs / utilities. I brought the DOT NET framework up to 3.5 plus all serive packs and most OS updates.
When FF 3.06 auto-updated to 3.0.7 the wheels fell off my happy (nice clean) system and ...
FF crashed fairly regularly and
FF did not warn me about closeing multiple tabs ... it's this that was annoying most of all.
I removed FF completely and reinstalled 3.0.6- problem solved. And I updated this installation of FF from within the browser rather than use the standalone installer.
I use too many FF addons for my own good ...
Adblock Plus 1.0.1
Adblock Plus: Element Hiding Helper 1.0.5
All-in One-Sidebar 0.7.10
AUSTLII Toolbar 1.1.7
Bigpond File check 0.1
Download Status bar 0.9.6.4
Download Helper 4.2
Downloadthemall 1.1.1
Duplicate Tab 1.0.2
Extended status bar 1.5.3
FEBE 6.1 (profile backup / restore utility)
FireFTP 1.0.4
Flashgot 1.1.8
Free Download Manager 1.3.4
Freecorder Toolbar 1.5.31.0 ... my primary suspect
Huperwords 5.3
Java Qucik Starter 1.0 (did not choose this - it appeared after updating the JRE)
Microsoft .Net Franework Assistant 1.0 (don't recall choosing this but might have been part of the install / update process for DOT NET)
Net Usage Item 1.2.215.1 (really brilliant)
Norton IPS 1.0 (norton intrustion protection)
Norton Toolbar 3.5
Send to URLS 2.0
SmartWhiIs Launcher 1.8 - doesn't work :)
Tab control 0.4.1
Tab Saver 1.1.2
The crashes / problems with FF occurred before I updated to 16.5 but after I installed a couple of MS XP security patches.
Like I said, I use far too many add-ons for my own good. But I don't have any problems since unistalling FF 3.0.7, rebooting, downgrading and the updating via FF itself.
When the problems appeared a number of other programs updated too ... including Adobe and many of the FF addons.
I never really found out what caused the problem but suspected it might be related to the DOT NET framdwork updates and or Freecorder (FF addon).
So ... I can confirm similar problems (now resolved) without 16.5 update ... suggests the update *may* not be the cause of this problem but an APE (alternate plausible explanation).
When I did update to 16.5 (manually) ... could not have been an easier process. Quite uneventful.
Hope this helps ... I agree that it might help if we give addon info / status of our DOT NET installation when posting to see if a pattern appears.
Cheers.
Mike