Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
1/17/2007 3:13:00 PM EDT
I recently upgraded my computer from an AMD 1.2GHZ to a P4 Duo Core complete with a new motherboard, video card, and 2gb of memory.  On a clean install of XP, windows boot time takes forever, as does shutdown.  It's easily twice as long as when I had my AMD with a hard drive nearly full.  

I have all of the "Critical Updates" including the service packs and .Net.  Once Windows is up and running, things go smoothly... I can play Oblivion with the video settings maxed at 75+fps.  It's just the startup and shutdown that baffles me.

There is plenty of space on my hard drive left for virtual memory, so I have ruled that possibility out.  I have run HouseCall, Adaware, and Spybot to make sure I didn't pick anything up while using IE to get updates.  

Let me know if you want a HiJack report or any other info.
1/17/2007 3:25:38 PM EDT
[#1]
Disable your NIC card - and see if it is still slow:


www.tunexp.com/tips/communicate/very_slow_boot_when_networking/



Use BOOTVIS to trace the source:

www.pctechshield.com/bootvis.htm
1/17/2007 4:15:59 PM EDT
[#2]
i was going to suggest updating your nic card drivers, and unistalling .net  frameworking


its typically not needed.      

ya know whats retarted my xti x850 pro card requires .net frameworking to be installed or their driver won't work properly

falarak gave excellent advice as well.    i haven't used that tool in over 3 years
1/19/2007 1:51:49 PM EDT
[#3]
Goto the start menu, goto "Run", and type in MSConfig, goto "Startup", and tell us (with screenshots or something) what's on it.
1/22/2007 11:43:32 AM EDT
[#4]
I think I figured out the problem.  I am using an ATI card and have the Catalyst Control Center installed.  I installed Catalyst before I updated to .Net v2.  From my understanding, Catalyst uses .Net v1 and if you install it before v2 then it's going to start a conflict.  On shutdown I would occasionally get a .net broadcasteventwindow error and I would have to end-process.  I looked it up, found others with an identical problem, uninstalled Catalyst, repaired .Net v2, and reinstalled Catalyst.  Now the problem is solved.


Sorry for the slow response time.