Alright folks, let's see if anyone else has some luck with this issue. I am at wit's end.
Hardware:
EVGA 650i Ultra 775 MB
Core 2 Duo E6420, AC 7 Pro Heatsink/Fan
2GB OCZ XTC PC6400
500GB Seagate 7200.11 SATA
Sony DVD+/-RW SATA
USB Card Reader
XFX 8800GS 384MB PCI-E
Antec Earthwatts 500W PSU, Sonata III Case
Software:
Windows XP SP2 & SP3
Minimal drivers
Problem:
Fresh installation of windows, install NVIDIA MB drivers, install Firefox (v2 and v3 tried). Open up 5 or 6 tabs in Firefox...leave for 2-3 days. Slowly, Firefox becomes nonoperational and unresponsive to things like closing tabs, minimizing the window, all links on a page, scrolling etc. My quick launch bar suddenly stops allowing icons to move around. Strange. Literally, I cannot drag an icon to a different position on the quick launch bar. I can pick it up and place it but it does not actually move.
Fixes:
Opening a new window (not tab) of Firefox and then closing it allows me to make a few operations or clicks within the Firefox window that was dieing before it stops working again. Restarting Firefox lets me work in Firefox for a good 10-15 minutes before the problem creeps up again. Restarting the PC sends me back to 1-2 days of normal operations.
Notes:
Seems like a memory leak doesn't it? Looking at task manager, no programs (including Firefox) are using an abnormal amount of memory or CPU. I have reinstalled Windows, trying different things, at least 8 times. This includes using different XP discs and versions. I have also of course tried installing all the correct drivers. I have replaced or exchanged with a similar part ALL of the hardware listed except the PSU and HDD. EVERYTHING else has been exchanged or removed in an attempt to see if it was the problem. What the heck is with the quick launch bar?
I am certain other problems exist as well but this is the point I haven't passed. The system passes a 48 hour loop of Prime 95 / Orthos / Memtest86 with flying colors.
1 Cookie for the winner. HELP!
Update: tried replacing the CPU with a Q6600 - didn't fix it. SP2 has already been tried as a few of you noted SP3 might be the problem.
Hardware:
EVGA 650i Ultra 775 MB
Core 2 Duo E6420, AC 7 Pro Heatsink/Fan
2GB OCZ XTC PC6400
500GB Seagate 7200.11 SATA
Sony DVD+/-RW SATA
USB Card Reader
XFX 8800GS 384MB PCI-E
Antec Earthwatts 500W PSU, Sonata III Case
Software:
Windows XP SP2 & SP3
Minimal drivers
Problem:
Fresh installation of windows, install NVIDIA MB drivers, install Firefox (v2 and v3 tried). Open up 5 or 6 tabs in Firefox...leave for 2-3 days. Slowly, Firefox becomes nonoperational and unresponsive to things like closing tabs, minimizing the window, all links on a page, scrolling etc. My quick launch bar suddenly stops allowing icons to move around. Strange. Literally, I cannot drag an icon to a different position on the quick launch bar. I can pick it up and place it but it does not actually move.
Fixes:
Opening a new window (not tab) of Firefox and then closing it allows me to make a few operations or clicks within the Firefox window that was dieing before it stops working again. Restarting Firefox lets me work in Firefox for a good 10-15 minutes before the problem creeps up again. Restarting the PC sends me back to 1-2 days of normal operations.
Notes:
Seems like a memory leak doesn't it? Looking at task manager, no programs (including Firefox) are using an abnormal amount of memory or CPU. I have reinstalled Windows, trying different things, at least 8 times. This includes using different XP discs and versions. I have also of course tried installing all the correct drivers. I have replaced or exchanged with a similar part ALL of the hardware listed except the PSU and HDD. EVERYTHING else has been exchanged or removed in an attempt to see if it was the problem. What the heck is with the quick launch bar?
I am certain other problems exist as well but this is the point I haven't passed. The system passes a 48 hour loop of Prime 95 / Orthos / Memtest86 with flying colors.
1 Cookie for the winner. HELP!
Update: tried replacing the CPU with a Q6600 - didn't fix it. SP2 has already been tried as a few of you noted SP3 might be the problem.