New
#11
Oh, durp. Yeah, to be honest dealing with wireless is something that often has to be trained. I personally deal with wireless all the time and it's a royal pain, but is gratifying once you get it just right.
I'm not sure how to continue approaching the BSODs, though. Without any kind of dump file, we're kinda lost. If you can see the blue screen and tell us what it says, that'd be at least something to start off with. I'll need the code number, the name of the bugcheck (is in all caps), the 4 parameters next to it (4 long hex numbers in parentheses), and a driver name if it shows that up too (as in "probably caused by:" or something like that).