Originally Posted by beers
Go remove those wireless profiles that aren't yours.
By default Windows will not simply 'authenticate to any network'.
You've manually been on them before and that's why when yours drops out you connect to another AP.
There are no other wireless profiles besides the one for my home router.
Originally Posted by scottsee
Do this.. Windows has a stupid feature that automatically try and connect to better wifi networks in range of your machine.
It never tried to connect to the other connections, it just dropped me and wouldn't let me reconnect until that connection disappeared.
Originally Posted by Spooony
If you have a wireless network that randomly drops connections even though your wireless adapter connects fine to the wireless network and Windows 7 says that nothing is wrong, and may even still show as connected based on the icon in your system tray, chances are you are being knocked off the wireless network by browser elections from the old NetBIOS network protocol. Basically, browser elections unleash a flurry of broadcast packets out onto the network, that for some reason are not handled properly and Windows 7 starts shutting down services to fix it.
Go to the logs are under Administrative Tools -> Event Viewer -> Windows Logs -> System
Browser Elections from NetBIOS breaking wireless network connections is a pattern of 3 system events that all occur with the same time stamp. The easiest way to find them is to look for the Source of BROWSER. That will be the first of the three events. The other two events will be the TCP/IP NetBIOS Helper service was successfully sent a stop control, followed by The TCP/IP NetBIOS Helper service has been stopped.
next events may vary depending upon how your computer is set up, but will include one indicating that the TCP/IP NetBIOS has successfully started.
Look for those events quickly and see if they are exact as I described
Seems as though it was just interference, I've not had a drop yet (touch wood) for the past 30 minutes or so. I think that's the problem fixed. Thanks a lot for the input guys, +reps.