Wireless stalling after HD re-image

So I decided to have my HD re-imaged today. Everything seems to run a bit better, with a glaring exception: The wireless.

First, when I turn on the wireless, it takes almost 5 seconds between the time when the light comes on and windows finally recognizes the wireless turning on. Before, it would only take about 1 second or so.

Second (and much more serious), is that the connection constantly stalls out. Windows still says I'm connected, but there is absolutely no activity going through the wireless. For example, when I click on a link, Firefox/IE will say "waiting for...." forever. If I click it again, it'll go though. If I'm in the middle of a download, the download status window will stop refreshing the time estimates and transfer rates (In other words, the download stalls out). In iTunes, it takes forever to connect to a shared library and/or play a song on the share library, but when I try it a second (sometimes a third) time, it works perfectly

I have updated to the latest drivers. Any ideas?

 

try uninstalling the drivers and reinstalling them
do you know what version of drivers you had before the re-image?

 

I do not know what I had before the re-image, but I did update to the latest drivers to no avail.

UPDATE: Now that I've had the chance to use my notebook on more than one wireless network, I can tell you that it seems to work fine on different networks, but seems a tad slower than what I remember. I will try my dorm room access point later tonight.

 

delete your wireless drivers, and the hardware from the hardware profile. restart computer, and reinstall drivers. it worked for me.

 

I deleted the drivers using the device manager; how do you delete the hardware from the hardware profile?

 

UPDATE: I enabled DHCP on my Wireless Access point, and that seemed to fix the problem.... last night. Today, I'm back on, and the wireless seems to be "hanging" again. Any ideas? I'm starting to suspect it's my Access point, but I need to try different networks to see if this is really the case or not.

 

Well, I now think the problem is with my router, and not my laptop. All the other wireless networks I've connected to so far have been flawless (I do seem to be getting lots of FCS errors, though...). Go figure.